I'm trying to connect to the serial port of my Xilinx Ultrascale ZCU102 with my Macbook Pro (OS: Big Sur 11.2). The board is connected with a USB - miniUSB cable to a hub USB C connected to one of the Mac USB C ports.
With lsusb | grep Serial I get correctly listed both the USB adapter and sd card reader which compose the hub. However, I cannot figure out how to see data transmitted by the board through UART. I've tried with Serial Tools, but the two serial ports I can see does not show anything. Then, I've tried to list devices with ls \dev, but I cannot figure out what can be the device.
How can I solve?
Thank you in advance
I was following the Coral Dev Board get started guide - Get started with the Dev Board (https://coral.withgoogle.com/docs/dev-board/get-started/). Everything worked fine until to the step - Connect to the board's shell via MDT.
I've waited about 5 minutes until the flashing to complete, and the terminal prompt returned to me, then I tried the command:
mdt devices
The terminal returns nothing. Unlike the guide says it supposes to return my board hostname and IP address. I've checked the USB-C OTG and USB-C power cable, they are all connected well.
I've also tried this solution: https://superuser.com/questions/1452786/coral-dev-board-not-recongized-on-mdt-shell. I went to Network under System Preferences, and clicked "+" icon, but I couldn't find the mendel device.
I'm using Macbook Pro running on macOS Catalina. The fastboot and mdt commands are both working.
I just found a solution:
Just plug micro-B USB cable, then run:
screen /dev/cu.SLAB_USBtoUART 115200
If it shows blank, wait a couple seconds, then plug usb-c power cable, the system of the dev board will start loading, the login prompt will come out. After I logged in, I plugged the usb-c cable into data port(keep the micro-B USB cable in at the same time), then run:
mdt devices
or
mdt shell
This solution works for me only when I have turned on the wifi of the dev board and connect it to the same wifi network. If you want to turn on the wifi network of coral dev board, run the command on screen terminal:
nmtui
The Network Manager TUI prompt will come out then you can connect to your wifi network.
It's a problem on macOS Catalina. It doesn't "see" USB connection as a network connection and as such it is impossible to connect to Coral Dev Board.
I have the same issue, but I tried with another MAC with older macOS and it worked just fine.
Now, I don't have yet the solution, but at least we all know the problem ;-)
Regards,
Rui
First check the that the device is detected by running dmesg command.
Normally you should see something like this
$ dmesg
...
[107834.681816] usb 2-3: new high-speed USB device number 3 using xhci_hcd
[107834.845073] usb 2-3: New USB device found, idVendor=18d1, idProduct=9304, bcdDevice= 4.19
[107834.845077] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[107834.845079] usb 2-3: Product: Mendel
[107834.845081] usb 2-3: Manufacturer: Google,LLC
[107834.845083] usb 2-3: SerialNumber: bored-horse
[107834.985296] cdc_acm 2-3:1.0: ttyACM0: USB ACM device
[107834.986069] usbcore: registered new interface driver cdc_acm
[107834.986070] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[107835.005045] cdc_ether 2-3:1.2 usb0: register 'cdc_ether' at usb-0000:06:00.3-3, CDC Ethernet Device, aa:9f:04:54:dc:45
[107835.005124] usbcore: registered new interface driver cdc_ether
[107835.019787] cdc_ether 2-3:1.2 enxaa9f0454dc45: renamed from usb0
[107897.336866] IPv6: MLD: clamping QRV from 1 to 2!
[107956.344960] usb 2-3: USB disconnect, device number 3
[107956.345357] cdc_ether 2-3:1.2 enxaa9f0454dc45: unregister 'cdc_ether' usb-0000:06:00.3-3, CDC Ethernet Device
...
After that, check your network interfaces using ip command
$ ip link
Then look for the one with the one with the same MAC address as the one that appears in the logs of dmesg.
Once you find it, run this command to assign an IP address
$ sudo dhclient <name of the network interface of coral dev board>
Now you should see an IP assigned to the interface.
$ ip a
After that, run mdt devices and you should see the dev board connected.
$ mdt devices
bored-horse (192.168.100.2)
I had the same problem in Debian (Buster). I was able to follow all the steps to connect and flash the device until 'mdt shell' and I would receive a 'Unable to find any devices on your local network segment' message.
Opening the network settings and enabling 'USB' as a network interface worked for me.
After connecting to the Coral Dev Board the first time and exchanging private keys, I unplugged the USB cable. After that, my computer was offline until I re-enabled the ethernet connection. It seems that enabling the USB network disabled the ethernet. At that point, mdt shell was able to connect via the ethernet network.
So I've just spent most of the afternoon with this issue. After I downgraded the OS to Chef it seemed to work fine as the USB device (OTG port) would initialize on boot and then the SSH key could be pushed through. However, with the latest OS (Eagle) this was not the case.
The fix was simple:
Remove the USB C OTG port cable from the board
Reboot the Coral board
Wait for boot sequence to complete
Connect the USB C OTG port cable to the board
Run "mdt shell"
key is pushed through!
Now I can set up the WiFi or connect Ethernet and remove that cable once again and now I can freely call mdt shell and it connects every time.
I am using Open-Q 820(APQ8096) carrier board. I have installed the Hexagon SDK 3.2 application and its USB driver which is available in the installation path of Hexagon SDK 3.2.
As a result, after installation if I connect OPEN-Q 820 board, it must recognized as
Qualcomm USB Composite Device XXXX under Universal Serial Bus controllers in device manager
Qualcomm HS-USB Diagnostics xxxx (comx) under Ports in device manager
But here there is no Qualcomm based usb recognised and instead only a standard USB Composite Device was getting listed below the Universal Serail Bus controllers section of the device manager.
To solve this we had followed the readme file which is present in the installation path of Hexagon SDK 3.2 (Qualcomm\Hexagon_SDK\3.2\tools\debug\usb) and tried to replace the standard USB Composite Device to Qualcomm based Serial port but it didn't work as expected. The VID_05C6&PID_9039 doesn't seem to have match in the list of com port in Qualcomm.
I am running windows 10 (64 bit) PC with full USB access.
OPEN-Q 820 Device instance path is mentioned below
USB\VID_0BDA&PID_57DE&REV_00147
USB\VID_0BDA&PID_57DE
Thank you
I'm working on a Kinect app, using a Kinect 2.0 for Xbox One on a Windows 10 PC. Now I have a problem using a new computer. Testing the Kinect with KinectStudio or any of the example programms, the Kinect keeps reconnecting frequently, as if you would pull out the usb cable and plug it in again.
If the Kinect is running I get the full 30 fps but mostly only for about 10 seconds before the connection is interrupted.
There is no other device plugged in at the usb 3 ports and I tried all of the ports. The computer has an Intel 8 Series/C220 Series USB Chipset and I updated and reinstalled all the drivers. The Kinect Configuration Verifier showes a problem with the usb Controller: "Supported USB 3.0 port detected with unknown bandwidth. Kinect may or may not be compatible with your hardware."
Did anyone experienced something similarly or do you have any idea how to fix it?
Your Kinect has to be attached to a 3.0 port that has its own pcie channel.
If the usb isn't built into the motherboard and you don't have a 3.0 without anything else on the channel, then you'll need to get a pcie to usb 3.0 addition for your motherboard.
I'm currently learning driver programming and am at very nascent stage. I'm unable to get the difference of use of xHCI, EHCI, or OHCI drivers and usb_storage.
When I plug my USB device (pen drive) and observe dmesg output, it says that my device is using the ehci driver, but my device stops working when I rmmod usb_storage.
There are many drivers for different kind of USB devices let it be mouse, keyboard, camera, etc.
As of now, I assume that the xHCI driver is for USB host and the other driver is for the device we connect to our USB host. Am I correct? If not, what is the explanation?
*HCI are specifications of USB hosts:
xHCI - for USB 3.0
EHCI - for USB 2.0
OHCI and UHCI - for USB 1.x
usb_storage is a upper level driver working on the USB host side, and it is responsible for communication only with USB storage devices, not keyboard, mouse, etc.
The USB is maintained in form of a stack and *hci drivers are the lowest level in that stack. usb-storage and other drivers are located on a higher level of this stack.