JON Jetpack 5.1.5 SDK Manager Flash Failure -- HELP PLS

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi I received 3 JON 8GB Developer’s kits with installed Jetpack 6.2.1, then I used SDK Manager on Ubuntu 20.04 to rollback to Jetpack 5.1.5 on all 3 sets because of the required environment for software I’m running.

After successfully rolling back all 3 sets, I proceeded to install the prop software on all 3, however I installed wrong software (x86 packages) onto the 3rd set, and the prop software wouldn’t run. When I tried to reflash the 3rd set back to a clean Jetpack 5.1.5 onto the NVME from SDK Manager, I keep encountering failures. The other 2 (no wrong software installed) sets run fine and don’t have to be reflashed.

I’ve attached my error log from SDK manager, can someone please help to figure out what’s wrong and point me to a resource I can use to rectify this error? You time and help is much appreciated!

NVIDIA Jetson Orin Nano SDK Manager Error Log.txt (7.7 KB)

2

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

The issue you’re experiencing with the Jetson Orin Nano (JON) 8GB Developer Kit is related to reflashing the device back to a clean Jetpack 5.1.5 installation after installing wrong software (x86 packages) on the third set. Despite successfully rolling back all three sets from Jetpack 6.2.1 to Jetpack 5.1.5 using the SDK Manager, the attempt to reflash the third set to a clean Jetpack 5.1.5 installation on the NVME from SDK Manager resulted in failures.

To address this issue, let’s break down the steps and considerations:

  1. Understanding the Environment: You initially had Jetpack 6.2.1 installed on all three JON 8GB Developer Kits. You then rolled back to Jetpack 5.1.5 due to software environment requirements. This rollback was successful on all three kits.

  2. Installing Wrong Software: On the third kit, you installed x86 packages, which are not compatible with the ARM-based Jetson Orin Nano. This is likely the root cause of your issue, as the wrong architecture packages can cause system instability and prevent proper flashing.

  3. Reflashing Attempts: Your attempts to reflash the third kit back to a clean Jetpack 5.1.5 installation using the SDK Manager have failed. This could be due to several reasons, including but not limited to:

    • Corrupted File System: The installation of x86 packages might have corrupted the file system or critical system files, preventing a clean reflash.
    • Incompatible Packages: The presence of x86 packages might interfere with the reflashing process, which expects a specific environment compatible with the Jetson Orin Nano.

  4. Troubleshooting Steps:

    • Manual Cleanup: Before attempting to reflash, try to manually remove any traces of the x86 packages from the system. This might involve using the package manager to remove packages or manually deleting files related to the x86 software.
    • Recovery Mode: Consider putting the Jetson Orin Nano into recovery mode and then attempting to reflash it. Recovery mode allows for a more direct access to the device’s boot loader, which might help in overcoming the issues caused by the wrong packages.
    • Check NVME Health: Ensure that the NVME drive is healthy and not causing issues. Sometimes, storage problems can lead to flashing failures.
    • Refer to Official Documentation: NVIDIA provides extensive documentation and forums where similar issues might have been discussed. Checking the official NVIDIA Jetson forums or documentation for troubleshooting guides related to reflashing and recovery might provide specific solutions.

  5. Comparison with Other Kits: The fact that the other two kits, which did not have the wrong software installed, run fine and do not need to be reflashed, suggests that the issue is indeed related to the installation of x86 packages on the third kit.

  6. Resource Utilization:

    • NVIDIA Forums and Documentation: Utilize NVIDIA’s official resources, including forums and documentation, for troubleshooting and guides on reflashing the Jetson Orin Nano.
    • Jetson Developer Community: The Jetson developer community might have encountered similar issues and could provide valuable insights or solutions.

In conclusion, the key steps to resolve the issue involve identifying and removing the incompatible x86 packages, ensuring the system is in a recoverable state, and then attempting to reflash the device using the SDK Manager. If issues persist, consulting official NVIDIA resources and community forums for specific troubleshooting steps related to the Jetson Orin Nano and reflashing procedures is recommended.

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

3

I’ve manually uninstalled all related packages as far as I can tell using Synaptic Package Manager and still have the issue. Can someone please look through the error logs and advise?

5

Hi
For your log:

(ERROR: calculated CRC8 0x4a != stored CRC8 0xfa)

Your eeprom crc seems to be changed.
Do you run i2cwrite command to change the value?

Please use command cat /etc/nv_boot_control.conf or doc on your normal device to get the board config.

And use below commands under the ~/nvidia/nvidia_sdk/JetPack_5.1.5_Linux

$sudo SKIP_EEPROM_CHECK=1 BOARDID=<BOARDID> BOARDSKU=<BOARDSKU> ./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 jetson-orin-nano-devkit internal

Thanks

6

Thank you I will try that and get back to you

7

您好修复了吗发一下操作过程把，感谢老外朋友

8

@DavidDDD it worked like a charm! Thank you for your help, really appreciate it.

9

是的，它非常有效。