Do i have a dead nano

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hello All i hope all is well…

I recieved this log trying to to put nano a02 into recovery mode from minicom… can someone tell how if the nano is dead or is there a alternate solution any help would be great

[0000.163] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.168] Processing in cold boot mode Bootloader 2
[0000.173] A02 Bootrom Patch rev = 1023
[0000.177] Power-up reason: pmc por
[0000.180] No Battery Present
[0000.182] pmic max77620 reset reason
[0000.186] pmic max77620 NVERC : 0x40
[0000.189] RamCode = 0
[0000.191] Platform has DDR4 type RAM
[0000.195] max77620 disabling SD1 Remote Sense
[0000.199] Setting DDR voltage to 1125mv
[0000.203] Serial Number of Pmic Max77663: 0x507cb
[0000.210] Entering ramdump check
[0000.213] Get RamDumpCarveOut = 0x0
[0000.217] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.222] Last reboot was clean, booting normally!
[0000.226] Sdram initialization is successful
[0000.231] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.237] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.242] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.248] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.254] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.260] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.266] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.272] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.288] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.294] Platform-DebugCarveout: 0
[0000.297] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.303] Non secure mode, and RB not enabled.
[0000.307] BoardID = 3448, SKU = 0x0
[0000.311] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.314] Nano-SD: checking PT table on QSPI …
[0000.319] Read PT from (2:0)
[0000.334] Using BFS PT to query partitions
[0000.338] PT: Partition TBC NOT found !
[0000.342] Warning: Find Partition via PT Failed
[0000.346] BoardID = 3448, SKU = 0x0
[0000.349] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.353] Nano-SD: checking PT table on QSPI …
[0000.358] PT: Partition TBC NOT found !
[0000.361] Warning: Find Partition via PT Failed
[0000.366] Error is 1

2

Hi,

The only problem here is you think you put the module into recovery mode. But actually it didn’t.
This is just another boot log.

3

Incidentally, recovery mode itself does not change a Nano in any permanent way. All it does is turn it into a custom USB device (understood by the driver package, which is downloaded by and part of the flash software). It isn’t until you run the flash software from an Ubuntu 18.04 host PC (I picked that release due to what is compatible with a Nano) that the Nano is modified. If a partition cannot be found, then likely you need to flash.

To get recovery mode the recovery pin must be grounded (there is a ground pin right next to the recovery pin) while power is either cycled or turned on (it is like a shift key on a keyboard…there is no need to hold power or recovery buttons down for any particular time; one merely taps on the power button or power reset button while the recovery button is held down). I sometimes refer to individual pins as buttons, but the button just shorts power or reset pins to ground; applying power by plug-in can be considered equivalent to tapping the “power on” button.

Note that on Nano dev kits the QSPI memory is on the Nano itself. Boot content goes there. The SD card is only for the rootfs. Although you can create an SD card separately, the boot content can only be added via the flash software while in recovery mode. You can find documentation and software here (L4T is what gets flashed, whereas JetPack/SDK Manager is the flashing software; each has its version tied to the other):

4

thank you so much for your time and info…i’ll get to it

5

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