I have DevKit Module that was working fine, but then suddenly stopped working. I’m thinking it’s possible that it was ESD’d while moving it for a demo. At least that’s what the SW developer thinks happened so he’s busy buying enclosures for all our Nano DevKits.
I tried using the console output, but it wasn’t working. It worked fine for other Devkits so I moved the Module over to another DevKit to get the Console output to work.
Here is the console output:
[0000.126] [TegraBoot] (version 00.00.2018.01-l4t-33e7fa82)
[0000.131] Processing in cold boot mode Bootloader 2
[0000.136] A02 Bootrom Patch rev = 1023
[0000.139] Power-up reason: pmc por
[0000.142] No Battery Present
[0000.145] pmic max77620 reset reason
[0000.148] pmic max77620 NVERC : 0x40
[0000.152] RamCode = 0
[0000.154] Platform has DDR4 type RAM
[0000.157] max77620 disabling SD1 Remote Sense
[0000.161] Setting DDR voltage to 1125mv
[0000.165] Serial Number of Pmic Max77663: 0x150ce4
[0000.173] Entering ramdump check
[0000.176] Get RamDumpCarveOut = 0x0
[0000.179] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.184] Last reboot was clean, booting normally!
[0000.189] Sdram initialization is successful
[0000.193] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.199] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.205] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.211] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.217] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.223] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.228] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.234] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.250] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.257] Platform-DebugCarveout: 0
[0000.260] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.266] Non secure mode, and RB not enabled.
[0000.272] Invalid GPT Partition
[0000.287] Using BFS PT to query partitions
[0000.291] failed to load NvTbootTbootCpu from (2:0)
[0000.296] re-load NvTbootTbootCpu from (4:0)
[0000.469] Csd NumOfBlocks=124735488
[0000.484] Using GPT Primary to query partitions
[0000.492] Loading Tboot-CPU binary
[0000.869] Verifying TBC in OdmNonSecureSBK mode
[0000.879] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.886] Bootloader downloaded successfully.
[0000.890] Downloaded Tboot-CPU binary to 0xa0000258
[0000.895] MAX77620_GPIO5 configured
[0000.898] CPU power rail is up
[0000.901] CPU clock enabled
[0000.905] Performing RAM repair
[0000.908] Updating A64 Warmreset Address to 0xa00002e9
[0000.913] Loading NvTbootBootloaderDTB
[0002.222] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0002.287] Bootloader DTB Load Address: 0x83000000
[0002.292] Loading NvTbootKernelDTB
[0003.600] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0003.665] Kernel DTB Load Address: 0x83100000
[0003.673] Loading cboot binary
[0005.354] Verifying EBT in OdmNonSecureSBK mode
[0005.396] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0005.403] Bootloader downloaded successfully.
[0005.595] Using BFS PT to query partitions
I tried multiple times with the same results, and it didn’t matter how I powered it. It always halted there.
I just got different results when I tried it again.
I should note that this MicroSD card works fine in a different Jetson Nano Devkit.
[0000.126] [TegraBoot] (version 00.00.2018.01-l4t-33e7fa82)
[0000.131] Processing in cold boot mode Bootloader 2
[0000.135] A02 Bootrom Patch rev = 1023
[0000.139] Power-up reason: pmc por
[0000.142] No Battery Present
[0000.145] pmic max77620 reset reason
[0000.148] pmic max77620 NVERC : 0xee
[0000.152] RamCode = 0
[0000.154] Platform has DDR4 type RAM
[0000.157] max77620 disabling SD1 Remote Sense
[0000.161] Setting DDR voltage to 1125mv
[0000.165] Serial Number of Pmic Max77663: 0x150ce4
[0000.173] Entering ramdump check
[0000.176] Get RamDumpCarveOut = 0x0
[0000.179] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.184] Last reboot was clean, booting normally!
[0000.189] Sdram initialization is successful
[0000.193] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.199] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.205] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.211] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.217] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.223] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.228] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.234] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.250] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.256] Platform-DebugCarveout: 0
[0000.260] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.266] Non secure mode, and RB not enabled.
[0000.272] Invalid GPT Partition
[0000.287] Using BFS PT to query partitions
[0000.291] failed to load NvTbootTbootCpu from (2:0)
[0000.296] re-load NvTbootTbootCpu from (4:0)
[0000.468] Csd NumOfBlocks=124735488
[0000.482] Using GPT Primary to query partitions
[0000.490] Loading Tboot-CPU binary
[0000.867] Verifying TBC in OdmNonSecureSBK mode
[0000.877] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.884] Bootloader downloaded successfully.
[0000.888] Downloaded Tboot-CPU binary to 0xa0000258
[0000.893] MAX77620_GPIO5 configured
[0000.897] CPU power rail is up
[0000.899] CPU clock enabled
[0000.903] Performing RAM repair
[0000.906] Updating A64 Warmreset Address to 0xa00002e9
[0000.911] Loading NvTbootBootloaderDTB
[0002.220] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0002.285] Bootloader DTB Load Address: 0x83000000
[0002.290] Loading NvTbootKernelDTB
[0003.598] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0003.663] Kernel DTB Load Address: 0x83100000
[0003.671] Loading cboot binary
[0005.352] Verifying EBT in OdmNonSecureSBK mode
[0005.395] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0005.402] Bootloader downloaded successfully.
[0005.594] Using BFS PT to query partitions
[0036.139] Sw timeout in read happened
[0036.143] Query status failed with error 0x5 status 3
[0036.147] Device not in idle state with error 0x10 in NvTbootSdmmcIoSector func at 369 line
[0036.156] Sector IO failed with 0x10 error
[0036.159] Sector IO failed with error 0x10 in NvTbootSdmmcIo func at 417 line
[0036.166] Sdmmc IO failed with 0x10 error
[0036.170] Next binary entry address: 0x92c00258
[0036.175] BoardId: 3448
[0036.179] Overriding pmu board id with proc board id
[0036.184] Display board id is not available
[0036.189] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0036.199] Command complete wait failed with error 0x3 Interrupt 0x18001
[0036.205] Number of retries left 4
[0036.209] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0036.219] Command complete wait failed with error 0x3 Interrupt 0x18001
[0036.225] Number of retries left 3
[0036.228] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0036.239] Command complete wait failed with error 0x3 Interrupt 0x18000
[0036.245] Number of retries left 2
[0036.248] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0036.258] Command complete wait failed with error 0x3 Interrupt 0x18000
[0036.265] Number of retries left 1
[0036.268] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0036.278] Command complete wait failed with error 0x3 Interrupt 0x18001
[0036.285] Number of retries left 0
[0036.288] Send command failed with 0x3
[0036.292] Setting block length failed with error 0x3 in NvTbootSdmmcIoSector func at 292 line
[0036.300] Sector IO failed with 0x3 error
[0036.304] Sector IO failed with error 0x3 in NvTbootSdmmcIo func at 417 line
[0036.311] Sdmmc IO failed with 0x3 error
[0036.314] Failed to load Bpmp Firmware!
[0036.318] Error is 3
hello S4WRXTTCS,
may I know which JetPack release you’re working with?
assume you had two Jetson-Nano devkit, one is workable and the other isn’t.
could you please share the revision of each of them.
also, may I know what’s the commands you’re used to flash these Nano platforms?
thanks
I’m using the latest Jetpack
That’s correct in that we have multiple Jetson-Nano Devkits. On the Devkit that’s bad the Console port wasn’t working so I moved the SOM to a working baseboard so I could get the console output. The SD card that’s in it was the known good SD card from the working SOM. The SD card was created using the Jetpack SDK manager with the good DevKit (SOM+BaseBoarD).
My understanding is that an Imaged SD card can freely be moved from one Devkit to another.
For the Revision where should I be looking?
Info on the one that stopped working:
Jetson Nano
NVidia CORP Model: P3448
Santa Clara 180-13448-DAAA-A02
R-R-NVA-P3448
On the SD Connector there is stamp of 90125EC
Above the SD connector there is a silkscreen of 1419 27-02
BarCode: 0421519015186
Info on the one the good one:
Jetson Nano
NVidia CORP Model: P3448
Santa Clara 180-13448-DAAA-A02
R-R-NVA-P3448
On the SD Connector there is stamp of 90311EC
Above the SD connector there is a silkscreen of 1819 02-01
BarCode: 1421919083548
Note: I’m not sure if the Barcode was interpreted correctly. It appeared to be in the DataMatrix format so I put it through one of the free online barcode readers as that.
hello S4WRXTTCS,
below message shows some partition reading failure.
may I know did those non-working Jetson-Nano flashed before?
[0000.272] Invalid GPT Partition
[0000.287] Using BFS PT to query partitions
you could found JetPack SDK manager install the image locally,
for example,
~/nvidia/nvidia_sdk/JetPack_4.2.1/...
please have another try to run the below commands manually to flash those non-working Jetson-Nano devices.
thanks
$ sudo ./flash.sh -r jetson-nano-qspi-sd mmcblk0p1
Sticking a new SD card into the non-working Jetson Nano, and then using the flash command did resolve the issue. At least on a known good carrier board.
That confuses me a bit as I though the only thing getting imaged was the SD card, and I was previously using a known good SD card that was imaged on a working Jetson.
So I’m confused about what the flash command did that brought it back to life.
My understanding is that an SD card image can freely be moved from one Jetson Devkit to another. Or is there something that locks them down on the first boot?
hello S4WRXTTCS,
you should flash the board for the 1st boot.
also, flashing commands also update several partition for SPI devices, you may also refer to below xml files for details.
thanks
$OUT/Linux_for_Tegra/bootloader/t210ref/cfg/flash_l4t_t210_spi_sd_p3448.xml