Tx2-4g R32.3.1 need device tree information and register information for USB 3.0 usbc super-speed

Old posts have dead links, so lets start this question again.

Please provide the devmem2 command to check all the need registers. My usbc does not come up as SUPER SPEED it comes up as HIGH SPEED


If you are talking about the uphy setting, you can dump

devmem 0x7009f028

If this is not what you want, then you can share the dmesg. Or put the same usb device to devkit and see if it could be detected as super speed. This can tell whether this is device side issue or jetson’s board design.

  1. the device comes up as super speed on the tx2 dev board.

  2. yes it is custom hardware that is why I am asking for the devmem commands so I can look at the config and such.

  3. I get this
    sudo devmem2 0x7009f028
    /dev/mem opened.
    Memory mapped at address 0x7f88436000.
    Value at address 0x7009F028 (0x7f88436028): 0xDEAD2009

  4. it appears that the address is not available for tx2-4g and it gives the same message on my tx2 dev board, and could you please give the memory addresses for the tx2 and their correct contents.

  5. I can include dmesg, but it will show the device is in high speed instead of super speed, and on the tx2 dev board it shows up as superspeed, so I really believe I have a device tree or register error on my part.



I am not sure what does that mean “that the address is not available for tx2-4g”. Didn’t you just dump that register and paste the result in (3)?

Please share your dts, board schematic and dmesg if you want us to help. There is no register to check for different speed issue.

You can also refer to the usb adaptation guide if you think it is device tree configuration problem.

is 0xDEAD2009 the correct value?

also the rs232 console gave me these messages.

[60465.210959] CPU3: SError detected, daif=1c0, spsr=0x800000c5, mpidr=80000101, esr=bf40c000
[60465.210973] CPU0: SError detected, daif=1c0, spsr=0x800000c5, mpidr=80000100, esr=bf40c000
[60465.210988] CPU4: SError detected, daif=1c0, spsr=0x800000c5, mpidr=80000102, esr=bf40c000
[60465.211002] CPU5: SError detected, daif=1c0, spsr=0x800000c5, mpidr=80000103, esr=bf40c000
[60465.211038] CPU1: SError detected, daif=1c0, spsr=0x800000c5, mpidr=80000000, esr=be000000
[60465.211251] ROC:IOB Machine Check Error:
[60465.211615] CPU2: SError detected, daif=140, spsr=0x60000145, mpidr=80000001, esr=be000000
[60465.211957] **************************************
[60465.211959] Machine check error in DCC:1:
[60465.212089] Status = 0xf400000100000405
[60465.212097] Bank does not have any known errors
[60465.212106] Overflow (there may be more errors)
[60465.212113] Uncorrected (this is fatal)
[60465.212121] Error reporting enabled when error arrived
[60465.212132] ADDR = 0x130

If you don’t share the schemaitc, then how could I know whether this is correct or not?

Do you really understand what does that register is doing and why I shared that register to you?

Oh sorry that I gave the wrong register. That is why there is error. But the result is still same. We need the scheamtic and dts files.

can I please get the correct register addresses, for all USB devices, and then we can compare the diff usb registers sets.

again, we are close, the usb is working and the dts might be correct, the only thing is the difference between high speed vs super speed.

Also hardware and manager just got back to me, no schematic because of no NDA.

I am stuck in between you and my management.

Again you must have seen what is preventing SUPER speed from working in other custom hardware.



The register I just shared is the ODMDATA. You can directly check /proc/device-tree/chosen/plugin-manager and share me the result.

There is no other register I can share.

If you cannot share schematic, please share your dts and just briefly describe your usb connection. For example, which port is enabled for SS device and what are the usb2 device accompanied with. Or you can just draw a block diagram of your usb connection info.

This is how we implement the USB port. The design works in the past, but now the SS is not recognized.

What does that mean “this design works in the past” ? What is changed here? Software version?

Hardware is the same, software changed a lot. We need to find out why the SS is broken.


Is your topic filed 2 years ago have anything related to the board we are talking about here?

Or it is a brand new board ?

mydtc (248.0 KB)

tai0vi6u is the my hardware guy

And could you dump the plugin-manager node? Please share the necessary info at once.

No, our board has only one USB3 super-speed. The other USB is just USB2.

Ok, could you help tell you software guy to share the necessary info?

And can we know what kind of “software change” is made here? This will give more hint.

how do you want me to share the plugin manager node.

you want to to tar gzip it?

file is the tar of the dir

file (350 KB)