NVMe flashing timeout error: L4t 36.4.3 - AGX Orin Industrial

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Hi,

We are getting NVMe time out error during the flashing process. Pls find the serial log and flashing log.
Kindly let us know, what might be the issue.
nvme-flash-timeout-log.log (321.8 KB)
serial-log-nveme-timeout.log (93.1 KB)

Note:

  1. We are using working proved flashing cable.
  2. we are able to flash successfully on onboard eMMC.

Thanks,
Nagesh R

3

*** Please note that this reply is generated by LLM automatically ***

Based on the provided information, it appears that you are experiencing an NVMe timeout error during the flashing process on a Jetson AGX Orin series system. You have provided two log files: nvmeflashtimeoutlog.log (3218 KB) and seriallognvemetimeoutlog.log (931 KB).

Unfortunately, the actual log file contents are not provided, so I’ll offer general guidance on potential issues and troubleshooting steps.

Possible Causes:

  1. Hardware Issues: Verify that the NVMe device is properly connected and configured. Check the cable and ensure it is securely connected to both the Jetson AGX Orin module and the NVMe device.
  2. Flashing Configuration: Review the flashing configuration file (jetson-agx-orin-devkit.conf) to ensure that the NVMe device is properly configured and enabled.
  3. Firmware Issues: Ensure that the NVMe device firmware is up-to-date and compatible with the Jetson AGX Orin module.
  4. Software Issues: Verify that the flashing software and tools are up-to-date and compatible with the Jetson AGX Orin module.

Troubleshooting Steps:

  1. Review Log Files: Analyze the provided log files (nvmeflashtimeoutlog.log and seriallognvemetimeoutlog.log) to identify any error messages or patterns that may indicate the root cause of the issue.
  2. Check NVMe Device: Verify that the NVMe device is properly recognized by the Jetson AGX Orin module. You can use tools like nvme list or nvme id-ctrl to check the device status.
  3. Update Firmware: If the NVMe device firmware is outdated, update it to the latest version.
  4. Reflash the Device: Try reflashing the device using the flash.sh command with the --nvme option to specify the NVMe device.
  5. Check Flashing Configuration: Review the flashing configuration file (jetson-agx-orin-devkit.conf) to ensure that the NVMe device is properly configured and enabled.

Comparison with Other Jetson Modules:

The provided information does not mention any specific differences between the Jetson AGX Orin module and other Jetson modules. However, it’s worth noting that the flashing process and configuration may vary between different Jetson modules.

For example, the jetson-agx-xavier-devkit.conf file is used for flashing the Jetson AGX Xavier Developer Kit, while the jetson-agx-orin-devkit.conf file is used for flashing the Jetson AGX Orin Developer Kit. Ensure that you are using the correct configuration file for your specific Jetson module.

In summary, the NVMe timeout error during the flashing process on a Jetson AGX Orin series system may be caused by hardware, flashing configuration, firmware, or software issues. Reviewing the log files, checking the NVMe device, updating firmware, reflashing the device, and checking the flashing configuration are potential troubleshooting steps.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Hi,

What is your flashing command?
Please provide the commands for us to review.

Thanks

5

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-agx-orin-devkit-industrial external

6

Hi,

What is your ubuntu version?
Is your ubuntu a native or a virtual machine?

Please add --erase-all in the command to cross check issue.

Thanks

9

Hi,

@DavidDDD

console-lof-nvme-flashing-err.log (153.6 KB)

nvme-flashing-err.log (331.3 KB)

We are one again facing NVMe flashing error.

Pls find theflashing log and console log attached FYI.

Thanks,

Nagesh R

10

ubuntu 20.04. Same Host pC used an working from 4 years.

It is not virtual machine.

I tried –erase-all but still flashing failing. Erase-all command is not taking effect I suppose.

pls find the log for your reference.

erase-all-not-working-flash-nvme.log (16.6 KB)

also we are getting below nvme error in console log during flashing:

insmod /lib/modules/5.15.148-tegra/kern verify_rate_range: FMON_PWM3: rate 1100
fmon_update_config: FMON_PWM3: detected fault 0x80
el/drivers/nvme/host/nvme-core.ko
insmod /lib/modules/5.15.148-tegra/kernel/drivers/nvme/host/nvme.ko
[ 9.615431] nvme 0005:01:00.0: Adding to iommu group 7
[ 9.615787] nvme nvme0: pci function 0005:01:00.0
[ 9.616014] nvme 0005:01:00.0: enabling device (0000 → 0002)
[ 9.619716] nvme nvme0: missing or invalid SUBNQN field.
[ 9.622831] nvme nvme0: allocated 16 MiB host memory buffer.
[ insmod.62494 /l6] mods/5.15.14nvmegrvme0: 8/0/0 erndefauldris/tt/r/poll malq3
2834] nvme0n1: p1
insmod /lib/modules/5.15.148-tegra/kernel/drivers/pwm/pwm-tegra.ko
insmod /lib/modules/5.15.148-tegra/kernel/drivers/hwmon/pwm-fan.ko
insmod /lib/modules/5.15.148-tegra/kernel/drivers/usb/gadget/libcomposite.ko

Also just want to inform that, FYI.. we have changed the flashing USB port to “host” mode in device tree.

It was told, it works even though it is changed to “host” mode as the recovery mode is set in hardware. Please confirm this. As the onboard eMMC flashing is working fine.

11

Hi,

Please refer to below topics No Known UDC device found in massflash - #15 by WayneWWW?

device mode is needed.

Thanks