Flashing Jetson Orin Nano – File rcm_state open failed, Error: failed to read rcm_state

Issue Overview

Users are experiencing a failure when attempting to flash the Nvidia Jetson Orin Nano Dev board using custom keys for Secure Boot and encryption. The specific error reported is "rcm_state open failed, Error: failed to read rcm_state." This issue arises during the flashing process after successfully generating and burning custom keys.

Symptoms:

• The flashing process fails with the mentioned error when using custom keys.
• Successful flashes occur when using default keys.

Context:

• The problem occurs during the flashing phase after executing commands for key generation and fuse burning.
• Users have attempted to flash with both the --test option and without it.

Hardware/Software Specifications:

• Nvidia Jetson Orin Nano Dev board
• Tools and scripts from the Jetson Linux Driver Package (L4T)
• Custom RSA and SBK keys generated via OpenSSL

Frequency of Issue:

This issue appears to be consistent among users attempting to implement custom key configurations for Secure Boot.

Impact on User Experience:

The inability to use custom keys severely limits the security features that users can implement, impacting their project goals related to Secure Boot and encryption.

Possible Causes

• Hardware Incompatibilities or Defects: Issues with the Jetson board itself may prevent proper communication during the flashing process.

• Software Bugs or Conflicts: There may be bugs in the flashing scripts or conflicts with existing software versions that affect key handling.

• Configuration Errors: Incorrect parameters or options in the flashing commands could lead to failures in reading or writing necessary states.

• Driver Issues: Outdated or incompatible drivers may hinder proper operation during the flashing process.

• Environmental Factors: Power supply inconsistencies or overheating could affect the board’s ability to flash correctly.

• User Errors or Misconfigurations: Incorrectly generated keys or improperly executed commands may lead to failure in the flashing process.

Troubleshooting Steps, Solutions & Fixes

1. Verify Key Generation and Fuse Burning:

   • Ensure that RSA and SBK keys are correctly generated.
   • Confirm that fuses have been successfully burned without errors.
   • Use the command:

     sudo ./odmfuse.sh --test -X ./fuse.xml -i 0x23 -k ./rsa.pem -S ./sbk.key jetson-orin-nano-devkit
     

2. Remove Test Options:

   • If fuses were burned using --test, try removing this option before attempting to flash again.

3. Use Correct Flashing Commands:

   • Follow these commands for a structured approach:

     sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" -u rsa_priv-3k.pem -v sbk.key --showlogs --network usb0 jetson-orin-nano-devkit internal
     

   • For actual flashing:

     sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only -u rsa_priv-3k.pem -v sbk.key jetson-orin-nano-devkit internal
     

4. Check Documentation:

   • Refer to the Nvidia Developer Guide for detailed instructions on signing and flashing with initrd using l4t_initrd_flash.sh.

5. Test Different Configurations:

   • Attempt to flash without including the EKB key as suggested by other users in the forum discussion.

6. Update Drivers and Firmware:

   • Ensure that all drivers are up-to-date and compatible with your version of L4T.

7. Monitor Environmental Conditions:

   • Check power supply stability and ensure adequate cooling for the device during operation.

8. Log Examination:

   • Review log files generated during the flashing process for any additional clues regarding failures.

9. Community Support:

   • Engage with community forums for further insights or similar experiences shared by other users.

10. Unresolved Aspects:

    • Further investigation may be needed into specific configurations of custom keys that lead to failures, as well as potential updates from Nvidia regarding known issues with certain versions of their software tools.

By following these troubleshooting steps, users should be able to diagnose and potentially resolve issues related to flashing the Jetson Orin Nano Dev board with custom keys effectively.