Issues with flashing jetson orin nx 16GB #1304
Answered
by
fabiocabaceira
SirMomster
asked this question in
Q&A
-
|
Hey, We are currently testing the demo project on a Jetson Orin NX. However, once we start the flashing process. It fails at step 3, and gets stuck on flashpkg. We assume this is because the Jetson doesn't get into the USB device mode, and in result, doesn't show up as a storage device. We could confirm this as no storage device shows up anywhere. Here is the command we run and the output, as you can see, it stays stuck on "Waiting for USB storage device flashpkg from f12c0204." Even after longer periods of time than this snippet shows. > sudo ./initrd-flash
Starting at 2023-07-28T15:45:09+02:00
Machine: p3509-a02-p3767-0000
Rootfs device: nvme0n1p1
Found Jetson device in recovery mode at USB 5-2
== Step 1: Signing binaries at 2023-07-28T15:45:09+02:00 ==
== Step 2: Boot Jetson via RCM at 2023-07-28T15:45:20+02:00 ==
Found Jetson device in recovery mode at USB 5-2
== Step 3: Sending flash sequence commands at 2023-07-28T15:45:22+02:00 ==
Waiting for USB storage device flashpkg from f12c0204.......We have been following the guide here: https://github.com/OE4T/meta-tegra/wiki/initrd-flashing-support If additional information is required, I would be glad to provide it. Kind regards |
Beta Was this translation helpful? Give feedback.
Answered by
fabiocabaceira
Aug 7, 2023
Replies: 5 comments 23 replies
-
|
Sounds like Linux is failing to boot. What carrier is your Orin NX modules installed into? Is it a Xavier NX development kit (that's the p3509), an Orin Nano development kit, or something else? Can you hook up a serial cable and capture the console output? |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Hey @madisongh, Thanks for the swift reply it's much appreciated, we use a JNX42 carrier board from Auvidea (https://auvidea.eu/product/70784/), we flash using p3509 when we use the NVIDIA SDK Manager, which works fine. We use the following command when we flash with the SDK manager: 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 p3509-a02+p3767-0000 internalThis board doesn't really have an accessible way to reach the console output during boot (there is a level switcher that we require), which is something we are looking into with the manufacturer (as it's currently on backorder). Kind regards |
Beta Was this translation helpful? Give feedback.
-
|
Hey @madisongh, Any idea what could be the cause of the difference between the NVIDIA SDK Manager and the sudo ./initrd-flash from meta-tegra? Thanks for your time, |
Beta Was this translation helpful? Give feedback.
-
|
There are differences - the scripts are different and NVIDIA uses all pre-built binary files for booting/kernel/etc. that its scripts select at flash time vs. Yocto builds being a mix of build-time and runtime configuration choices. Which of those differences might be significant in this case, I don't know off-hand. Can you post the detailed logs from the successful SDK Manager flashing run and the failed one from the Yocto build for comparison? And serial console output would be helpful, too, but if that's not possible, at least the host-side logs would be a start. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @madisongh, I attached the logs from the NVIDIA SDK Manager and those of the Yocto flashing: Do you know if the We hope to provide you with more information asap regarding the serial logs. But this might take some time. Thanks in advance, Kind regards |
Beta Was this translation helpful? Give feedback.
-
|
Hey @madisongh , When attempting to use /initrd-flash, I also encounter a problem where the process gets stuck at "Waiting for USB storage device flashpkg from 8a60000a......." However, when using NVIDIA SDK Manager, I can flash the JetPack OS and the ports start working again. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Which machine configuration(s) did you try? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your help @madisongh , I was able to solve my problem. Initially, in the So, I built a demo image with the Thank you again. |
Beta Was this translation helpful? Give feedback.
Answer selected by
madisongh
-
|
Hi @madisongh, Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Looking at their wiki page for flashing JetPack/L4T when using that carrier, it looks like the |
Beta Was this translation helpful? Give feedback.
-
|
Hello @madisongh . Old issue, but I've been facing a similar problem for a custom machine configuration (slighty modified meta-tegra). I was able to flash like 2 hours ago, now, when trying to reflash, I'm having this issue. dmesg output Any idea? Can I possibly enable logging for the script? |
Beta Was this translation helpful? Give feedback.
13 replies
-
|
Orin NX 8GB After:
I'm able to flash my custom image using Is this a known issue? |
Beta Was this translation helpful? Give feedback.
-
|
Are you enabling UEFI secure boot ? |
Beta Was this translation helpful? Give feedback.
-
|
Could you please share the logs for the serial uart ? |
Beta Was this translation helpful? Give feedback.
-
After this, it shutdowns I think? |
Beta Was this translation helpful? Give feedback.
-
|
That looks like a boot after flashing with the NVIDIA SDK Manager, rather than a Yocto build. The system should be waiting for you to complete the setup via GUI or through one of the USB-gadget serial terminals. |
Beta Was this translation helpful? Give feedback.
-
|
To add my two cents here: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
FYI So, it seems that selecting the correct machine is quite important. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I'm using Orin NX 8GB Module mounted on Hadron board from CTI. I face the same issue here exactly. Stuck on waiting for flashpkg. But it works on Jetpack 5(Kirkstone branch), but after switching to scarthgap I couldn't anymore. In order to resolve that issue can anyone tell me how to read all machine configs from jetpack as I've made my custom machine and modified it as Jetpüack but I want to double check every flashvar to make sure that I've using the same dts/dtsi for the every flashvar. The vendor also sent a patch for a quasi similar problem and stated that "Patch for fixing NVMe flash issues when external usb CC is involved" The problem that vendor patches function set_up_usb_device_mode() in nv_enable_remote.sh in L4T, but I don't know what is the opposite for that function in initrd-flash. I want to make sure that I emulate everything done in L4T from custom carrier vendor. you can also see the logs from machine side to point out if there an issue I've overseen. |
Beta Was this translation helpful? Give feedback.
-
|
What did they patch in that function? It probably maps to something in the |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for your help @madisongh , I was able to solve my problem.
Initially, in the
machine.conffile, I usedjetson-orin-nano-devkit-nvme. However, upon examining the successful JetPack flashing process, I found the dtb:tegra234-p3767-0000-p3509-a02.dtb.So, I built a demo image with the
machine.conffile set top3509-a02-p3767-0000. Although the progress got stuck on step 5 when runningsudo /initrd-flash, the USB ports were still functional, indicating that there was progress. After a few retries, I was able to successfully flash the image usinginitrd-flash.sh.Thank you again.