*RFSoC 2x2 kit University , Xilinx ZYNQ UltraScale+ RFSoC ZU28DR FPGA* model 
no. HTG-ZRF2-XUP

board boot image = (CASPER) rfsoc2x2_casper.img

Ubuntu 20.04 LTS , Kernel 5.15.0-71-generic

(long term) I need to log into this 2x2 board's internal Petalinux, so that 
I can configure its firewall. Normally this is done by using minicom and 
going in through a serialized TTY protocol. But physically through a USB 
cable into the board. (thus a USB-to-Serial conversion is required).  The 
embedded linux will ask for a username and password, which will be casper 
and casper

I am connecting the Micro USB 3.0 from the 2x2 board to a PC. I have 
installed the cable drivers of Vivado. I have installed kernel drivers for 
cp210x, usbserial, and ftdi. dmesg | grep tty shows nothing new. dmesg | 
grep USB shows nothing new. lsusb does not show a connection to this board.

There is no physical problem with the cables as this board connects and 
*communicates 
fine with the PYNQ toolchain.*

(Additionally I have even tried to create a serial connection to this board 
with a separate PC running Windows 10. Silicon Labs VCP drivers did not 
work. Silicon Labs Universal drivers did not work. Silicon Labs Dual CP2105 
USB to UART bridge Standard COM Port did not cause the computer to 
recognize this board.)

What am I doing wrong here? Should I purchase a Xilinx Platform Cable II? 
Or other?   
Thank you and best regards,
Ken Semanov

# modinfo usbserial.ko filename:       
/lib/modules/5.15.0-71-generic/kernel/drivers/usb/serial/usbserial.ko 
license:        GPL v2 description:    USB Serial Driver core author:       
  Greg Kroah-Hartman <gre...@linuxfoundation.org> srcversion:     
2098B346F9958408D3913EE depends:         retpoline:      Y intree:         
Y name:           usbserial vermagic:       5.15.0-71-generic SMP 
mod_unload modversions # modinfo ftdi_sio.ko filename:       
/lib/modules/5.15.0-71-generic/kernel/drivers/usb/serial/ftdi_sio.ko 
license:        GPL description:    USB FTDI Serial Converters Driver 
author:         Greg Kroah-Hartman <g...@kroah.com>, Bill Ryder 
<bry...@sgi.com>, Kuba Ober <k...@mareimbrium.org>, Andreas Mohr, Johan 
Hovold <jhov...@gmail.com> srcversion:     C27E9B59BFCD7E40039C94E depends: 
       usbserial retpoline:      Y intree:         Y name:           
ftdi_sio vermagic:       5.15.0-71-generic SMP mod_unload modversions 
sig_id:         PKCS#7 signer:         Build time autogenerated kernel key # 
modinfo cp210x.ko filename:       
/lib/modules/5.15.0-71-generic/kernel/drivers/usb/serial/cp210x.ko license: 
       GPL v2 description:    Silicon Labs CP210x RS232 serial adaptor 
driver srcversion:     BB515B5DE5AC65351B31D53 depends:        usbserial 
retpoline:      Y intree:         Y name:           cp210x vermagic:       
5.15.0-71-generic SMP mod_unload modversions sig_id:         PKCS#7 signer: 
        Build time autogenerated kernel key # ./install_drivers INFO: 
Installing cable drivers. INFO: Script name = ./install_drivers INFO: 
HostName = XPS-8950-329 INFO: Current working dir = 
/tools/Xilinx/Vivado/2021.1/data/xicom/cable_drivers/lin64/install_script/install_drivers
 
INFO: Kernel version = 5.15.0-71-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. 

lsusb should know a device code for the 2x2 board, but is not there.
# lsusb Bus 002 Device 003: ID 0b00:0483 INGENICO 4-Port USB 3.0 Hub Bus 
002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 
011: ID 7392:7711 Edimax Technology Co., Ltd EW-7711UTn nLite Wireless 
Adapter [Ralink RT2870] Bus 001 Device 008: ID 0bda:1100 Realtek 
Semiconductor Corp. Bus 001 Device 007: ID 0bda:5483 Realtek Semiconductor 
Corp. 4-Port USB 2.0 Hub Bus 001 Device 006: ID 8087:0032 Intel Corp. Bus 
001 Device 005: ID 413c:2519 Dell Computer Corp. Dell Universal Receiver 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 

dmesg should show something like ttyAMC0 or ttyUSB0. Neither occurs between 
plugging and unplugging.
# dmesg | grep tty [    0.108882] printk: console [tty0] enabled [   
 0.641750] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is 
a 16550A [    0.674622] tty tty63: hash matches [    3.265952] 
dw-apb-uart.6: ttyS4 at MMIO 0x4014240000 (irq = 16, base_baud = 6250000) 
is a 16550A # dmesg | grep USB [174471.295188] usbserial: USB Serial 
support registered for generic [174484.880442] usbserial: USB Serial 
support registered for cp210x [174876.736576] usbserial: USB Serial support 
registered for FTDI USB Serial Device [174909.601717] usb 1-9: USB 
disconnect, device number 10 [175156.276064] usb 1-9: new high-speed USB 
device number 11 using xhci_hcd [175156.442266] usb 1-9: New USB device 
found, idVendor=7392, idProduct=7711, bcdDevice= 1.01 [175156.442280] usb 
1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 
[175156.572627] usb 1-9: reset high-speed USB device number 11 using 
xhci_hcd 

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ce9765a7-13f4-419c-acc9-aaba099ec2c2n%40lists.berkeley.edu.

Reply via email to