Issue Flashing Production Modules with Jetpack SDK 35.3.1 (Jetpack 5.1.1)

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
, ,
1

Hi,

I’ve been successfully using a Linux image based on Jetpack SDK 35.3.1 (Jetpack 5.1.1) configured for production purposes. This image has been used extensively in production environments with previous Jetson modules without any issues.

Recently, we received new batches of production Jetson modules, and I’m experiencing issues when attempting to flash these modules using SDK version 35.3.1. The specific error I’m encountering is as follows:

> [   0.3132 ] Sending blob
> [   0.4391 ] ERROR: might be timeout in USB write.
> Error: Return value 3
> Command tegrarcm_v2 --instance 1-2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin

The commands used to flash are:

  • For SDK 35.3.1:
> sudo ./tools/kernel_flash/l4t_initrd_flash.sh -p "--no-systemimg -c bootloader/t186ref/cfg/flash_t234_qspi.xml" --network usb0 jetson-orin-nano-devkit internal
  • For SDK 36.4.3:
> sudo ./tools/kernel_flash/l4t_initrd_flash.sh -p "--no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml" --network usb0 jetson-orin-nano-devkit internal

The key issue is that using SDK 36.4.3, the flashing process completes successfully, but the module fails to boot my existing Linux image (built with SDK 35.3.1). My host system is Ubuntu 22.04 with an ext4 filesystem, and as mentioned, the issue clearly seems related to the SDK version compatibility with these newer modules.

Due to the extensive configuration, installed libraries, and cross-compiling setups we have on this SDK 35.3.1 image, updating to SDK 36.4.3 is not feasible at this moment as it would require significant time and resources.

Here are my specific questions:

  1. Can you confirm that if I flash QSPI using SDK 36.4.3, it will indeed be unable to boot the image made originally with SDK 35.3.1?
  2. Is there a way to fully extract the working QSPI image from a module previously flashed successfully with SDK 35.3.1 and then directly flash this extracted QSPI image onto the new production modules using the latest SDK (36.4.3) without any compilation steps?
  3. Given my tight production timeline and the inability to rebuild the entire setup quickly, what options do I have to make these new modules compatible with SDK 35.3.1?
  4. Could this issue be related to something I’ve read about certain modules having a modified fuse pre-programmed at the factory?

Attached are the logs showing:

Thank you very much in advance for your support and prompt response.

Best Regards.

2

Hi,
You should be using new PCN. Please go to download center and check Jetson PCN Summary:
Jetson Download Center | NVIDIA Developer

Please check which PCN you use and whether there’s overlay package for Jetpack 5.1.1

1 Like
3

Hi.

Applying the patch to the Jetson dev kit with Jetpack 5.1.1 worked perfectly.

Thank you for your support!

Best regards.

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.