I tried flashing my NVIDIA Jetson Orin Nano Super Developer Kit, which has a 1TB NVMe, using SDK Manager. The OS flashing completes successfully, but after that the device is no longer recognized over the USB-C connection.
I also tried flashing via SD card, using both SDK Manager and BalenaEtcher, but the issue remains.
Even after updating all L4T packages, the device still does not work correctly.
Checking the logs with dmesg shows the following errors:
[ 9.257911] tegra-i2c c240000.i2c: un-recovered arbitration lost
[ 9.257919] ina3221 1-0040: Unable to reset device
[ 9.257957] ina3221: probe of 1-0040 failed with error -5
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are experiencing issues with flashing your NVIDIA Jetson Orin Nano Super Developer Kit, specifically with the device not being recognized over the USB-C connection after flashing. You have tried flashing using SDK Manager and BalenaEtcher, but the issue persists.
To troubleshoot this issue, let’s break down the possible causes and potential solutions:
Flashing configuration: Ensure that you are using the correct flashing configuration file for your Jetson Orin Nano Developer Kit with the Orin Nano or the Orin NX modules with Super profile. The provided context mentions jetson-orin-nano-devkit-super-nvme.conf as the configuration file for this specific setup.
Flashing command: Verify that you are using the correct flashing command. The provided context shows an example of flashing the device using l4t_initrd_flash.sh with the --external-device option set to nvme0n1p1. Make sure you are using the correct device identifier for your NVMe drive.
UEFI settings: Check the UEFI settings on your Jetson Orin Nano Developer Kit to ensure that the boot order is set correctly. You may need to select the NVMe drive as the boot option from the UEFI menu.
Kernel and Bootloader payloads: Ensure that the kernel and Bootloader payloads are generated correctly using l4t_generate_soc_bup.sh. This script generates the payloads based on specifications, so make sure you are using the correct specifications for your Jetson Orin Nano Developer Kit.
Signature header: Verify that the signature header is generated correctly using l4t_sign_image.sh. This script signs and generates the signature header at boot.
Secure boot: Check if secure boot is enabled on your Jetson Orin Nano Developer Kit. If secure boot is enabled, you may need to use l4t_uefi_sign_image.sh to sign and encrypt the images for secure boot.
Comparing the provided context with the issue you are experiencing, it appears that the flashing process completes successfully, but the device is not recognized over the USB-C connection. This suggests that the issue may be related to the UEFI settings or the boot order.
To fix this issue, you can try the following:
Check the UEFI settings on your Jetson Orin Nano Developer Kit to ensure that the boot order is set correctly.
Verify that the NVMe drive is selected as the boot option from the UEFI menu.
Try flashing the device again using the l4t_initrd_flash.sh command with the --external-device option set to nvme0n1p1.
If the issue persists, try using l4t_uefi_sign_image.sh to sign and encrypt the images for secure boot.
If none of these solutions work, you may need to provide more information about your setup and the exact error messages you are seeing to further troubleshoot the issue.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
I have tried all the steps you suggested, but the issue persists. The device still shows the following error:
feb 20 14:24:03 nvidia-jetson kernel: irq: IRQ243: trimming hierarchy from :bus@0:pmc@c360000
feb 20 14:24:03 nvidia-jetson kernel: tegra-i2c c240000.i2c: un-recovered arbitration lost
feb 20 14:24:03 nvidia-jetson kernel: fusb301 1-0025: failed to read device id, err : 0xfffffffb
feb 20 14:24:03 nvidia-jetson kernel: fusb301 1-0025: fusb301 not support
feb 20 14:24:03 nvidia-jetson kernel: fusb301: probe of 1-0025 failed with error -22
Hi, thanks for the suggestions.
I already sent the unit back to the dealer, and they confirmed it was a hardware issue. They replaced the Jetson module.