Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 347 subscribers
  • Views 1317 views
  • Users 0 members are here
Related

Yet another issue with Zedboard UART

carac

Hello everyone,

I have been scratching my head on this for the past week and can't seem to figure out what's happening with the USB-UART on my Zedboard.

When i boot from the default image on the SD card, i can open a gtkterm on /dev/ttyACM0 (baud rate 115200) and use it as a console for the embedded Linux with no issue

Then, i try to generate a simple bistream with just the zynq processing system and only UART 1 on MIO 48:49. Compilation runs fine, I can program the device (I checked that it is indeed my design by switching on some random LEDs), export the hardware and start the SDK, generate a BSP and starts a hello world project. I check that i can indeed connect to the USB-UART interface by creating a new connection in the SDK terminal (which then indicates Connected to Serial (/dev/ttyACM0, 115200, 0, 8).

However, when i build the project and run it (Launch on Hardware), although the SDK log on the right shows that the program was loaded and executed, the console at the bottom remains completely empty (except for the header "TCF Debug Virtual Terminal - ARM Cortex A9 MPCore1)

I'm using Vivado 2018.3 Webpack  under Ubuntu 16.04 but also tried with several earlier versions (I went all the way back to 2014.1 and 2014.2 with the same result). I have done every possible tutorial on this (which always amount to load an empty design with just the processor and do a helloworld). I have no compilation error at any stage of the process and i'm pretty sure my design is loaded since i can set some LEDs and see them on the board. I have tried not connecting the SDK terminal to the /dev/ttyACM0 and use gtkterm or screen instead, with the same result.

I have the last version of the USB drivers for the Cypress and FTDI devices and the correct permissions to access them (otherwise I would not be able to connect to the reference design in the SD card via the UART link) therefore I have no idea what's going on at this point.

Anyone got stuck with the same issue? I'm pretty sure the problem exists between the keyboard and the chair but i have no clue as to where exactly image

Parents
  • 0 in reply to bhfletcher

    Hello Bryan, STDIN and STDOUT are set by default to ps7_uart1 in the BSP.

  • 0 in reply to carac

    OK, good. That's correct. If you had enabled ps7_uart0, it would have defaulted to that. Since you only had ps7_uart1, it set it to the correct thing.

     

    How are you setting the clock and DDR parameters?

     

    Thanks,

    Bryan

  • 0 in reply to bhfletcher

    Hi, just a quick update.

    I've done some more experiments and I think I narrowed it down to a problem with the USB_UART driver on my Linux machine :

    - I downloaded Vivado 2018.3 on a Windows machine, re-did the same project and everything works fine

    - If I plug the Serial cable to my Windows machine, the JTAG cable to my Linux machine, I can run the program on the SDK of my Linux machine and see the Hello world on my Windows machine (using Putty)

    - However, if I plug the Serial cable to my Linux machine, the JTAG cable to my Windows machine, and I run the program on the SDK of my Windows machine, nothing appear on the Linux serial console (again using Putty)

     

    So I doubled checked my driver/kernel configuration :

    $ lsusb :

    Bus 001 Device 036: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC

    ---

    Bus 001 Device 037: ID 04b4:0008 Cypress Semiconductor Corp.

     

    $ ls /dev/ttyACM*

    /dev/ttyACM0

     

    $ uname -a

    Linux <mymachine> 4.15.0-70-generic #79~16.04.1-Ubuntu SMP Tue Nov 12 14:01:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

     

    $ cd /opt/Xilinx/Vivado/2018.3/data/xicom/cable_drivers/lin64/install_script/install_drivers/ && sudo ./install_drivers

    INFO: Installing cable drivers.

    INFO: Script name = ./install_drivers

    INFO: HostName = <hostname>

    INFO: Current working dir = /opt/Xilinx/Vivado/2018.3/data/xicom/cable_drivers/lin64/install_script/install_drivers

    INFO: Kernel version = 4.15.0-70-generic.

    INFO: Arch = x86_64.

    USB udev file exists and will not be updated.

    --File /etc/udev/rules.d/52-xilinx-ftdi-usb.rules exists.

    --File /etc/udev/rules.d/52-xilinx-ftdi-usb.rules version = 0001

    --File 52-xilinx-ftdi-usb.rules exists.

    --File 52-xilinx-ftdi-usb.rules version = 0001

    --File 52-xilinx-ftdi-usb.rules is already updated.

    --File /etc/udev/rules.d/52-xilinx-pcusb.rules exists.

    --File /etc/udev/rules.d/52-xilinx-pcusb.rules version = 0002

    --File 52-xilinx-pcusb.rules exists.

    --File 52-xilinx-pcusb.rules version = 0002

    --File 52-xilinx-pcusb.rules is already updated.

    INFO: Digilent Return code = 0

    INFO: Xilinx Return code = 0

    INFO: Xilinx FTDI Return code = 0

    INFO: Return code = 0

    INFO: Driver installation successful.

    CRITICAL WARNING: Cable(s) on the system must be unplugged then plugged back in order for the driver scripts to update the cables.

     

    $ cd /opt/Xilinx/SDK/2018.3/data/xicom/cable_drivers/lin64/install_script/install_drivers/ && sudo ./install_drivers

    INFO: Installing cable drivers.

    INFO: Script name = ./install_drivers

    INFO: HostName = cyberalps

    INFO: Current working dir = /opt/Xilinx/SDK/2018.3/data/xicom/cable_drivers/lin64/install_script/install_drivers

    INFO: Kernel version = 4.15.0-70-generic.

    INFO: Arch = x86_64.

    USB udev file exists and will not be updated.

    --File /etc/udev/rules.d/52-xilinx-ftdi-usb.rules exists.

    --File /etc/udev/rules.d/52-xilinx-ftdi-usb.rules version = 0001

    --File 52-xilinx-ftdi-usb.rules exists.

    --File 52-xilinx-ftdi-usb.rules version = 0001

    --File 52-xilinx-ftdi-usb.rules is already updated.

    --File /etc/udev/rules.d/52-xilinx-pcusb.rules exists.

    --File /etc/udev/rules.d/52-xilinx-pcusb.rules version = 0002

    --File 52-xilinx-pcusb.rules exists.

    --File 52-xilinx-pcusb.rules version = 0002

    --File 52-xilinx-pcusb.rules is already updated.

     

    INFO: Digilent Return code = 0

    INFO: Xilinx Return code = 0

    INFO: Xilinx FTDI Return code = 0

    INFO: Return code = 0

    INFO: Driver installation successful.

    CRITICAL WARNING: Cable(s) on the system must be unplugged then plugged back in order for the driver scripts to update the cables.

     

    $ cat /etc/group | grep dialout

    dialout:x:20:<myusername>

     

    I also tried all the steps described here : http://microzed.org/content/usb-uart-problem

    So far, still nothing...

  • 0 in reply to carac

    If you are using a VM, you could look at the instructions here for enabling the cable in your VM: http://avnet.me/vm_install_guide_2018_3 .

     

    I thought I also read somewhere that Linux had issues connecting via USB through a docking station or hub. Someone else reported that they had to connect directly to a USB port on the laptop instead of a port replicator / docking station.

     

    Bryan

Reply Children
No Data