Hello NVIDIA team,
I am currently working with a Jetson AGX Orin Industrial 64GB Developer Kit and have encountered an issue that I believe is related to the EEPROM located at I2C address 0x50
. While testing with the i2cset
utility, I may have unintentionally modified the EEPROM content. As a result, the board is no longer booting properly.
After running the command sudo i2cdump -y 0 0x50
, I obtained the following data dump from the EEPROM:
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 02 00 fe 00 00 00 00 00 00 00 00 00 00 00 00 00 ?.?..
10: 01 00 00 0a 36 39 39 2d 31 33 37 30 31 2d 30 30 ?..?699-13701-00
20: 30 35 2d 35 30 31 20 47 2e 30 00 00 00 00 00 00 05-501 G.0…
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
40: 00 00 00 00 4e 12 28 66 6d 3c 31 34 32 30 32 32 …N?(fm<142022
50: 35 30 32 33 39 35 33 00 00 00 00 00 00 00 00 00 5023953…
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
90: 00 00 00 00 00 00 4e 56 43 42 00 00 4d 31 00 00 …NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 4e 12 28 66 …N?(f
b0: 6d 3c 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 m<?..
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 da …?
After this possible corruption, I noticed several issues:
- The board no longer outputs anything via HDMI.
- The Ethernet interface is not functioning.
- However, I am still able to boot and access the device through the serial (UART) interface using a host PC.
Additionally, when I attempt to flash JetPack 6.2 using NVIDIA SDK Manager, the flashing process fails with EEPROM-related errors. Below are excerpts from the log output:
15:49:39 ERROR: Flash Jetson Linux - flash: — Parsing board ID (ERROR: calculated CRC8 0x66 != stored CRC8 0xda) succeeded.
15:49:39 ERROR: Flash Jetson Linux - flash: — Parsing board version (ERROR: calculated CRC8 0x66 != stored CRC8 0xda) succeeded.
15:49:39 ERROR: Flash Jetson Linux - flash: — Parsing board SKU (ERROR: calculated CRC8 0x66 != stored CRC8 0xda) succeeded.
15:49:39 ERROR: Flash Jetson Linux - flash: — Parsing board REV (ERROR: calculated CRC8 0x66 != stored CRC8 0xda) succeeded.
15:49:39 ERROR: Flash Jetson Linux - flash: Error: Target board not found.
15:49:39 ERROR: Flash Jetson Linux - flash: [exec_command]: /bin/bash -c /home/muralichikkanna/.nvsdkm/replays/scripts/JetPack_6.2_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: Error: Target board not found.
15:49:39 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
15:49:39 INFO: Flash Jetson Linux - flash: [host] [ 1.86 MB used. Disk Avail on Partition /dev/sda2: 749.44 GB ]
15:49:39 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 3s ]
15:49:39 ERROR: command error code: 11
15:49:39 ERROR: Flash Jetson Linux - flash: command terminated with error
15:49:39 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.
15:49:39 SUMMARY: Multimedia API - target: Depends on failed component
15:49:39 SUMMARY: TensorRT Runtime - target: Depends on failed component
15:49:39 SUMMARY: CUDA Runtime - target: Depends on failed component
15:49:39 SUMMARY: CuDNN Runtime - target: Depends on failed component
15:49:39 SUMMARY: OpenCV Runtime - target: Depends on failed component
15:49:39 SUMMARY: VPI Runtime - target: Depends on failed component
15:49:39 SUMMARY: CuPVA Runtime - target: Depends on failed component
15:49:39 SUMMARY: NVIDIA Container Runtime with Docker integration (Beta) - target: Depends on failed component
From this output, it’s evident that the EEPROM corruption is preventing the board from being properly identified, which in turn blocks the JetPack flashing process.
I would like to request the following assistance:
- Can someone from NVIDIA confirm whether the EEPROM dump shown above is valid for the Jetson AGX Orin Industrial 64GB Developer Kit?
- If it is invalid, could you kindly share the correct EEPROM content or a reference dump for this board variant?
- Is there an official method or supported tool to reprogram or restore the EEPROM data (via serial, recovery mode, or another safe method)?
Your guidance in restoring the EEPROM and recovering full functionality of the board would be highly appreciated.
Thank you,
ChandraSekhar