NIOSV firmware stuck when juart-terminal is not open for the print messasges.

[prashant_gohel]

Hi,

I am facing an issue where the NIOSV firmware gets stuck if the JUART terminal is not open for printing messages. Once I open the JUART terminal, everything works fine.

Is there any way or BSP setting I can use to prevent the NIOSV firmware from getting stuck when the JUART terminal is not open?

[EstebanV_Altera]

Hello,

This is not usual behavior, the default shouldn't behave like this. Are you having prints into the terminal? If you remove such prints the programs continues?

Which Quartus version are you using? Which NIOSV version (G,C,M)?

Please provide as much details as possible so I can reproduce

~E.V.

[prashant_gohel]

Hi Esteban,

I am using Quartus 25.1 with NIOSV version M.

When the terminal is open, everything works fine, but if I close the terminal, the NIOSV gets stuck. Our requirement is that the NIOSV should run normally without needing the terminal to be open.

[EstebanV_Altera]

Could you please verify what is written here?

https://www.intel.com/content/www/us/en/docs/programmable/683130/21-4/driver-options-fast-vs-small-implementations-29605.html

"fast" version of the driver shouldn't be blocking execution.

~E.V.

[dim1]

When you generate BSP, go to the JUART Driver settings - there is an option to allow the driver to ignore when the output FIFO is full. Enable that option and it will not wait for somebody to read the output.

[EstebanV_Altera]

Please confirm both setings pointed out by me and @dim1 

In the BSP should appear as: altera_avalon_jtag_uart_driver.enable_small_driver = false and/or altera_avalon_jtag_uart_driver.enable_jtag_uart_ignore_fifo_full_error = true

~E.V.

[BoonBengT_Altera]

Hi @prashant_gohel,

Greetings, just checking in to see if there is any further doubts in regards to this matter.

Hope your doubts have been clarified.

Best Wishes

BB