**FATAL ERROR from Bootloader when flashing from massflashblob**

Issue Overview

Users are experiencing a FATAL ERROR during the boot process after attempting to flash the Nvidia Jetson Orin Nano Dev board using the massflashblob method in the R36.2.0 environment. The specific symptoms include:

• The boot process halts at UEFI, displaying the error message:

  FATAL ERROR [FILE=platform/top/bpmp/startup/sku.c, ERR_UID=598]: chip sku 0xd5 not in <nv>/sku/te980m_0
  

• Additional errors related to camera initialization:

  ERROR: camera-ip/isp5/isp5.c:2031 [isp5_pm_init] "ERROR: Failed to turn isp1 power on"
  

• A firmware initialization failure:

  BUG: core/init/init.c:86 [init_all] "*** FIRMWARE INIT FAILED AT LEVEL 95 ***"
  

This issue occurs specifically when users attempt to flash using the massflashblob method after modifying the bootloader configuration for EEPROM. In contrast, flashing directly without the massflashblob does not result in any errors, indicating that the problem is likely tied to the massflash process.

Context and Specifications

• Hardware:

  • Orin Nano EVK (p3768-000)
  • Orin Nano 8GB CPU Module (p3767-0003)
  • NVMe SSD

• Software:

  • Jetson Linux R36.2.0

The issue appears to be consistent across different setups, as multiple users have reported similar errors when using both custom and standard configurations.

Possible Causes

Several potential causes for this issue have been identified:

• Hardware Incompatibilities: The chip SKU error suggests a mismatch between the hardware configuration and the expected firmware.

• Software Bugs or Conflicts: There may be bugs in the R36.2.0 software version that affect the massflash process.

• Configuration Errors: Incorrect modifications to bootloader settings or EEPROM configurations could lead to initialization failures.

• Driver Issues: Outdated or incompatible drivers may cause conflicts during the flashing process.

• Environmental Factors: Power supply issues or temperature fluctuations could impact the stability of the flashing operation.

• User Errors or Misconfigurations: Incorrect command usage or parameters during the flashing process might lead to these errors.

Troubleshooting Steps, Solutions & Fixes

To address this issue, follow these comprehensive troubleshooting steps and potential solutions:

Step-by-Step Instructions

1. Verify Hardware Configuration

   • Ensure that all hardware components are compatible and correctly connected.

2. Check Software Version

   • Confirm that you are using a clean version of Jetson Linux R36.2.0 without any modifications.
   • If necessary, download a fresh copy from NVIDIA’s official site.

3. Modify Bootloader Configuration

   • Follow these steps to modify the bootloader dtsi for EEPROM:

     cd Linux_for_Tegra/bootloader
     sudo nano tegra234-mb2-bct-common.dtsi
     

   • Change:

     cvb_eeprom_read_size = <0x100>
     

     To:

     cvb_eeprom_read_size = <0x0>
     

4. Create Massflashblob

   • Execute the following commands to create a massflashblob:

     TARGET_CONF=p3768-0000-p3767-0000-a0
     ROOTFS_SIZE=$((8*1024*1024*1024))
     
     sudo BOARDID=3767 BOARDSKU=0003 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \
         --external-device nvme0n1p1 \
         -S ${ROOTFS_SIZE} \
         -c tools/kernel_flash/flash_l4t_external.xml \
         -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
         --massflash 5 \
         --showlogs \
         --network usb0 \
         ${TARGET_CONF} \
         nvme0n1p1
     

5. Flash from Massflashblob

   • Use this command to initiate flashing:

     time sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5
     

6. Check Logs for Errors

   • After executing the flash command, review log files located in Linux_for_Tegra/initrdlog/ for any ongoing processes or errors.

Recommended Approaches

• If issues persist, consider testing on different development kits (DevKits) as some users reported that similar errors occurred even when using standard configurations.

• Ensure that all commands are executed with appropriate permissions (using sudo).

Best Practices

• Always use a clean BSP (Board Support Package) from NVIDIA for testing.

• Regularly check for updates or patches from NVIDIA that may address known bugs in specific software versions.

Unresolved Aspects

While many users have successfully followed these steps, further investigation may be required regarding specific hardware configurations or environmental factors affecting individual setups. Additionally, users should remain vigilant for updates from NVIDIA that might resolve underlying software issues causing these errors.