Orin module cannot be burned

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

After using the command sudo./flash. sh jetson-agx-orin devkit-industrial mmcblk0p1 to burn an orin module, the print is as follows, but it gets stuck and cannot be moved. Burning another module is normal. What is the problem?

After executing the flash command, log as follows

###############################################################################

L4T BSP Information:

R35 , REVISION: 5.0

User release: 0.0

###############################################################################

2

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

Based on the provided context, it appears that the issue is related to flashing a Jetson AGX Orin module using the flash.sh command. The command used is:

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

The print output indicates that the flashing process is stuck, and the module cannot be moved. However, burning another module is normal.

To troubleshoot this issue, let’s analyze the provided information:

  1. The flash.sh command is used to flash the Jetson AGX Orin module.
  2. The configuration file used is jetson-agx-orin-devkit-industrial.conf.
  3. The module being flashed is an Orin industrial module (P3701-0008) attached to a Jetson Orin reference carrier board (P3737-0000).
  4. The print output shows the L4T BSP Information, which indicates the revision and user release.

Comparing this information with the provided context, we can see that:

  • The jetson-agx-orin-devkit-industrial.conf configuration file is used for flashing the Jetson Orin industrial module.
  • The flash.sh command is used to flash the module, which is consistent with the provided context.
  • The L4T BSP Information indicates that the revision is R35, and the user release is 00, which is consistent with the provided context.

However, the issue seems to be specific to this particular module, as burning another module is normal. This suggests that the problem might be related to the module itself or the flashing process.

To resolve this issue, you can try the following:

  1. Verify that the module is properly connected to the carrier board and that all cables are securely connected.
  2. Check the module’s firmware version and ensure that it is compatible with the jetson-agx-orin-devkit-industrial.conf configuration file.
  3. Try flashing the module again using the same command, but with the --no-flash option to see if the issue persists.
  4. If the issue persists, try flashing the module using a different configuration file or a different flashing method.

In summary, the issue appears to be specific to the Jetson AGX Orin module being flashed, and further troubleshooting is required to determine the root cause of the problem.

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

5

Don’t know what happened. Do you have other host PC to try?

6

I can’t burn it with other computers either. I have successfully burned several other Orin modules with this computer, but this one is stuck in the front few lines and doesn’t work. I suspect there may be some problem with the modules

7

what is the log from sdkmanager if you try to use sdkmanager to flash instead of flash.sh?