Flashing stall on custom board

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

When flashing JP7.2 onto the Orin AGX, the process gets stuck at this stage. This is our custom-designed board, and the flashing command we used is
“sudo ./flash.sh jetson-agx-orin-devkit internal”.
How should I troubleshoot this issue?

1c6e901a-9660-46c6-bc84-8f746f0cbd6d
1c6e901a-9660-46c6-bc84-8f746f0cbd6d1302×829 353 KB

and serial port log as follow:

img_v3_0213j_3086908b-2520-483a-90b6-40a9285375cg
img_v3_0213j_3086908b-2520-483a-90b6-40a9285375cg1130×809 177 KB

3

— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —

To troubleshoot the flashing issue on your custom-designed Jetson AGX Orin board, you can try the following steps:

  1. Check the serial console log: Open the serial console before attempting to flash the board. This will help you capture the log and identify any potential issues. You can use a tool like minicom to capture the serial console log.
  2. Verify the flashing command: Ensure that you are using the correct flashing command for your custom board. The command you provided, sudo ./flash.sh jetson-agx-orin-devkit internal, is for the devkit, but you may need to use a different command for your custom board.
  3. Check with your vendor: If you are using a custom board, it’s possible that the vendor has provided a custom image for flashing. Check with your vendor to see if they have any specific instructions or images for flashing your board.
  4. Try a different flashing method: If you are using SDK Manager, try flashing the board using the command-line interface instead. This can help you identify if the issue is specific to SDK Manager or if it’s a more general flashing issue.
  5. Check the board’s hardware: Ensure that the board’s hardware is functioning correctly. Check the power supply, USB connections, and any other peripherals to ensure they are working as expected.

By following these steps, you should be able to troubleshoot the flashing issue on your custom-designed Jetson AGX Orin board.

Note: The provided context does not cover the specific flashing issue on custom boards, but the above steps are general troubleshooting steps that can be applied to flashing issues on Jetson AGX Orin boards.

— We support team will also look into your issue to have further suggestions soon. please stay tuned. —

4

please check if you are using 502 SOM.

5

As I mentioned in this post, it is not failing for all 502 SOM. This issue is only with Kingston EMMC and not all 502 FAB uses Kingston EMMC.

7

We are not using 502 SOM, We use 32GB module, and we do not use nvme. I flash the internal emmc.

img_v3_0213k_32621769-bb69-4244-b661-23f9f25966ag
img_v3_0213k_32621769-bb69-4244-b661-23f9f25966ag932×506 124 KB

9

The 502 SOM issue is not about nvme but only emmc.

Do you have a NV devkit on your side to bypass the factor of your custom board?

10

It’s same in devkit.

20260715-171351
20260715-1713511920×865 192 KB

11

Could you help fall back to rel-36 and share us the info of the emmc?

user@localhost:~$ cat /sys/block/mmcblk0/device/name

12

It’s TY2964

img_v3_0213k_0ee17a7c-4915-4927-a502-4558067cc34g
img_v3_0213k_0ee17a7c-4915-4927-a502-4558067cc34g1920×1080 239 KB

13

Yes, this is same issue as JetPack 7.2 - Flashing fails for module 699-13701-0005-502, works for module 699-13701-0005-501 - #17 by sevm89

Please wait for us to share the new patch to fix this.

17

Please find the patch attached at JetPack 7.2 - Flashing fails for module 699-13701-0005-502, works for module 699-13701-0005-501 - Jetson Systems / Jetson AGX Orin - NVIDIA Developer Forums