UPHY Fails to initialize after update to 35.5.0

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Hello,

I update my current setup to 35.5.0 and am seeing error messages during bootup.
I feel like this is why I fails to initialize my ethernet interface once Linux has booted.

HSIO UPHY reset has been de-asserted 0x0
initialized uphy
fmon_enable: FMON_GBE_UPHY_L7_CORE_TX: detected fault 0x1
fmon_enable: FMON_MGBE3_TX_PCS: detected fault 0x1
fmon_enable: FMON_MGBE3_MAC: detected fault 0x1
fmon_enable: FMON_GBE_UPHY_L4_CORE_TX: detected fault 0x1
fmon_enable: FMON_MGBE0_TX_PCS: detected fault 0x1
fmon_enable: FMON_MGBE0_MAC: detected fault 0x1
fmon_enable: FMON_GBE_UPHY_L5_CORE_TX: detected fault 0x1
fmon_enable: FMON_MGBE1_TX_PCS: detected fault 0x1
fmon_enable: FMON_MGBE1_MAC: detected fault 0x1
fmon_enable: FMON_GBE_UPHY_L6_CORE_TX: detected fault 0x1
fmon_enable: FMON_MGBE2_TX_PCS: detected fault 0x1
fmon_enable: FMON_MGBE2_MAC: detected fault 0x1

I am using the same setup as my ORIN Devkit but now with an Indutrial board.

Thanks!

3

Hi,

If this is Orin industrial then it is common warning, you could ignore them.

4

Hi @WayneWWW ,

Thank you for the answer. Do you have any idea about what could cause my issue? Only the bootloader update was done and made us loose the capability to set the ethernet interface to up. The only thing that appeared are these messages so we though it could come from here but if it’s a normal message, could it come from a malformed device tree?

Thanks

5

Hi,

Just forget about any error log you’ve ever seen and only answered my questions first. If you stick to some specific logs, you won’t see the whole picture.

  1. Are you using a NV devkit here or a custom board? Or you are not sure?

  2. What bootloader update was that? What did you do? What was the bootloader before your update? Some old version?

  3. “loose the capability to set the ethernet interface to up” → I believe you are talking about the kernel side ethernet. Could you attach the full dmesg?

6

Hi,

  1. We are using the NV Devkit here (industrial)
  2. We went from Jetson Linux 35.2.1 to Jetson Linux 35.5.0
  3. Yes the kernel side ethernet you are right. Unfortunately I cannot share the demsg output at the moment. I will ask my supervisor.

Thanks

7
  1. We went from Jetson Linux 35.2.1 to Jetson Linux 35.5.0

I would like to point out some potential mistakes here. This upgrade does not include bootloader only.

Kernel update is also required. Thus, I guess you just didn’t indicate it correctly.
Or if you really only update bootloader, then that sounds a problem.

8

You are right, I just got more information that the kernel was also updated.

The configuration remains the same, we used the devkit default configuration and deployed it to the NV Devkit (industrial).

9

Then I don’t think that would be any problem if this is NV devkit.

If it really has problem then there would be plenty error reports, but that didn’t happen.

Waiting for you to share the log.