overriding HAL driver, alt_sys_init()

Thanks for the response Jake. I suspect your suspicion about the bsp tool generating the macro call from the component name rather than the driver is probably correct.

I think I replaced all the significant altera_avalon_uart's in the driver directory. Here is the output from a grep in the driver directory,

$ grep -irn altera_avalon_uart .

./class.ptf:2:# class.ptf for altera_avalon_uart

./class.ptf:16: CLASS altera_avalon_uart

./class.ptf:59: class = "altera_avalon_uart";

./class.ptf:61: iss_model_name = "altera_avalon_uart";

./HAL/system.h_component_output.gtf:5: altera_avalon_uart class of components. It expects the following

./my_uart_sw.tcl:8:# Associate it with some hardware known as "altera_avalon_uart"

./my_uart_sw.tcl:10:set_sw_property hw_class_name altera_avalon_uart

I got a similar result when using the FIFO uart from these forums, but didn't implement the hardware so perhaps that was a doomed attempt.

Actually, the whole reason for the custom uart is because we are using a bit from a PIO component to control the direction of traffic on a rs485 transceiver. Apparently the fifo uart has this ability but I am trying to do it in software before asking the person in charge of the hardware to make any changes.