Failed to flash my new AGX Orin module with R35.1

[hemz]

Hi, experts.
we have recently procured a new batch of AGX Orin module, but they can’t to flash by flash.sh in R35.1, I’m very sure that the old batch of AGX Orin module can flash with R35.1.
I just run:
sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1
And the log information is as follows:

flash_log.txt (60.3 KB)

uart_log.txt (8.5 KB)

What should I do?
Thank you.

[carolyuu]

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing issues flashing a new batch of Jetson AGX Orin modules using the flash.sh command in R35.1. You’ve mentioned that the old batch of AGX Orin modules could be flashed successfully with R35.1, but the new batch is not working.

To troubleshoot this issue, I recommend the following steps:

1. Verify the configuration file: Ensure that you are using the correct configuration file for the Jetson AGX Orin module. According to the provided context, the correct configuration file for the Jetson AGX Orin Developer Kit is jetson-agx-orin-devkit.conf. Make sure that this file is present in the extracted Jetson Linux release directory and that it is being used during the flashing process.
2. Check the flashing command: Verify that the flashing command is correct. The provided context suggests that the correct command for flashing the Jetson AGX Orin module is:

   # sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1
   

   Make sure that you are using the correct command and that the mmcblk0p1 parameter is correct for your specific use case.
3. Review the log files: You’ve mentioned that you have log files (flashlog.txt and uartlog.txt) that may contain information about the flashing process. Review these log files to see if they provide any clues about what might be going wrong during the flashing process.
4. Compare the old and new batches: Since the old batch of AGX Orin modules could be flashed successfully with R35.1, it’s possible that there is a difference between the old and new batches that is causing the issue. Compare the two batches to see if there are any differences in the hardware, software, or configuration that could be contributing to the problem.
5. Try a different flashing method: If the above steps do not resolve the issue, you may want to try a different flashing method. The provided context mentions an alternative flashing method using the l4t_initrd_flash.sh script. You can try using this script to flash the module:

   $ sudo ./tools/kernel_flash/l4t_initrd_flash.sh -u <pkc_keyfile> [-v <sbk_keyfile>] --uefi-keys uefi_keys/uefi_keys.conf jetson-agx-orin-devkit internal
   

   Replace <pkc_keyfile> and <sbk_keyfile> with the actual file names and paths for your specific use case.

By following these steps, you should be able to troubleshoot and resolve the issue with flashing the new batch of Jetson AGX Orin modules.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

[hemz]

Hi,
I followed these steps:

 1. yes, jetson-agx-orin-devkit.conf file exists.

 2. command is correct.

 3 & 4. I compared the log files with old AGX Orin module, I found that the ram code and Board ID are different.

The following are the log files of my old AGX Orin module (It can flash successfully):

flash_log(old module).txt (766.2 KB)

uart_log(old module).txt (22.3 KB)

Furthermore, I tried this link:

Not able to flash

Hi, [ 0.2967 ] Sending bct_br [ 0.3478 ] ERROR: might be timeout in USB write. Error: Return value 3 The log means you should do this:

And I download the patch (overlay_xusb_35.3.1.tbz2), it corresponds to R35.3.1, but my bsp version is R35.1. this maight be the reason why it’s not working?

[   2.6714 ] Sending bct_mem
[   2.7152 ] Sending blob

[   2.7530 ] ERROR: might be timeout in USB write.

Error: Return value 3
Command tegrarcm_v2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Failed flashing t186ref.

So, How do i solve the problem on R35.1?

[DavidDDD]

Hi,

Please reach out the pcn download center to get the AGX Orin patch for r35.1.

Thanks

[hemz]

Hi, thanks.

I applied the patches to R 35.1(234-pcn210100-pcn211461-emmc-35.1.tbz2 and t234-dram-package-35.1.0_2024-09-18.tbz2) ,

However, a new issue has come up:

*** Flashing target device started. ***

Failed flashing t186ref.

Traceback (most recent call last):
  File "./tegraflash.py", line 1305, in <module>
    chip = chip.replace('  ', ' ')
AttributeError: 'NoneType' object has no attribute 'replace'

The following are the log files:

flash_log.txt (21.6 KB)

uart_log.txt (4.7 KB)

Furthermore, I noticed that the eMMC patch uses ‘tegra234-p3737-overlay.dtbo’, But I can’t find it in R35.1:

And i just found these two dtbo files:

Can you give me some advice ?

[hemz]

I think I’ve found the cause of the problem: I’m still missing a patch.

https://developer.nvidia.com/embedded/jetson-linux-r351

Now, I can flash my new AGX module (After applying all 3 patches).

Thank you.