Started with jp6 dp and continues with jp5.1.2

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

I had been trying to install jp6 dp on top of l4t 35.4.1 using sdkmanager. When flashing got to about 50% only then would it pop up the (from agx orin devkit getting started guide)
(5. On the flashing prompt;
Select “Manual Setup - Jetson AGX Orin” for 1. )
So jetpack 6.0dp never installed and the Orin would not boot.

Next installed jp5.4.1 on the nvme. Everything in sdk installed normally and I once again had fully operational agx orin devkit.

Then I tried installing jp6 again via sdk. I again did not get the popup (5. On the flashing prompt; Select “Manual Setup - Jetson AGX Orin” for 1. )

Then cancelled the sdk install. then installed jp6 via nvautoflash.sh and it reported no error but did not reboot. When I forced reboot via removing/reapplying power the Orin once again would not boot.

Then installed jp5.4.1 again with
./flash.sh jetson-agx-orin-devkit nvme0n1 and i’ve attached the terminal output with errors also mentioned in a couple of other posts herein but I don’t see a resolution for whatever my problem is.

The second to last line in the attached flash.log says
" The target t186ref has been flashed successfully. "
but obviously flash.sh should have and probably did install t234.

So thank you for any assistance you can provide.
flash.log (94.2 KB)

3

Your whole topic is messy and hard to understand.
Can you please summarize what you wanted to do?
It’s 35.4.1 or 36.2?

4

My issue is twofold.

(1). jp6dp SDK will not launch the popup that lets you pick what drive to flash.

(2). Once jp6dp fails, then when I run sdk 5.1.2, flash.sh, or nvautoflash.sh, they report success (“The target t186ref has been flashed successfully.” ) when in fact they’ve not changed the filesystem on nvme.

Look at first line in attached log to see i told flash.sh to do t234 not t186. And the second to last line therein what states “success”.

link to identical errors that are in my attached log file.

5

t186ref is just a code name that we don’t change with new chips like T194 and T234.
It does not matter and is not something users should care.
The real issue is that your command for flashing NVMe is wrong.

With 35.4.1, you need:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-agx-orin-devkit internal

With 36.2, you need:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-agx-orin-devkit internal
6

Thank you. I’ll try it tomorrow. I’m not currently where the agx orin is.

7

36.2
Waiting for target to boot-up…
Unknown device “/sys/class/net/usb0”: No such device
Unknown device “/sys/class/net/usb0”: No such device
Waiting for target to boot-up…
Waiting for device to expose ssh …RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh …Run command: flash on fc00:1:1:0::2
SSH ready
mount.nfs: Connection timed out
Flash failure
Cleaning up…
l4t_initrd_flash.log (270.9 KB)
usbNVIDIa.log (612 Bytes)

8

35.4.1 successfully installed with your provided command.

9

Usually it’s some Internet connection issue:

10

Thank you for your assistance. I think I should close this thread as at this late date I’ve discovered that my hp workstation no longer has /dev/ttyUSB0 and I tried the following that also failed and failed to write a log. So I will attempt this on my old hp workstation but may wait until jp6 is released.

./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --showlogs
–network eth0:192.168.1.79/24:192.168.1.175:192.168.1.1
jetson-agx-orin-devkit internal

1 Like
11

Thank you for your help. I moved to my ubuntu 20.04 workstation that has python2.7. Installed yaml, and sdk jp6. Ran the following and quickly installed R36. 2

./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–showlogs --network eth0:192.168.1.79/24:192.168.1.179:192.168.1.1
jetson-agx-orin-devkit internal

13

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