Forum Discussion
Hi Archer,
Thank you for such detailed response.
I found the latest version of the fifoed_avalon_uart (13.2) and will try it at some point.
Meanwhile I have a few comments.
I registered custom alt_instruction_exception_handler that has 3 parameters: cause, exception_pc and badaadr. It does not have exception_context parameter that you have mentioned.
My BSP does not have IORD_ALTERA_AVALON_UART_STATUS, ALTERA_AVALON_UART_STATUS_xxx_MSK definition. I guess they are for the standard UART. I can use their FIFOED_AVALON_UART_STATUS_xxx counterparts but some of them the driver uses for calling a corresponding ISR, so it seems that Overrun error is not considered as a problem.
Hi @BBS3000,
Thanks for letting me know that you will try a newer version. It may be helpful in your usage scenario.
I see below case having some discussion about fifoed avalon uart. It has useful info, please refer to it.
Why "fifoed avalon uart" was removed from web site ? - Intel Community
For the driver part, it is not designed to consider all potential conditions and handle them properly as avalon uart IP. The designers have to evaluate the capability of the IP core they are using and find alternate solution if performance can't be satisfied. Such as using one more Nios core to offload part of processing task.
Regards,
Archer