problem of PS UART self-test application

Hi...
I have faced a strange problem.
I use the code that Xilinx offers, named xuartps_selftest_example.c, and don't modify it except some instance name. When I run it, it shows unrecognizable code and shows Failed. But when I debug it, it shows success.
What's the problem?

0 Former Member over 12 years ago

顶
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 12 years ago

i also have the same problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 zedhed over 12 years ago

Hi tec998s,

Which version of tools are you using? Can you describe the failure any further? When you say that the application "shows unrecognizable code and shows Failed" are you referring to garbled output on the console?

When you run the application, are you creating a new run configuration for the application?

If the UART1 PS device is not being initialized properly to generate character outputs at the correct baud rate, this condition could cause garbled characters on the console.

The ps7_init.tcl file exported into SDK by PlanAhead is used by XMD in the background to initialize the Zynq PS hardware before executing an application. I know that by default, when creating a debug configuration, the path to the ps7_init.tcl gets populated in the "Device Initialization" tab of the
Debug Configurations manager. Can you check to see if that same ps7_init.tcl file is being specified for your application's Run Configuration as well?

Also, I would recommend against using the serial console built into SDK for now. I recommend using the latest version of Tera Term which is available for free from the SourceForge Japan site:

http://ttssh2.sourceforge.jp/index.html.en

Regards,

-Kevin
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 12 years ago in reply to zedhed

I have a similar UART problem. I routed the PS uart0 to the EMIO and then to two PMOD pins, JA1 and JA2, The stdin and stdout for the BSP are set to ps7_uart_1 and the through the Cypress usb to serial chip as per the standard config. The default baud rate for stdout /stdin is specified as 115200. But after adding UART0, It seems to step down to half the baud rate of 57600. (using Terra term) Then the loopback test for the UART0 fails for both the polled mode and interrupt mode. Running the debugger shows the return test string misaligned as if the loopback mode is broken.
I'm using Plan Ahead/EDK/SDK 14.3
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fayyazrafiq over 11 years ago in reply to Former Member

I am getting the same problem, could you please tell me, how you resolved the problem.

Many Thanks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 11 years ago in reply to fayyazrafiq

I have the same problem. I routed UART0 from the PS to the PL through the EMIO. The self test is failing. Did anyone figure out a fix?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 fayyazrafiq over 11 years ago in reply to Former Member

I am facing the same problem, i routed the UART0 to EMIO and then to package pins but no data output. I am using XPS/SDK 14.5. I wrote somewhere that it is bug in the ZEDBOARD (http://www.zedboard.org/content/zedboard-revision-d-bug-issues-emio-related). I found so many posts for this problem but there is no single solution exist either from Xilinx or ZEDBOARD side. I thought either the ZEDBOARD manufacturer or the XILINX are concealing something which is very severe and wasting time for the developer in this field.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 11 years ago

As many people said above, I have same problem with run UART0 selftest or UartPSExample program.
I got a message "UartPSExample FAILED".
(I am using SDK 2013.4 and Zedboard rev D.)

Is there any solution for this?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 10 years ago

I hope that this is of some help. I am using Vivado 2014.2 with the ZC702 board (not the ZedBoard), but I think that my solution may work for ZedBoard as well. I saw the comment by Kevin above about the ps7_init.tcl file and it led me to check which ps7_init.tcl was used in my debug and in my run configurations. It turns out that Vivado/SDK2014.2 automatically populated the configurations with the wrong file, from an old design. I switched to the ps7_init.tcl file in the <design>/<design>.sdk/<design>_hw_platform_0/ps7_init.tcl and the UART test suddenly started passing.

Paul
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel