I am attempting to flash brand new Jetson TX2NX modules and having failures. I have a system image and device tree that are both known to work, and my flashing setup has successfully flashed 1000s of TX2NXs.
In the latest shipment I received of TX2NX modules, 90% of them are failing to flash. For each one that fails, the flash procedure hangs at the following step:
*** Checking CPU bootloader
tegradevflash_v2 --instance 1-10.1 --iscpubl
No matter how long I let the flash process sit, it never advances.
I am running the flash procedure the same way on all the devices, not in a VM, and with a known working image and device tree. My question is: are all these TX2NX modules likely defective or has something changed with recent batches and I need to update the flashing utilities? Please advise, thank you!
We use our custom carrier board to flash. We have used this carrier board design to flash 1000s of Jetsons over the last few years, and we have attempted to use multiple different boards for flashing. 10% of the Jetsons are working when flashed through our carrier.
What is your JP version?
Could you use our dev kit to cross check whether the issue exist?
Also please attach a full flash log and the serial console log.
We are using Jetpack 4.6 I believe. I see that in JetPack 4.6.6, the release notes reference a new DRAM chip. It seems that the TX2NX modules failing have a different product code on their DRAM than the ones passing.
Is the DRAM likely the culprit? And will we need to update to 4.6.6?
Ok, the TX2 modules seem like they are able to be flashed using JetPack 4.6.6. That’s a good start.
Now the question is whether I can reuse my device tree with new JetPack flashing tools.
Is it expected to work if I drop the dtb into the correct locations inside of the new JetPack folder? Or do I need to rebuild my device tree based off of JetPack 4.6.6 for things to work on the new TX2 modules with these new RAM chips?
Also, I can’t seem to get the nvmassflashgen.shscript to generate a working mass-flash directory. The command succeeds and it outputs a tbz2 file but whenever I try to flash one of these new modules using the generated mass flash directory, it fails with the output below.
Please advise, thank you.
BR_CID: 0x81801001640e27071400000017ff84c0
RCM version 0X180001
Boot Rom communication completed
*** Boot Rom communication succeeded.
*** Checking applet
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --isapplet
Applet version 01.00.0000
*** Checking applet succeeded.
*** Sending BCTs
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
Applet version 01.00.0000
Sending bct_bootrom
[................................................] 100%
Sending bct_mb1
[................................................] 100%
*** Sending BCTs succeeded.
*** Sending bootloader and pre-requisite binaries
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --download blob blob.bin
Applet version 01.00.0000
Sending blob
[................................................] 100%
*** Sending bootloader and pre-requisite binaries succeeded.
*** Booting Recovery
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --boot recovery
Applet version 01.00.0000
*** Booting Recovery succeeded.
*** Checking applet
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --isapplet
*** Checking CPU bootloader
/opt/hwui/massflash_tx2nx/tegradevflash_v2 --instance 5-1 --iscpubl
Bootloader version 01.00.0000
Bootloader version 01.00.0000
*** Checking CPU bootloader succeeded.
*** Flashing the device
/opt/hwui/massflash_tx2nx/tegradevflash_v2 --instance 5-1 --pt flash.xml.bin --create
Bootloader version 01.00.0000
Erasing sdmmc_boot: 3 ......... [Done]
Writing partition secondary_gpt with gpt_secondary_0_3.bin
[................................................] 100%
Erasing sdmmc_user: 3 ......... [Done]
Writing partition master_boot_record with mbr_1_3.bin
[................................................] 100%
Writing partition primary_gpt with gpt_primary_1_3.bin
[................................................] 100%
000000000d0d0001:
*** Error: Flashing the device failed.
Ok, I’ll start a new issue about the mass flashing.
It has been a long time since we’ve rebuilt the device tree for our carrier board, so we’re a bit lost. Could you please describe in detail the exact steps required to produce the necessary files? If there is simple documentation for exactly how to do this, please direct me to that.
For our custom carrier board we only need to customize one or two GPIOs. The customization is fairly straightforward, and I believe have the old .dts files. From memory, I believe we generated them starting from the Jetson TX2 NX Series Pinmux Table downloadable from here. This spreadsheet no longer seems to work, when I try to edit it and generate the .dtsifiles I receive Visual Basic Macro errors. If there is a better or alternative way, please let me know.