Minized prints cabalistic characters to SDK terminal

I use MiniZed with Xilinx SDK 2018.3 in standalone mode;

My design_wrapper_hw_platform uses uart1 for stdin and sdtout (as shown in the tutorial) and also some QuadSPI block (unused in the project for now)

"Hello Word" comes out as "`Ûqp‚nî" whether I use print or xil_printf. Baud rate is 115200.

What can cause that?

0 jafoste4 over 5 years ago

Hi Anne,

Is the terminal your using to view this text setup to 115200 BAUD Rate? Or is just the MiniZed setup for this baud rate?

My assumption is that the BSP your using was re-targeted from UART0 to UART1.

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Fred27 over 5 years ago

Generally, those random characters mean that data is flowing but the baud rate is wrong. However, I recently had a similar issue with xil_printf on the Zybo Z7 and couldn't find a baud rate that would work. It wasn't anything critical so I never got to the bottom of it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 annemenendez over 5 years ago in reply to jafoste4

Indeed, the project targets uart1 and the baud rate is 115200 on both sides (vivado and SDK terminal).
If I select uart0, then nothing is displayed at all, which makes sense.

I am now suspecting that this comes from the fact that I started with a project running on a different ZYNQ board and changed it to Minized, with automatic update of the necessary IPs. I am afraid that I will have to re-enter the design from scratch for the minized platform. I welcome definitely welcome other hints or suggestions.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jafoste4 over 5 years ago in reply to annemenendez

Hi Anne,

Typically we recommend rebuilding the project from scratch targeting the desired hardware you wish to use. I suspect some clocking issue with your hardware platform. My suggestion would be to rebuild the project from scratch targeting your MiniZed and see if you get the desired output.

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 annemenendez over 5 years ago in reply to jafoste4

Unfortunately, that was the way to go. Pretty tedious!
Thx for the help
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jafoste4 over 5 years ago in reply to annemenendez

Hi Anne,

Just an after thought. We typically script any of our designs that we plan to keep updated to the latest tool set or change to a different set of hardware. This in turn allows us to build the designs from the ground up every time. This also allows you to target a diffrent set of hardware wish some text changes. This tends to help with the type of issue you have seen. Please feel free to take a look at the Avnet github for reference.

Thx,
Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel