Issue with Jetson nano 2G boot up for the first time

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hi , I’m trying to bootup my Jestson nano 2G unit for the first time. I see nvidia logo and the screen is stuck there. Attaching the boot log for more details. I’m booting via SD card and downloaded the 2G version of the image from

I’ve unzipped the file contents and copied them using BalenaEtcher onto a UHS-1 64gb sandisk microsd card. Pls let me know what am I missing here. Thanks.

Serial port Boot log:
Welcome to minicom 2.7.1

OPTIONS: I18n
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyUSB0, 19:28:18

Press CTRL-A Z for help on special keys

�[0000.125] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.130] Processing in cold boot mode Bootloader 2
[0000.135] A02 Bootrom Patch rev = 1023
[0000.138] Power-up reason: pmc por
[0000.141] No Battery Present
[0000.144] pmic max77620 reset reason
[0000.147] pmic max77620 NVERC : 0x40
[0000.151] RamCode = 3
[0000.153] Platform has DDR4 type RAM
[0000.156] max77620 disabling SD1 Remote Sense
[0000.161] Setting DDR voltage to 1125mv
[0000.165] Serial Number of Pmic Max77663: 0x2a1c66
[0000.172] Entering ramdump check
[0000.175] Get RamDumpCarveOut = 0x0
[0000.179] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.184] Last reboot was clean, booting normally!
[0000.188] Sdram initialization is successful
[0000.192] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.199] Lp0 Carveout Base=0x00000000ff800000 Size=0x00000000
[0000.204] BpmpFw Carveout Base=0x00000000ff800000 Size=0x00000000
[0000.210] GSC1 Carveout Base=0x00000000ff800000 Size=0x00000000
[0000.216] Resize the SecureOs Carveout to 0x00100000
[0000.221] GSC2 Carveout Base=0x00000000ff900000 Size=0x00100000
[0000.227] GSC4 Carveout Base=0x00000000ff800000 Size=0x00000000
[0000.232] GSC5 Carveout Base=0x00000000ff800000 Size=0x00000000
[0000.238] GSC3 Carveout Base=0x000000017f800000 Size=0x00100000
[0000.244] RamDump Carveout Base=0x0000000000000000 Size=0x00000000
[0000.250] Platform-DebugCarveout: 0
[0000.253] Nck Carveout Base=0x00000000ff800000 Size=0x00000000
[0000.259] Non secure mode, and RB not enabled.
[0000.263] BoardID = 3448, SKU = 0x3
[0000.266] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.270] Nano-SD: checking PT table on QSPI …
[0000.274] Read PT from (2:0)
[0000.290] Using BFS PT to query partitions
[0000.296] Loading Tboot-CPU binary
[0000.324] Verifying TBC in OdmNonSecureSBK mode
[0000.334] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.341] Bootloader downloaded successfully.
[0000.345] Downloaded Tboot-CPU binary to 0xa0000258
[0000.350] MAX77620_GPIO5 configured
[0000.353] CPU power rail is up
[0000.356] CPU clock enabled
[0000.360] Performing RAM repair
[0000.363] Updating A64 Warmreset Address to 0xa00002e9
[0000.368] BoardID = 3448, SKU = 0x3
[0000.371] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.375] Nano-SD: checking PT table on QSPI …
[0000.379] Loading NvTbootBootloaderDTB
[0000.446] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.526] Bootloader DTB Load Address: 0x83000000
[0000.530] BoardID = 3448, SKU = 0x3
[0000.534] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.537] Nano-SD: checking PT table on QSPI …
[0000.542] Loading NvTbootKernelDTB
[0000.608] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.687] Kernel DTB Load Address: 0x83100000
[0000.692] BoardID = 3448, SKU = 0x3
[0000.695] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.699] Nano-SD: checking PT table on QSPI …
[0000.705] Loading cboot binary
[0000.821] Verifying EBT in OdmNonSecureSBK mode
[0000.862] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0000.869] Bootloader downloaded successfully.
[0000.874] BoardID = 3448, SKU = 0x3
[0000.877] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.881] Nano-SD: checking PT table on QSPI …
[0000.885] PT: Partition NCT NOT found !
[0000.889] Warning: Find Partition via PT Failed
[0000.893] Next binary entry address: 0x92c00258
[0000.898] BoardId: 3448
[0000.902] Overriding pmu board id with proc board id
[0000.907] Display board id is not available
[0000.911] No Bpmp FW loaded
[0000.914] Not loading WB0 as no bpmp/sc7entry fw
[0000.918] Set NvDecSticky Bits
[0000.922] GSC2 address ff93fffc value c0edbbcc
[0000.928] GSC MC Settings done
[0000.931] BoardID = 3448, SKU = 0x3
[0000.934] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.938] Nano-SD: checking PT table on QSPI …
[0000.943] TOS Image length 53680
[0000.947] Monitor size 53680
[0000.949] OS size 0
[0000.965] Secure Os AES-CMAC Verification Success!
[0000.969] TOS image cipher info: plaintext
[0000.973] Loading and Validation of Secure OS Successful
[0000.989] NvTbootPackSdramParams: start.
[0000.994] NvTbootPackSdramParams: done.
[0000.998] Tegraboot started after 51829 us
[0001.002] Basic modules init took 922845 us
[0001.006] Sec Bootdevice Read Time = 12 ms, Read Size = 61 KB
[0001.011] Sec Bootdevice Write Time = 0 ms, Write Size = 0 KB
[0001.017] Next stage binary read took 11286 us
[0001.021] Carveout took -63807 us
[0001.024] CPU initialization took 99966 us
[0001.028] Total time taken by TegraBoot 970290 us

[0001.033] Starting CPU & Halting co-processor

64NOTICE: BL31: v1.3(release):5b49e7f80
NOTICE: BL31: Built : 11:38:25, Jan 25 2021
ERROR: Error initializing runtime service trusty_fast
[0001.155] RamCode = 3
[0001.157] get_emc_table_offset: Can’t find emc-table node
[0001.162] LPDDR4 Training: Can’t find emc-table node
[0001.198]
[0001.199] Debug Init done
[0001.202] Marked DTB cacheable
[0001.205] Bootloader DTB loaded at 0x83000000
[0001.210] Marked DTB cacheable
[0001.212] Kernel DTB loaded at 0x83100000
[0001.216] DeviceTree Init done
[0001.229] Pinmux applied successfully
[0001.234] gicd_base: 0x50041000
[0001.237] gicc_base: 0x50042000
[0001.240] Interrupts Init done
[0001.244] Using base:0x60005090 & irq:208 for tick-timer
[0001.250] Using base:0x60005098 for delay-timer
[0001.254] platform_init_timer: DONE
[0001.257] Timer(tick) Init done
[0001.261] osc freq = 38400 khz
[0001.265]
[0001.266] Welcome to L4T Cboot
[0001.269]
[0001.270] Cboot Version: 00.00.2018.01-t210-39562017
[0001.275] calling constructors
[0001.278] initializing heap
[0001.281] initializing threads
[0001.284] initializing timers
[0001.287] creating bootstrap completion thread
[0001.291] top of bootstrap2()
[0001.294] CPU: ARM Cortex A57
[0001.297] CPU: MIDR: 0x411FD071, MPIDR: 0x80000000
[0001.302] initializing platform
[0001.309] Manufacturer: MF = 0xc2, ID MSB = 0x25
[0001.314] ID LSB = 0x36, ID-CFI len = 194 bytes
[0001.318] Macronix QSPI chip present
[0001.322] SPI device register
[0001.324] init boot device
[0001.327] allocating memory for boot device(SPI)
[0001.332] registering boot device
[0001.340] QSPI bdev is already initialized
[0001.344] Enable APE clock
[0001.347] Un-powergate APE partition
[0001.350] of_register: registering tegra_udc to of_hal
[0001.355] of_register: registering inv20628-driver to of_hal
[0001.361] of_register: registering ads1015-driver to of_hal
[0001.366] of_register: registering lp8557-bl-driver to of_hal
[0001.372] of_register: registering bq2419x_charger to of_hal
[0001.378] of_register: registering bq27441_fuel_gauge to of_hal
[0001.389] gpio framework initialized
[0001.393] of_register: registering tca9539_gpio to of_hal
[0001.398] of_register: registering tca9539_gpio to of_hal
[0001.404] of_register: registering i2c_bus_driver to of_hal
[0001.409] of_register: registering i2c_bus_driver to of_hal
[0001.415] of_register: registering i2c_bus_driver to of_hal
[0001.420] pmic framework initialized
[0001.424] of_register: registering max77620_pmic to of_hal
[0001.429] regulator framework initialized
[0001.433] of_register: registering tps65132_bl_driver to of_hal
[0001.439] initializing target
[0001.445] gpio_driver_register: register ‘tegra_gpio_driver’ driver
[0001.453] board ID = D78, board SKU = 3
[0001.457] Skipping Z3!
[0001.461] fixed regulator driver initialized
[0001.480] initializing OF layer
[0001.483] NCK carveout not present
[0001.487] Skipping dts_overrides
[0001.491] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.508] I2C Bus Init done
[0001.511] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.521] I2C Bus Init done
[0001.524] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.534] I2C Bus Init done
[0001.537] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.547] I2C Bus Init done
[0001.550] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.560] I2C Bus Init done
[0001.563] of_children_init: Ops found for compatible string maxim,max77620
[0001.573] max77620_init using irq 118
[0001.578] register ‘maxim,max77620’ pmic
[0001.582] gpio_driver_register: register ‘max77620-gpio’ driver
[0001.588] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0001.599] I2C Bus Init done
[0001.603] NCK carveout not present
[0001.612] Find /i2c@7000c000’s alias i2c0
[0001.616] get eeprom at 1-a0, size 256, type 0
[0001.625] Find /i2c@7000c500’s alias i2c2
[0001.629] get eeprom at 3-a0, size 256, type 0
[0001.633] get eeprom at 3-ae, size 256, type 0
[0001.638] pm_ids_update: Updating 1,a0, size 256, type 0
[0001.643] I2C slave not started
[0001.646] I2C write failed
[0001.649] Writing offset failed
[0001.652] eeprom_init: EEPROM read failed
[0001.656] pm_ids_update: eeprom init failed
[0001.660] pm_ids_update: Updating 3,a0, size 256, type 0
[0001.690] pm_ids_update: The pm board id is 3448-0003-412
[0001.697] Adding plugin-manager/ids/3448-0003-412=/i2c@7000c500:module@0x50
[0001.706] pm_ids_update: pm id update successful
[0001.710] pm_ids_update: Updating 3,ae, size 256, type 0
[0001.740] pm_ids_update: The pm board id is 3542-0000-201
[0001.746] Adding plugin-manager/ids/3542-0000-201=/i2c@7000c500:module@0x57
[0001.754] pm_ids_update: pm id update successful
[0001.785] eeprom_get_mac: EEPROM invalid MAC address (all 0xff)
[0001.791] shim_eeprom_update_mac:267: Failed to update 0 MAC address in DTB
[0001.799] eeprom_get_mac: EEPROM invalid MAC address (all 0xff)
[0001.804] shim_eeprom_update_mac:267: Failed to update 1 MAC address in DTB
[0001.813] updating /chosen/nvidia,ethernet-mac node 48:b0:2d:3c:10:3c
[0001.819] Plugin Manager: Parse ODM data 0x000a4000
[0001.832] shim_cmdline_install: /chosen/bootargs: earlycon=uart8250,mmio32,0x7
[0001.847] Find /i2c@7000c000’s alias i2c0
[0001.851] get eeprom at 1-a0, size 256, type 0
[0001.860] Find /i2c@7000c500’s alias i2c2
[0001.864] get eeprom at 3-a0, size 256, type 0
[0001.868] get eeprom at 3-ae, size 256, type 0
[0001.873] pm_ids_update: Updating 1,a0, size 256, type 0
[0001.878] I2C slave not started
[0001.881] I2C write failed
[0001.883] Writing offset failed
[0001.887] eeprom_init: EEPROM read failed
[0001.890] pm_ids_update: eeprom init failed
[0001.895] pm_ids_update: Updating 3,a0, size 256, type 0
[0001.925] pm_ids_update: The pm board id is 3448-0003-412
[0001.931] Adding plugin-manager/ids/3448-0003-412=/i2c@7000c500:module@0x50
[0001.938] pm_ids_update: pm id update successful
[0001.942] pm_ids_update: Updating 3,ae, size 256, type 0
[0001.973] pm_ids_update: The pm board id is 3542-0000-201
[0001.979] Adding plugin-manager/ids/3542-0000-201=/i2c@7000c500:module@0x57
[0001.986] pm_ids_update: pm id update successful
[0002.016] Add serial number:1420622028580 as DT property
[0002.024] Applying platform configs
[0002.031] platform-init is not present. Skipping
[0002.035] calling apps_init()
[0002.041] Couldn’t find GPT header
[0002.046] Proceeding to Cold Boot
[0002.049] starting app android_boot_app
[0002.053] Device state: unlocked
[0002.056] display console init
[0002.064] could not find regulator
[0002.067] hdmi cable connected
[0002.083] edid read success
[0002.100] DT entry for leds-pwm not found
[0002.104] edid read success
[0002.107] width = 640, height = 480, frequency = 25174825
[0002.112] width = 1920, height = 1080, frequency = 148500000
[0002.118] width = 1280, height = 720, frequency = 74250000
[0002.123] width = 1920, height = 1080, frequency = 148351648
[0002.129] width = 1280, height = 720, frequency = 74175824
[0002.134] width = 1920, height = 1080, frequency = 148351648
[0002.140] width = 1280, height = 720, frequency = 74175824
[0002.145] width = 720, height = 480, frequency = 26973026
[0002.151] width = 720, height = 576, frequency = 26973026
[0002.156] Best mode Width = 1920, Height = 1080, freq = 148351648
[0002.164] tmds-config node not found
[0002.168] pmc_set_io_pad_voltage: Error -2 retrieving platform-io-pad-voltageps
[0002.183] setting ‘vdd-1v8’ regulator to 1800000 micro volts
[0002.190] could not find regulator
[0002.194] could not find regulator
[0002.197] could not find regulator
[0002.225] using default cmu settings
[0002.229] dc_hdmi_enable, starting HDMI initialisation
[0002.235] dc_hdmi_enable, HDMI initialisation complete
[0002.240] list and configure display window
[0002.249] display console init completed
[0002.260] subnode volume_up is not found !
[0002.264] subnode back is not found !
[0002.268] subnode volume_down is not found !
[0002.272] subnode menu is not found !
[0002.275] Gpio keyboard init success
[0002.356] found decompressor handler: lz4-legacy
[0002.370] decompressing blob (type 1)…
[0002.441] load_bmp_blob: panelresolution=1080 type=3
[0002.515] decompressor handler not found
[0002.519] load_firmware_blob: Firmware blob loaded, entries=2
[0002.525] XUSB blob version 0 size 124416 @ 0x934ae28c
[0002.531] -------> se_aes_verify_sbk_clear: 747
[0002.535] se_aes_verify_sbk_clear: Error
[0002.539] SE operation failed
[0002.542] bl_battery_charging: connected to external power supply
[0002.554] device_query_partition_size: failed to open partition spiflash0:MSC !
[0002.561] MSC Partition not found
[0002.568] device_query_partition_size: failed to open partition spiflash0:USP !
[0002.575] USP partition read failed!
[0002.579] blob_init: blob-partition USP header read failed
[0002.584] android_boot Unable to update recovery partition
[0002.589] kfs_getpartname: name = LNX
[0002.593] Loading kernel from LNX
[0002.602] Found 19 BFS partitions in “spiflash0”
[0002.920] load kernel from storage
[0002.925] decompressor handler not found
[0003.188] Successfully loaded kernel and ramdisk images
[0003.194] board ID = D78, board SKU = 3
[0003.198] sdmmc node status = okay
[0003.201] sdcard instance = 0
[0003.204] sdcard gpio handle 0x5a
[0003.208] sdcard gpio pin 0xc9
[0003.211] sdcard gpio flags 0x0
[0003.214] vmmc-supply 0x9d
[0003.216] cd_gpio_pin = 201
[0003.219] pin_state = 0
[0003.221] Found sdcard
[0003.223] SD-card IS present …
[0003.227] load_and_boot_kernel: SD card detected OK
[0003.232] load_bmp_blob: panelresolution=1080 type=3
[0003.728] display bmp image done
[0003.731] NCK carveout not present
[0003.734] Skipping dts_overrides
[0003.737] NCK carveout not present
[0003.747] Find /i2c@7000c000’s alias i2c0
[0003.751] get eeprom at 1-a0, size 256, type 0
[0003.760] Find /i2c@7000c500’s alias i2c2
[0003.764] get eeprom at 3-a0, size 256, type 0
[0003.768] get eeprom at 3-ae, size 256, type 0
[0003.773] pm_ids_update: Updating 1,a0, size 256, type 0
[0003.778] I2C slave not started
[0003.781] I2C write failed
[0003.784] Writing offset failed
[0003.787] eeprom_init: EEPROM read failed
[0003.791] pm_ids_update: eeprom init failed
[0003.795] pm_ids_update: Updating 3,a0, size 256, type 0
[0003.825] pm_ids_update: The pm board id is 3448-0003-412
[0003.832] Adding plugin-manager/ids/3448-0003-412=/i2c@7000c500:module@0x50
[0003.840] pm_ids_update: pm id update successful
[0003.845] pm_ids_update: Updating 3,ae, size 256, type 0
[0003.875] pm_ids_update: The pm board id is 3542-0000-201
[0003.881] Adding plugin-manager/ids/3542-0000-201=/i2c@7000c500:module@0x57
[0003.889] pm_ids_update: pm id update successful
[0003.920] eeprom_get_mac: EEPROM invalid MAC address (all 0xff)
[0003.926] shim_eeprom_update_mac:267: Failed to update 0 MAC address in DTB
[0003.933] eeprom_get_mac: EEPROM invalid MAC address (all 0xff)
[0003.939] shim_eeprom_update_mac:267: Failed to update 1 MAC address in DTB
[0003.948] updating /chosen/nvidia,ethernet-mac node 48:b0:2d:3c:10:3c
[0003.954] Plugin Manager: Parse ODM data 0x000a4000
[0003.967] shim_cmdline_install: /chosen/bootargs: earlycon=uart8250,mmio32,0x7
[0003.976] Add serial number:1420622028580 as DT property
[0003.984] Updated bpmp info to DTB
[0003.988] Updated initrd info to DTB
[0003.992] “proc-board” doesn’t exist, creating
[0003.998] Updated board info to DTB
[0004.001] “pmu-board” doesn’t exist, creating
[0004.008] Updated board info to DTB
[0004.011] “display-board” doesn’t exist, creating
[0004.017] Updated board info to DTB
[0004.020] “reset” doesn’t exist, creating
[0004.025] Updated reset info to DTB
[0004.028] Cmdline: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype
[0004.065] DTB cmdline: earlycon=uart8250,mmio32,0x70006000
[0004.071] boot image cmdline: root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4
[0004.084] Updated bootarg info to DTB
[0004.088] Adding uuid 000000016431b6c90800000012fe8100 to DT
[0004.094] Adding eks info 0 to DT
[0004.099] WARNING: Failed to pass NS DRAM ranges to TOS, err: -7
[0004.105] Updated memory info to DTB
[0004.113] set vdd_core voltage to 1075 mv
[0004.117] setting ‘vdd-core’ regulator to 1075000 micro volts
[0004.123] Found secure-pmc; disable BPMP

U-Boot 2020.04-g6b630d64fd (Jan 25 2021 - 11:38:16 -0800)

SoC: tegra210
Model: NVIDIA Jetson Nano 2GB Developer Kit
Board: NVIDIA P3541-0000
DRAM: 4 GiB
“Synchronous Abort” handler, esr 0x96000046
elr: 00000000800e8eac lr : 00000000800978fc (reloc)
elr: 00000000fff97eac lr : 00000000fff468fc
x0 : 00000000fda2d000 x1 : 0000000000000000
x2 : 0000000002502000 x3 : 00000000fff2f000
x4 : 00000000ff800008 x5 : 0000000000000000
x6 : 00000000004a0400 x7 : 00000000fff2f008
x8 : 00000000ffff0000 x9 : 0000000000000008
x10: 000000000a200023 x11: 0000000000000002
x12: 0000000000000002 x13: 000000008019a410
x14: 000000017fa00000 x15: 00000000fff30b3c
x16: 0000000100000000 x17: 00000000001fffff
x18: 00000000fd7ffdc0 x19: 00000000fffb7940
x20: 00000000fffb7000 x21: 000000007feaf000
x22: 0000000084100000 x23: 00000000000a07d8
x24: 0000000080080000 x25: 0000000000000800
x26: 0000000000000800 x27: 0000000000000000
x28: 0000000000000800 x29: 00000000fd7fa330

Code: 17fffff1 52800123 92401c26 17fffff3 (f81f8085)
Resetting CPU …

resetting …

2

The SD card models of Jetsons have QSPI memory containing boot content. That has to be a release version compatible with the SD card release. Most likely you will need to flash the module itself with an Ubuntu 18.04 host PC and JetPack/SDK Mananger. See:
https://developer.nvidia.com/embedded/jetpack-archive

3

Hi linuxdev, thanks for responding. I’m new to this platform. I’ve installed the SDK Manager on ubuntu machine. When I connect my Jetson nano via microusb and run thru the steps as listed in the SDK manager still doesn’t detect the device. Can you pls share how to flash the sd card modules? Also, is there a way to identify if jetson nano went into recovery mode?
I’ve checked dmesg and also lsusb for any NVIDIA devices, but did not find any.

IMG-0086
IMG-00861920×1908 429 KB

4

If the correct USB cable is connected (it uses a micro-B USB cable on the micro-OTG USB port), and if the Jetson is in recovery mode, then SDKM should detect the Jetson. Recovery mode occurs if the recovery pin is shorted to ground during the moment power is applied, or if the pin is shorted to ground when the power is reset. There is no need to hold the recovery pin shorted to ground after power up or power cycle. If lsusb still fails, then something has gone wrong (perhaps it is the wrong cable, or perhaps it isn’t really in recovery mode).

One thing to test is that if you think the Jetson really is in recovery mode, then monitor “dmesg --follow” on the host PC and either plug in or replug the cable and see what new log messages come up. Post what you get.

Note that you can still flash SD cards separately so long as it is from a release version compatible with what was flashed to the module’s QSPI memory.

Note: VMs typically fail like this due to improper setup of USB passthrough.

5

I’m using a standalone Ubuntu 18.04 machine. I tried swapping multiple USB cables. I don’t observe any new messages on dmesg when putting the device in recovery mode or in general plugging/re-plugging the micro USB cable to jetson nano. Any idea which version of sd card image is compatible with the modules on my qspi? Does the serial log attached above give any cues as to what’s going wrong?

6

I have no way of knowing which release your QSPI is currently at.

The lack of any message with plug/unplug tends to indicate a hardware error if the Jetson was put into recovery mode. If you are using a “charger” cable rather than one provided, then this could be the problem, but since you tried multiple cables (and I assume watched logs from dmesg for each) and this did not show anything at all, then I am thinking it is hardware failure.

Someone from NVIDIA may be able to spot something in the log, but I can’t see any “simple” cause. The same advice would probably be repeated though, to try to flash. If flash is not possible it may require RMA.

7

  1. For any jetson nano issue, if you see it got stuck in bootloader, stop trying sdcard image. Just try to flash with sdkmanager.

  2. To flash with sdkmanager, you need to put the board into recovery mode.

  3. In this page, please set “Pre-config” and manual config.
    image

8

Hi WayneWWW, I’m trying to put the board in recovery mode by connecting Pin 9 FC REC and Pin 10 GND, booting up, and removing it after a few seconds. But the board is not going into recovery mode. Checked dmesg and lsub to detect any NVIDIA USB port messages, but I see none. The image I shared above is what exactly I’m using with the configs you mentioned. I think the core issue here is I’m not able to put my unit into recovery mode. I need assistance with it. Also, can u take a look at the serial log I pasted above and let me know if there are any cues on what is going wrong? Is there a different way to put the board in recovery mode?

9

Hi,

  1. Remove the power cable from your jetson.

  2. Plug the FC REC +GND jumper. Do not remove it. Plug the power cable back.

  3. Check the lsusb on your host. (also with micro usb cable connected to jetson).

10

Still see nothing. No new Device ID pop up

11

How many jetson do you have on your side? And how many of them cannot enter recovery mode?

12

I only have one board with me.

13

Is your host machine a VM? Does you micro usb cable have data line but not only power line?

14

I’ve a stand-alone Ubuntu. Looks like my usb cable has a faulty data line, have re-soldered it. Able to put the unit in recovery mode 😀 Will continue flashing using the sdkmanager. Thanks for the inputs WayneWWW.

1 Like
15

Good evening,
I am having the same type of issue with a Jetson Nano 2GB.
I have tried booting via the SD card with the 461 image and the screen got stuck at the nVidia logo.
Then I switched to using SDKmanager. I am running Ubuntu 18.04 on a host PC. I have put the board in Forced Recovery mode. The flashing process started and it works for a while but then it fails. I have tried numerous times, same result.
I have saved the log, I will attach it here.
SDKM_logs_JetPack_4.6.2_Linux_for_Jetson_Nano_modules_2022-07-14_21-53-38.zip (107.7 KB)

16

Hi,

Please try multiple times and see if it always got stuck. If so, please

  1. Make sure your sdcard size is large enough. I would suggest at least 32GB.

  2. Dump the serial log as Jetson Nano Style - Serial Console - JetsonHacks when the flash starts.

Also, make sure the usb is not disconnected during flash and host is not VM.

17

Hi Wayne,
I confirm that:
1)I have tried multiple times with the same result.
2) The sd card size is 64GB.
3) The host is NOT a VM.
4) The USB is NOT disconnected during flash.

I will work on the serial log and post it as soon as I have results.

Thank you for helping us.

18

Hi Wayne,
On my side, the issue has been resolved. I have tried flashing again, this time with a different micro-USB cable and the flashing process was completed.
Thanks again.

1 Like
19

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