Backup massflash failed

Hello, I want to back up the image of AGX orin 32G core module EMMC on our self-developed carrier board.

My current version of the system on the box is jetpack5.1

I have successfully backed up the system by referring to the link below, but now we can only brush one machine at a time, and now we want to brush the machine in batches.
How do I backup and clone Orin - Jetson & Embedded Systems / Jetson AGX Orin - NVIDIA Developer Forums

Then I refer to the link below, when massflash backup, I have the following error.
Flash Orin 32G fail - Jetson & Embedded Systems / Jetson AGX Orin - NVIDIA Developer Forums
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Timeout
Cleaning up…

  • I see the following error in the debugging serial port.

eht_idx_find: 0xaaaaaaaa not a valid code address
no eidx for 0xaaaaaaaa
I/TC: OP-TEE version: 3.19 (gcc version 9.3.0 (Buildroot 2020.08)) #2 Tue Jan 24 23:20:42 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check Porting guidelines — OP-TEE documentation documentation
I/TC: Primary CPU initializing
I/TC: WARNING: Test OEM keys are being used!
I/TC: This is only for TZ-SE testing and should NOT be used for a shipping product!
I/TC: Primary CPU switching to normal world boot
ERROR: camera-ip/isp5/isp5.c:1977 [isp5_pm_init] “ERROR: Failed to turn isp power on”
BUG: core/init/init.c:85 [init_all] “*** FIRMWARE INIT FAILED AT LEVEL 95 ***”

Jetson UEFI firmware (version 2.1-32413640 built on 2023-01-24T23:12:27+00:00)

But in fact, this problem has been solved by referring to the link below. It is completely no problem when I power on the system normally, and this problem only occurs when I backup the system. I would like to ask what causes it.
ISP power on issue cause Orin boot failed - Jetson & Embedded Systems / Jetson AGX Orin - NVIDIA Developer Forums

  • As attachments, I have attached the log and serial port log during backup.

Please upgrade to jp5.1.1 for some known issue in bpmp dtb which will lead to ODMDATA fails to get updated.

The current version, is already integrated with the algorithm version. It’s already in the mass production stage. Is there a solution to this in the current version?

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