topic Re: How to control USB HUB to output USB 3.0 eye diagram in imx8mplus platform ? in i.MX Processors

How to control USB HUB to output USB 3.0 eye diagram in imx8mplus platform ?

t2865k5 — Thu, 04 Nov 2021 03:36:58 GMT

Dear NXP ,

HW : srg_imx8mplus

SW : 5.10.9-1.0.0

I run command in imx8mplus plarform as follows:

echo "host" >> /sys/kernel/debug/usb/38200000.dwc3/mode
/unit_tests/memtool -32 0x38200430=0x0A010340

It can output USB 3.0 eye diagram because there is no USB HUB on imx8mplus platform.

I run the same command on the srg_imx8mplus platform but it didn't output USB 3.0 eye diagram.

I asked the USB HUB FAE and he told me . NXP imx8mplus must run command to USB HUB:
USB HUB port1,port2,port3,port4

May you tell me how to run the command (USB HUB port)

srg_imx8mplus HW:

igorpadykov — Thu, 04 Nov 2021 07:54:18 GMT

Hi Albert

seems it is standard procedure for usb hubs, described in usb.org documentation.

EHSETT tool can be used as described for example in below document :

Best regards
igor

t2865k5 — Thu, 04 Nov 2021 08:32:13 GMT

Dear NXP ,

The EHSETT tool works in windows environment.
In Linux OS environment , I use memtool
to write 0x0A010340 data to 0x38200430 address.

I need to run command to USB HUB in Linux OS.

For the USB HUB 4 ports of srgimx8mplus platform , it can work normally.This means that NXP has outputed data to the USB HUB in Linux OS.

So I need to know how to run command to the USB HUB in linux OS instead of in windows OS.

igorpadykov — Thu, 04 Nov 2021 10:29:59 GMT

for developing such procedure may be suggested to proceed with help of

Best regards
igor

t2865k5 — Mon, 08 Nov 2021 11:02:06 GMT

Dear NXP ,

imx8mplus is currently unable to run command to write
USB hub. Is my understanding correct?

igorpadykov — Tue, 09 Nov 2021 00:43:38 GMT

>imx8mplus is currently unable to run command to write
>USB hub. Is my understanding correct?

i.MX8M Plus USB module has not special commands for that case.

However i.MX8M Plus USB module complies with USB specification rev 3.0 (xHCI compatible),

so "xHCI compatible" procedure will work.

Please apply to hub vendor support for correct procedure.

Best regards
igor