I have a custom designed base board with the Verdin iMX8M Mini Quad 2GB WB IT V1.1B based. The image used is your Linux Reference Minimal 5.6.0+build.18.
I’m using the USB_2 with a schematic very similar to that in figure 27, where the IC1A has been replaced by the AOZ1353DI-01 (it is the same one used in the Dhalia board). I’m using USB_1 in host mode (USB_1_ID=0) with the same schematic as USB_2.
Thank you very much for your answer but I think that in this case the imx8m mini and the imx8m plus do not manage USB in the same way. The default configuration for the Verdin module with imx8m mini in the DTS is as follows:
We use the same one and I can confirm that the USB_1 port changes its role depending on what is connected to the USB_1_ID input (GND: host / NC:device). The USB_2 port is configured as HOST and has the same error: it only detects a device during boot or if the uhubctl command is executed.
After booting and without any USB device connected, the situation is as follows:
Nothing is detected
Run uhubctl (no arguments)
Device is detected, enumerated and works
If you have any comments or suggestions, please drop me a line.
Hi @henrique.tx !
Thank you very much for the link, we will try to modify the ci_hdrc_imx.c file to try to solve this issue. Out of curiosity, what causes this issue? is it a problem in the SOM?
I confirm that by connecting the USB_1_ID signal to GND the error persists. I have seen that they have not published anything about this issue and it catches my attention. In the Dahlia card the USB_1 is not connected to a HUB and yet the detection of USB devices in the X3A port works correctly, how can this be possible?
Thanks for your attention. I’m looking forward to your reply.
This issue is related to NXP changing some pins after Toradex released the Verdin iMX8M Mini. So the versions available are affected by this issue. A workaround could also be host-fixing the role on the device tree (instead of OTG).
I had some issues similar to this post where the OTG didnt work properly, and this did indeed fix it for me.
I dont know if you can use this confirmation for anything, but hopefully it can help someone in a similar issue