Flashing L4T35.4.1 to orin nx 8GB SOM fails

Hello, we tried to flash jetson orin nx 8gb SOM using the orin nano developer kit.But the flash fails with the following error.

We also tried flashing with SDK Manager (JETPACK 6.0) but still it fails.Herewith i have attached the logs of both SDK manager and UART.Kindly help me to resolve this issue.
JP6.0_SDK_UARTLOG.log (8.5 KB)
SDKM_logs_JetPack_6.0_(rev._1)_Linux_for_Jetson_Orin_NX_modules_2024-05-21_18-09-19.zip (45.6 KB)

Hi,

I have seen this error in the past. In my case the USB timeout was causing the port to go to sleep. Remove the timeout and reboot:

sudo sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT="[a-z ]*/& usbcore.autosuspend=-1/' \
    /etc/default/grub
sudo update-grub2
reboot

I also had to disable ufw because it was blocking a different part of the installation. Disable the firewall temporarily, and re-enable it after the installation:

sudo ufw disable
# Flash the board
sudo ufw enable

Hi,
Thankyou @miguel.taylor for your valuable input.But the issue we are facing is related to EEPROM read failure and not USB timeout error.

Hi,

In my case, I was getting the exact same EEPROM read error, which was caused by the USB timeout. I think it is a common issue on Ubuntu 20.04.

You can also try the solution from this post, which involves skipping the EEPROM read and setting the values manually, but in my case, it didn’t help.

Hi,
I have tried the solution given, but the issue is not resolved.I am getting the same EEPROM error.

Are you using VM or host PC with Ubuntu OS?

I am using host PC with Ubuntu OS(version:22.04.3)

The EEPROM is corrupted.
Find the Linux_for_Tegra folder on your host PC, and do

sudo BOARDID=3767 BOARDSKU=0001 FAB=300 \
./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” \
–showlogs --network usb0 jetson-orin-nano-devkit internal

Then after you can flash your device and it boots up, follow this post to correct the EEPROM:

I am getting the below error , when I execute the initrd.sh flash command to flash as shown below. Is EEPROM of my orion NX 16 GB SOM is also corrupt?

/home/trident/Downloads/r36_3_0/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -p -c ./bootloader/generic/cfg/flash_t234_qspi.xml -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1

  •                          *
    
* Step 1: Generate flash packages *
* ```
                            *

Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY=“” /home/trident/Downloads/r36_3_0/Linux_for_Tegra/flash.sh --no-flash --sign -c ./bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit nvme0n1p1

###############################################################################

L4T BSP Information:

R36 , REVISION: 3.0

User release: 0.0

###############################################################################
ECID is
Board ID() version() sku() revision()
Chip SKU(00:00:00:D3) ramcode() fuselevel(fuselevel_production) board_FAB()
emc_opt_disable_fuse:(0)
Error: Unrecognized module SKU
Error: failed to generate images
Cleaning up…

what are values for BOARDSKU and FAB for my Orion NX 16GB module?

That means the deivce is not even detected to be in force recovery mode.

Thankyou @DaveYYY @kayccc
The issue has been solved .

But we see, it list “NVidia Corp” when we run lsusb command…

@nagesh_accord
Please don’t mix up unrelated things in other people’s posts.
Your issue should be handled here:

Ok…