I’m trying to flash a Jetson TX2 NX module (P3636) mounted on a Xavier NX devkit (P3518). When using the sdkmanager, or the flash.sh script from the Linux_for_Tegra archive, the result is the same: the flashing hangs at the following step:
16:20:06 INFO: Flash Jetson TX2 NX - flash: [ 11.4429 ] tegrarcm_v2 --boot recovery
16:20:06 INFO: Flash Jetson TX2 NX - flash: [ 11.4461 ] Applet version 01.00.0000
16:20:08 INFO: Flash Jetson TX2 NX - flash: [ 12.4690 ] tegrarcm_v2 --isapplet
16:20:08 INFO: Flash Jetson TX2 NX - flash: [ 13.4311 ] tegradevflash_v2 --iscpubl
I am otherwise able to flash the Xavier NX module P3668 without any issue.
Any idea what’s going wrong?
may I know what’s your flash commands to flash a Jetson TX2 NX.
$ sudo ./flash.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1
Yes I’m precisely using this command:
sudo ./flash.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1
may I know which JetPack release version you’re working on?
could you please try again with the latest JetPack release version.
I’m using with the Jetpack 4.5.1 (L4T 32.5.1) which is the latest revision.
Could you try remove WiFi module and flash by manually?
I removed the WiFi module and flashed again. It still hangs at the same exact step. Here is the UART log if it can help:
[0082.173] I> Welcome to MB2(TBoot-BPMP) Recovery(version: 01.00.160913-t186-M-00.00-mobile-2814ffb8)
[0082.183] I> Boot-device: eMMC
[0082.263] I> sdmmc DDR50 mode
[0082.268] I> sdmmc bdev is already initialized
[0082.272] I> pmic: reset reason (nverc) : 0x50
[0082.277] W> Cannot find any partition table for 00000003
[0082.283] W> Cannot find any partition table for 00010003
[0082.292] I> Binary(16) of size 534416 is loaded @ 0xd7800000
[0082.299] I> Binary(17) of size 113296 is loaded @ 0xd79e4560
[0082.327] I> Copy BTCM section
[0082.331] I> Binary(13) of size 221376 is loaded @ 0x96000000
[0082.338] I> Binary(20) of size 191456 is loaded @ 0x85214400
[0082.346] I> Binary(14) of size 394672 is loaded @ 0x85314600
[0082.353] I> TOS boot-params @ 0x85000000
[0082.357] I> TOS params prepared
[0082.360] I> Loading EKS ...
[0082.364] I> Binary(15) of size 1040 is loaded @ 0x85914800
[0082.369] I> EKB detected (length: 0x400) @ 0x85914800
[0082.374] I> Copied encrypted keys
[0082.378] I> boot profiler @ 0x175844000
[0082.382] I> boot profiler for TOS @ 0x175844000
[0082.387] I> Unhalting SCE
[0082.389] I> Primary Memory Start:80000000 Size:70000000
[0082.394] I> Extended Memory Start:f0110000 Size:856f0000
[0084.038] I> MB2(TBoot-BPMP) Recovery done
Please make sure you are using TX2 NX module (P3636) + Xavier-NX devkit (P3509).
We tried flash TX2 NX, it can flash JP-4.5.1 (r32.5.1) success.
My TX2 NX is a P3636 module mounted on a P3518 devkit. Note that flashing a P3668 on the same P3518 devkit works fine.
- TX2 NX module (P3636) + Xavier-NX devkit (P3509) = jetson-xavier-nx-devkit-tx2-nx.conf
- Xavier-NX module (P3668) + Xavier-NX devkit (P3509) = jetson-xavier-nx-devkit.conf or jetson-xavier-nx-devkit-emmc.conf
If you’re using P3636 on P3518 devkit and flash fail, please remove original folder and download image to try again.
Yes that’s my understanding: jetson-xavier-nx-devkit works, jetson-xavier-nx-devkit-emmc.conf works but jetson-xavier-nx-devkit-tx2-nx.conf hangs as described above. Is there a way to debug such a hang, could my P3636 module be dysfunctional?
are you using the native JetPack release?
did you update the
bl31.bin, (i.e. the arm trusted firmware), or
lk.bin, (i.e. Trusty image) for flashing the board?
please have a try to assign board information to the flash command-line and try again?
$ sudo BOARDID=3636 BOARDSKU=0010 FAB=000 ./flash.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1
I am using the native JetPack release without any edition. I did not update the
bl31.bin or the
lk.bin firmware. The board has never been flashed.
I tried the command you provided, the problem remains. Please find the complete flash log attached.
flash.log (23.1 KB)
The flash log is going well up to the point of hang. I am curious, when the flash hangs, does the Jetson show up with “
lsusb -d 0955:”? I left it open to show all NVIDIA devices, so others might also show up (I did so because I think you have an NX dev kit but we are in the TX2 forum). Regardless of whether the Jetson shows up then with
lsusb, will it continue if you briefly disconnect and reconnect the micro-B USB cable?
When the flashing hangs,
lsusb -d 0955: shows:
Bus 003 Device 008: ID 0955:7c18 NVIDIA Corp. APX which is identical to with what is shown before flashing.
Briefly disconnecting/reconnecting the micro USB cable when the flashing hangs doesn’t help, the flashing process is still stuck at
Here’s the dmesg log during the flashing process:
[771669.154928] usb 3-5: new high-speed USB device number 7 using xhci_hcd
[771669.371934] usb 3-5: New USB device found, idVendor=0955, idProduct=7c18, bcdDevice= 0.00
[771669.371938] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[771669.371939] usb 3-5: Product: APX
[771669.371939] usb 3-5: Manufacturer: NVIDIA Corp.
[771676.345115] loop0: detected capacity change from 0 to 29360128
[771676.777542] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[771715.383478] usb 3-5: USB disconnect, device number 7
[771715.758426] usb 3-5: new high-speed USB device number 8 using xhci_hcd
[771715.975835] usb 3-5: New USB device found, idVendor=0955, idProduct=7c18, bcdDevice= 0.00
[771715.975841] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[771715.975842] usb 3-5: Product: APX
[771715.975843] usb 3-5: Manufacturer: NVIDIA Corp.
[771715.975844] usb 3-5: SerialNumber: 00000
Is the host PC a VM? This too could cause a failure, but the
lsusb is correct, so I doubt this would even matter, but need to ask. Can you say more about the host PC itself, including if there is a USB HUB, and if the HUB has other devices on it?
No I’m using a native Linux install (Guix System) and the Xavier devkit is connected directly to my PC using an USB-C to micro USB cable. I’m able to flash other Jetson boards such as the Nano, Nano EMMC and Xavier NX which makes me think that the problem is directly related to the TX2 NX module itself.
it does look like hardware issue here,
do you have another TX2 NX module (P3636) or Xavier-NX devkit (P3509) for cross validation?
if you’d confirm your Jetson product is defective,
please contact the NVIDIA Customer Care team for the RMA process.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.