Jetson Orin NX 16GB (900-13767-0000-0A1) incompatibility with JetPack 5.1.2 / L4T 35.x

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

Module:

  • Jetson Orin NX 16GB
  • P/N: 900-13767-0000-0A1

JetPack Version:

  • 5.1.2 (L4T 35.4.1)

Machine:

- Ubuntu 22.04.5 LTS

Issue:

- ERROR: might be timeout in USB write.

  • AI says new DRAM chips used in 0A1 that were not used in 0A0 variants are not defined in older Jetpacks so USB transfer fails. This is NOT an issue autosuspend as that has already been disabled on my system and the same process works on 0A0 Jetsons.

Steps to reproduce:

  1. Flash using:
    sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal

Logs:

2

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

The issue you’re experiencing with the Jetson Orin NX Module (PN 900-13767-0000-A1) and JetPack Version 5.1.2, L4T 35.4.1, is related to the new DRAM chips used in the 0A1 variant, which are not defined in older Jetpacks. This causes the USB transfer to fail.

To resolve this issue, you can try the following steps:

  1. Update to the latest Jetpack version: Ensure that you’re running the latest Jetpack version, which should include support for the new DRAM chips used in the 0A1 variant. You can check for updates using the sudo apt-get update and sudo apt-get upgrade commands.
  2. Use the SKIP_EEPROM_CHECK flag: As mentioned in the documentation, you can try flashing the device using the SKIP_EEPROM_CHECK flag to skip the EEPROM read during flashing. This can be done by running the following command:
$sudo SKIP_EEPROM_CHECK=1 BOARDID=<BOARDID> BOARDSKU=<BOARDSKU> ./flash.sh <board> <rootdev>

Replace <BOARDID> and <BOARDSKU> with the values specific to your device.

  1. Correct the EEPROM content: If the above steps don’t work, you may need to correct the EEPROM content manually. You can use the Linux i2c-tools to dump the complete EEPROM content, calculate the CRC8 value, and write the correct value to byte 255 in EEPROM. Refer to the Jetson EEPROM Layout documentation for more information on this process.

In comparison to the 0A0 variant, the 0A1 variant uses new DRAM chips that are not defined in older Jetpacks. This is the root cause of the issue you’re experiencing. By updating to the latest Jetpack version or using the SKIP_EEPROM_CHECK flag, you should be able to resolve the issue and successfully flash the device.

Additionally, it’s worth noting that the autosuspend issue is not related to the problem you’re experiencing, as you’ve already disabled autosuspend on your system. The issue is specific to the new DRAM chips used in the 0A1 variant.

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

3

Guessing that’s due to PCN212822, please apply the overlay patch for your JetPack 5.1.2 from Jetson PCN Download Center | NVIDIA Developer