I have a problem setting the USB3 in UltraZed-3EG

Hi,

How I am defining through PetaLinux (2018.3) the USB3 of the UltraZed-EG, as apparently it doesn’t support the previous setup ( of Ultra96-V1 and V2).

The main command ifconfig usb0 192.168.100.1 netmask 255.255.255.0 and modprobe g_ether

Are not recognized in UltraZed-3EG as they were recognized in Ultra96-v1 or v2.

I am getting the following messages:

479.877751] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

[ 481.965750] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

[ 484.053749] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

[ 486.141749] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

[ 488.229748] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

[ 490.317748] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

I have replaced two cables that works well in Ultr96-V2 Boards and got the same messages.

Why it specifies USB2 and not USB3, is the connector of J15 shouldn’t be 2-3?

What should be the mode of ID J15, currently it connected 2-3 I am looking at four jumpers that refers to USB modes: power and ID,

They look okay they are in configuration of host not otg and not device.

Thanks,

Shiri

0 drozwood90 over 5 years ago

Hi there,

Sometimes when using USB3 with the Zynq MPSoC, the USB cabling can be highly suspect. I personally use this adapter and plug my USB device DIRECTLY into the adapter WITHOUT using any cables. That seems to allow my devices to work.
https://www.whizzsystems.com/usb3-micro-b-plug-adapter/

If you check the Xilinx forums, you'll see similar responses from many users. There are a few other good adapters, but I've only tested the above. From what I recall reading on the Xilinx forums, if you use a generic adapter or generic cables (think eBay) there is a very high probability that you will have issues.

--Dan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sint12345 over 5 years ago

Thanks for your answer, although I have replaced the cable, and I used the same cables that worked great at Ultra96V2 with no problem.

I do think the main problem is that the driver of g_ether was not loaded properly as it is not recognized.

I think because the bsps may be different than the driver was not loaded properly

modprobe g_ether -
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel