Failed to flash jetson nano 2GB devkit with Jetpack4.6.4

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

I am trying to flash the Jetson Nano 2GB Devkit using sdkmanager, with Jetpack 4.6.4. Everything seems fine, but when the progress reaches 99%, it gets stuck for a long time and does not proceed further.

sudo ./flash.sh jetson-nano-2gb-devkit mmcblk0p1

Then I attempted to use flash.sh for flashing, encountering the same problem, where it hangs at the following stage.

[ 166.2114 ] [................................................] 100%
[ 166.2853 ] Writing partition VER_b with qspi_bootblob_ver.txt
[ 174.1285 ] [................................................] 100%
[ 174.1681 ] Writing partition VER with qspi_bootblob_ver.txt
[ 174.4510 ] [................................................] 100%
[ 174.4929 ] Writing partition APP with system.img
[ 174.7759 ] [................................................] 100%
3

Hi,

What do you get from serial console log?

Does swapping for a different SD card help?

4

@DaveYYY
Thanks for your quick reply. Here is the log:

[0086.253] [L4T TegraBoot] (version ԧ
[0086.258] Processing in recovery mode
[0086.262] A02 Bootrom Patch rev = 1023
[0086.265] Power-up reason: pmc por
[0086.269] Established communication link with host
[0087.392] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0087.400] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0087.409] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0002.258] Enabled early print
[0002.261] [L4T TegraBoot] (version ԧ
[0002.266] Processing in recovery mode
[0002.270] A02 Bootrom Patch rev = 1023
[0002.273] Power-up reason: software reset
[0002.277] Established communication link with host
[0003.408] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0003.416] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0003.424] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0003.250] Enabled early print
[0003.253] [L4T TegraBoot] (version ԧ
[0003.258] Processing in recovery mode
[0003.262] A02 Bootrom Patch rev = 1023
[0003.265] Power-up reason: software reset
[0003.269] Established communication link with host
[0004.510] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0004.518] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0004.526] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0265.376] Enabled early print
[0265.379] [L4T TegraBoot] (version ԧ
[0265.384] Processing in recovery mode
[0265.387] A02 Bootrom Patch rev = 1023
[0265.391] Power-up reason: software reset
[0265.394] Established communication link with host
[0266.662] Odmdata from BCT: 0x000a4000
[0266.666] DebugPort= 0x3
[0266.668] SkipQspiOnly= 0x0
[0266.721] BoardId read from EEPROM/NCT: 3448
[0266.725] BoardID = 3448, SKU = 0x3
[0266.752] NvTbootInit_Porg: Setting GPIO_A6 for HDMI ...
[0266.757] max77620 setting MBLPD bit
[0266.761] No Battery Present
[0266.763] RamCode = 1
[0266.766] Platform has DDR4 type RAM
[0266.769] max77620 disabling SD1 Remote Sense
[0266.773] Setting DDR voltage to 1125mv
[0266.777] Serial Number of Pmic Max77663: 0x323d1
[0266.785] Entering ramdump check
[0266.788] Get RamDumpCarveOut = 0x0
[0266.791] RamDumpCarveOut=0x0,  RamDumperFlag=0xe59ff3f8
[0266.796] Last reboot was clean, booting normally!
[0266.801] Sdram initialization is successful 
[0266.805] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0266.811] Lp0 Carveout Base=0x00000000ff800000 Size=0x00000000
[0266.817] BpmpFw Carveout Base=0x00000000ff800000 Size=0x00000000
[0266.823] GSC1 Carveout Base=0x00000000ff800000 Size=0x00000000
[0266.829] Resize the SecureOs Carveout to 0x00100000
[0266.834] GSC2 Carveout Base=0x00000000ff900000 Size=0x00100000
[0266.839] GSC4 Carveout Base=0x00000000ff800000 Size=0x00000000
[0266.845] GSC5 Carveout Base=0x00000000ff800000 Size=0x00000000
[0266.851] GSC3 Carveout Base=0x00000000bf800000 Size=0x00200000
[0266.857] RamDump Carveout Base=0x0000000000000000 Size=0x00000000
[0266.863] Platform-DebugCarveout: 0
[0266.866] Downloaded BCT successfully
[0267.601] Downloaded Bootloader successfully
[0267.714] Downloaded rp1 successfully
[0267.909] MAX77620_GPIO5 configured
[0267.913] CPU power rail is up
[0267.915] CPU clock enabled
[0267.919] Performing RAM repair
[0267.922] Updating A64 Warmreset Address to 0x92c002e9
[0267.929] Enable APE clock/reset
[0267.932] Error in NvTbootGetTOSBinaryLength: 0x11 !
[0267.936] Loading Secure OS image failed. 
[0267.940] Set NvDecSticky Bits
[0267.944] GSC2 address ff93fffc value c0edbbcc
[0267.950] GSC MC Settings done
[0267.954] Next binary entry address: 0x92c00258 
[0267.959] BoardId: 3448
[0267.961] Overriding pmu board id with proc board id
[0267.966] Display board id is not available 
[0267.970] Starting CPU & Halting co-processor 

[0274.412] 
[0274.413] Debug Init done
[0274.417] Marked DTB cacheable
[0274.420] Bootloader DTB loaded at 0x83000400
[0274.424] DeviceTree Init done
[0274.439] Pinmux applied successfully
[0274.444] gicd_base: 0x50041000
[0274.447] gicc_base: 0x50042000
[0274.450] Interrupts Init done
[0274.455] Using base:0x60005090 & irq:208 for tick-timer
[0274.460] Using base:0x60005098 for delay-timer
[0274.464] platform_init_timer: DONE
[0274.468] Timer(tick) Init done
[0274.472] osc freq = 38400 khz
[0274.476] 
[0274.477] Welcome to L4T Cboot
[0274.480] 
[0274.481] Cboot Version: 00.00.2018.01-t210-acb23272
[0274.486] calling constructors
[0274.489] initializing heap
[0274.492] initializing threads
[0274.495] initializing timers
[0274.498] creating bootstrap completion thread
[0274.502] top of bootstrap2()
[0274.505] CPU: ARM Cortex A57
[0274.508] CPU: MIDR: 0x411FD071, MPIDR: 0x80000000
[0274.512] initializing platform
[0274.521] Manufacturer: MF = 0xc2, ID MSB = 0x25
[0274.526] ID LSB = 0x36, ID-CFI len = 194 bytes
[0274.530] Macronix QSPI chip present
[0274.534] SPI device register
[0274.536] init boot device
[0274.539] allocating memory for boot device(SPI)
[0274.544] registering boot device
[0274.553] sdmmc node status = okay
[0274.556] sdcard instance = 0
[0274.559] sdmmc cd-inverted
[0274.562] sdcard gpio handle 0x5a
[0274.565] sdcard gpio pin 0xc9
[0274.568] sdcard gpio flags 0x0
[0274.571] vmmc-supply 0x9a
[0274.574] Instance: 0
[0274.576] Allocating memory for context
[0274.580] enabling clock
[0274.582] sd card init
[0274.584] Check card present and stable
[0274.588] Send command 0
[0274.661] Send command 3
[0274.665] Set RCA for the card
[0274.668] Query card specific data by command 9
[0274.675] Parse CSD data
[0274.677] Send command 7
[0274.687] Calling sd device register
[0274.691] Init sdcard
[0274.693] Allocating memory for boot device
[0274.697] Registering user device
[0274.710] of_register: registering tegra_udc to of_hal
[0274.715] of_register: registering inv20628-driver to of_hal
[0274.721] of_register: registering ads1015-driver to of_hal
[0274.727] of_register: registering lp8557-bl-driver to of_hal
[0274.732] of_register: registering bq2419x_charger to of_hal
[0274.738] of_register: registering bq27441_fuel_gauge to of_hal
[0274.751] gpio framework initialized
[0274.754] of_register: registering tca9539_gpio to of_hal
[0274.760] of_register: registering tca9539_gpio to of_hal
[0274.765] of_register: registering i2c_bus_driver to of_hal
[0274.771] of_register: registering i2c_bus_driver to of_hal
[0274.776] of_register: registering i2c_bus_driver to of_hal
[0274.782] pmic framework initialized
[0274.785] of_register: registering max77620_pmic to of_hal
[0274.791] regulator framework initialized
[0274.795] of_register: registering tps65132_bl_driver to of_hal
[0274.801] initializing target
[0274.807] gpio_driver_register: register 'tegra_gpio_driver' driver
[0274.816] board ID = D78, board SKU = 3
[0274.820] Skipping Z3!
[0274.825] fixed regulator driver initialized
[0274.848] initializing OF layer
[0274.852] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0274.871] I2C Bus Init done
[0274.873] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0274.884] I2C Bus Init done
[0274.887] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0274.898] I2C Bus Init done
[0274.901] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0274.912] I2C Bus Init done
[0274.915] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0274.926] I2C Bus Init done
[0274.929] of_children_init: Ops found for compatible string maxim,max77620
[0274.940] max77620_init using irq 118
[0274.945] register 'maxim,max77620' pmic
[0274.949] gpio_driver_register: register 'max77620-gpio' driver
[0274.955] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0274.967] I2C Bus Init done
[0274.970] Applying platform configs
[0274.978] platform-init is not present. Skipping
[0274.982] calling apps_init()
[0275.010] Found 14 GPT partitions in "sd0"
[0275.014] Proceeding to flashing Server
[0275.018] usbdcd_reinit Initialize driver to use already enumerated device
[0275.025] nv3p_priv_usbf_open USB configuration success
[0275.466] Writing GPT partition
[0275.489] Erasing Boot device
[0275.492] device_write_gpt: Erasing boot device spiflash0
[0293.973] Erasing Storage Device
[0293.976] Writing protective mbr
[0293.988] Writing primary GPT
[0294.008] Writing secondary GPT
[0294.048] Found 1 GPT partitions in "sd0"
[0294.080] Writing PT partition
[0298.012] partition PT write successful.
[0298.048] Writing NVC partition
[0308.102] partition NVC write successful.
[0308.142] Writing NVC_R partition
[0318.210] partition NVC_R write successful.
[0318.248] Writing TBC partition
[0323.176] partition TBC write successful.
[0323.209] Writing RP1 partition
[0337.186] partition RP1 write successful.
[0337.220] Writing EBT partition
[0366.349] partition EBT write successful.
[0366.383] Writing WB0 partition
[0366.670] partition WB0 write successful.
[0366.706] Writing BPF partition
[0366.992] partition BPF write successful.
[0367.024] Writing TOS partition
[0370.487] partition TOS write successful.
[0370.520] Writing DTB partition
[0384.498] partition DTB write successful.
[0384.532] Writing LNX partition
[0424.419] partition LNX write successful.
[0424.453] Writing EKS partition
[0424.740] partition EKS write successful.
[0424.776] Writing BMP partition
[0433.905] partition BMP write successful.
[0433.941] Writing RP4 partition
[0441.844] partition RP4 write successful.
[0441.882] Writing VER_b partition
[0442.170] partition VER_b write successful.
[0442.205] Writing VER partition
[0442.491] partition VER write successful.
[0442.525] Writing APP partition
[0770.544] Error in command_complete 18001 int_status
[0770.551] Error in command_complete 18001 int_status
[0770.558] Error in command_complete 18001 int_status
[0770.563] sending the command failed 0xffffffec in sdmmc_send_command at 109
[0770.570] setting block length failed 0xffffffec in sdmmc_block_io at 945
[0770.577] block I/O failed 0xffffffec in sdmmc_io at 1215
[0770.582] block write failed 0xffffffec in sdmmc_bdev_write_block at 178
[0770.589] Failure in device_write_sparse_image_recovery at 511
[0770.595] bytes_written is :[-20]
[0770.598] bytes_to_decode is :[1047528]
[1109.267] failed APP partition write !
[1109.270] Number of bytes written -20
[1109.274] panic (caller 0x92c0293c): Written less bytes than expectedHALT: spinning forever...

I see that some errors have occurred. Does this mean that my TF card has suffered irreparable damage?

5

Sounds like the case.
If it fails in the same place every time, then maybe like some bad blocks in your SD card.

6

@DaveYYY I used a tool to check the TF card and did not find any error blocks. Moreover, I replaced the TF card with another one, but the same problem persists.

7

Do you have other modules for testing?
Maybe the module itself was broken.

8

You are correct.
I downloaded the standard JP4.6.1 image from the download center, flashed it, and found that the system wouldn’t boot, and there was no serial output.
However, this is really strange because this Jetson Nano was working fine before. I tried flashing a new system with the SDK Manager and didn’t perform any risky operations.

10

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