Flashing Error on Jetson AGX Orin Industrial SOM

Hello Team,

We are currently working with the NVIDIA Jetson AGX Orin Industrial (0008) SOM on our custom board, using L4T R35.5.0.

we are using the following command:
sudo ./flash.sh jetson-agx-orin-devkit-industrial mmcblk0p1

However, each time we attempt to flash the board, we encounter the following error:

[ 565.1714 ] Writing partition APP with system.img [ 5925689140 bytes ]
Error: Return value 3........                                 ] 031%
Command tegradevflash_v2 --pt flash.xml.bin --create
Failed flashing t186ref.
Command exited with non-zero status 1

Could you please provide clarification on what this error means and how we can resolve it?

Thank you for your assistance.

Regards
Parashuram

Try rel-35.6 first.

Hello Wayne,

Thank you for your reply.

We did our development with the R35.5.0 release and have successfully flashed the system multiple times without any issues. However, we are now encountering a flashing error that we haven’t seen before.

We would like to continue using the R35.5.0 package. Could you please provide guidance on how to resolve this issue?

Thank you for your support.

Regards,
Parashuram

Then what is changed here? Does this issue happen because you changed something?
What is the variable here? The module changed? The carrier board changed? The software changed?

Does same module work on NV devkit?

You should clarify this first.

Hello Wayne,

We are using the same build for both the commercial SOM and the industrial SOM. The flashing process works fine on the commercial SOM, but we are encountering issues with the industrial SOM. Previously, the industrial SOM was also flashing successfully with this build, but we are now facing this issue unexpectedly.

For commercial som flash command:

sudo ./flash.sh Jetson-agx-orin-devkit mmcblk0p1

For industrial som
sudo ./flash.sh Jetson-agx-orin-devkit-industrial mmcblk0p1

Regards,
Parashuram

Any UART log during flash failure could be shared?

the industrial SOM was also flashing successfully with this build, but we are now facing this issue unexpectedly.

Then would it pass if you try to flash more times?

Could you put same module to NV devkit and reproduce this issue?

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