When i use doflash.sh script to flash jeston orin nano 8GB devkit failed

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

the follow is error info:

image
image1039×727 110 KB

What could possibly cause this problem？？？how can i fix it???

2

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

Based on the provided context, it appears that you are experiencing an issue with your Jetson Orin Nano device, and you’ve shared an error message with an image (1039727, 110 KB). Unfortunately, I couldn’t view the image, but I’ll provide a general troubleshooting guide to help you identify and potentially fix the problem.

Common Issues on Jetson Orin Nano:

  1. Boot and Shutdown Issues: Some users have reported problems with the device not shutting down properly or experiencing automatic restarts. (e.g., “My jetson orin nx 16g won’t shut down properly” and “Orinnx poweroff and power on，it not work。”)
  2. Flashing and Installation Issues: There have been reports of flashing failures, especially when using custom boards or specific JetPack versions. (e.g., “Flashing JetPack 6.0 to custom Jetson Orin Nano 4GB board fails after initial boot”)
  3. Container and Docker Issues: Some users have encountered problems with container runtime, Docker integration, or specific container installations. (e.g., “Error with “Nvidia Container Runtime with Docker Integration” on AGX Orin with JP6.2” and “Install Jenkin on NVIDIA Jetson Orin Nano”)

Troubleshooting Steps:

  1. Check the Boot Process: Ensure that the device is booting correctly, and the boot process is not interrupted. You can try booting the device in recovery mode or using a serial console to diagnose the issue.
  2. Verify the Flashing Process: If you’re experiencing flashing issues, try re-flashing the device using the correct JetPack version and following the official flashing instructions.
  3. Inspect the Container Runtime: If you’re encountering container-related issues, check the container runtime logs, and ensure that the Docker integration is correctly configured.
  4. Review the System Logs: Check the system logs (e.g., dmesg, syslog, or journalctl) for any error messages that might indicate the cause of the problem.
  5. Seek Community Help: If none of the above steps resolve the issue, share the error message and details about your setup on the NVIDIA Jetson forums or other relevant communities to get help from experts and other users who may have experienced similar problems.

Specific to Your Error Message:

Without the actual error message or image, it’s challenging to provide a precise solution. However, I recommend checking the system logs and container runtime logs for any error messages related to the image (1039727, 110 KB). You can also try searching for similar error messages on the NVIDIA Jetson forums or other online resources.

If you’re still unable to resolve the issue, please provide more details about the error message, your setup, and any relevant configuration files, and I’ll do my best to assist you further.

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

8

Hi,

How do you flash your device using script?

  • Please provide the commands for us to review.

Is your host a native ubuntu or a virtual machine?

Do you follow the quick start guide to flash your device?

Thanks

9

my script as follow:

#!/bin/bash

image=$1
machine=$2

scriptdir=“$( cd “$( dirname “${BASH_SOURCE[0]}” )” >/dev/null && pwd )”
deployfile=${image}-${machine}.tegraflash.tar.gz
tmpdir=mktemp

rm -rf $tmpdir
mkdir -p $tmpdir
echo “Using temp directory $tmpdir”
pushd $tmpdir
cp $scriptdir/build/tmp/deploy/images/${machine}/$deployfile .
tar -xvf $deployfile
set -e
sudo /home/tvt/yocto-tegra/build/tmp/work/jetson_orin_nano_devkit_nvme-poky-linux/core-image-sato-dev/1.0-r0/tegraflash/doflash.sh
popd
echo “Removing temp directory $tmpdir”
rm -rf $tmpdir

and i excute the command: sudo ./deploy.sh core-image-sato-dev jetson-orin-nano-devkit-nvme

10

Hi,

We notice that you could not read EEPROM board information.

Do you put the device in recovery mode?

Please try to use lsusb to check your status.

Thanks

11

@DavidDDD

the follow is lsusb result:

tvt@tvt-virtual-machine:~/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_NANO_8GB/Linux_for_Tegra/source$ lsusb
Bus 002 Device 011: ID 0955:7020 NVIDIA Corp. L4T (Linux for Tegra) running on Tegra
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

12

Hi,

Please refer to the official doc to check whether in recovery mode.

Thanks

13

it is in recovery mode,because I shorted pins 9 and 10 on the J14 header of the development board

14

Hi,

Could you take a picture for us to review?

Thanks

15

@DavidDDD

What kind of pictures would you like to see? Are you referring to photos of the development board?

devkit
devkit522×658 332 KB

16

Hi,

Please try to use other jumper to short the REC and GND pins.

If you could access the system, you could run sudo reboot --force forced-recovery.

Thanks