flashing jetson nano stucks on 99.9%

Hello,

I’m using “jetson nano module (P3488)” and tried to flashing with SDK Manager 0.9.14.4964 & JetPack 4.2.3

(we are not using devkit but designed with our own carrier board)

Anyway, it stucks on 99.9% on “Flash Jetson OS” and I can’t do anything …

Can anybody give me some hints ?

https://ibb.co/6rrtvKN

https://ibb.co/LRsDppF

Thanks

To debug such issue, please try to dump serial console log during flash process.

https://www.jetsonhacks.com/2019/04/19/jetson-nano-serial-console/

Also, under such case, you cannot rely on sdkmanager but should directly use the flash script under Linux_for_Tegra. If you don’t know what it is, please refer to L4T document or quick start guide from our download center.

I got console message as belows

what’s wrong with me ?

[0007.734] Enabled early print
[0007.737] [TegraBoot] (version 00.00.2018.01-l4t-e5cfc6a7)
[0007.742] Processing in recovery mode
[0007.745] A02 Bootrom Patch rev = 1023
[0007.749] Power-up reason: pmc por
[0007.752] Established communication link with host
[0008.762] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0008.770] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0008.779] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0223.708] Odmdata from BCT: 0x00094000
[0223.711] DebugPort= 0x3
[0223.721] BoardId read from EEPROM/NCT: 3448
[0223.725] BoardID = 3448, SKU = 0x2
[0223.752] NvTbootInit_Porg: Setting GPIO_A6 for HDMI …
[0223.757] No Battery Present
[0223.760] RamCode = 0
[0223.762] Platform has DDR4 type RAM
[0223.765] max77620 disabling SD1 Remote Sense
[0223.770] Setting DDR voltage to 1125mv
[0223.774] Serial Number of Pmic Max77663: 0x140df1
[0223.781] Entering ramdump check
[0223.784] Get RamDumpCarveOut = 0x0
[0223.788] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0223.793] Last reboot was clean, booting normally!
[0223.797] Sdram initialization is successful
[0223.802] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0223.808] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0223.814] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0223.820] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0223.825] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0223.831] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0223.837] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0223.843] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0223.859] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0223.865] Platform-DebugCarveout: 0
[0223.869] Downloaded BCT successfully
[0224.192] Downloaded Bootloader successfully
[0224.261] Downloaded rp1 successfully
[0224.317] MAX77620_GPIO5 configured
[0224.320] CPU power rail is up
[0224.323] CPU clock enabled
[0224.327] Performing RAM repair
[0224.330] Updating A64 Warmreset Address to 0x92c002e9
[0224.336] Enable APE clock/reset
[0224.339] Error in NvTbootGetTOSBinaryLength: 0x11 !
[0224.344] Loading Secure OS image failed.
[0224.348] Set NvDecSticky Bits
[0224.351] GSC2 address ff53fffc value c0edbbcc
[0224.358] GSC MC Settings done
[0224.362] Next binary entry address: 0x92c00258
[0224.366] BoardId: 3448
[0224.369] Overriding pmu board id with proc board id
[0224.373] Display board id is not available
[0224.378] Starting CPU & Halting co-processor

[0229.774]
[0229.775] Debug Init done
[0229.778] Marked DTB cacheable
[0229.781] Bootloader DTB loaded at 0x83000400
[0229.785] DeviceTree Init done
[0229.797] Pinmux applied successfully
[0229.801] gicd_base: 0x50041000
[0229.805] gicc_base: 0x50042000
[0229.808] Interrupts Init done
[0229.812] Using base:0x60005090 & irq:208 for tick-timer
[0229.817] Using base:0x60005098 for delay-timer
[0229.821] platform_init_timer: DONE
[0229.825] Timer(tick) Init done
[0229.829] osc freq = 38400 khz
[0229.833]
[0229.834] welcome to cboot
[0229.836]
[0229.838] Cboot Version: 00.00.2018.01-t210-21e03500
[0229.843] calling constructors
[0229.845] initializing heap
[0229.848] initializing threads
[0229.851] initializing timers
[0229.854] creating bootstrap completion thread
[0229.858] top of bootstrap2()
[0229.861] CPU: ARM Cortex A57
[0229.864] CPU: MIDR: 0x411FD071, MPIDR: 0x80000000
[0229.869] initializing platform
[0229.872] Scratch reg 37 & 271 initial value set…
[0229.878] cboot:secure-pmc present
[0229.976] config for ddr50 mode completed
[0229.981] sdmmc node status = disabled
[0229.984] sdmmc node status is disabled
[0229.989] sdmmc node status = disabled
[0229.993] sdmmc node status is disabled
[0229.997] sdmmc node status = disabled
[0230.001] sdmmc node status is disabled
[0230.006] sdmmc node status = okay
[0230.009] sdmmc node is non-removable
[0230.012] Instance: 0
[0230.014] Allocating memory for context
[0230.018] enabling clock
[0230.021] sd card init
[0230.023] Check card present and stable
[0230.027] Send command 0
[0230.033] Error in command_complete 18001 int_status
[0230.040] Error in command_complete 18001 int_status
[0230.047] Error in command_complete 18001 int_status
[0230.052] sending the command failed 0xffffffec in sdmmc_send_command at 109
[0230.059] Sending CMD_SD_SEND_IF_COND failed
[0230.063] Retrying CMD0/CMD8 sequence …
[0230.067] Send command 0
[0230.073] Error in command_complete 18001 int_status
[0230.080] Error in command_complete 18001 int_status
[0230.087] Error in command_complete 18001 int_status
[0230.092] sending the command failed 0xffffffec in sdmmc_send_command at 109
[0230.099] Sending CMD_SD_SEND_IF_COND failed
[0230.103] Identify SD card failed 0xffffffec in sdmmc_init at 1127
[0230.120] error opening sdcard-0
[0230.123] of_register: registering tegra_udc to of_hal
[0230.128] of_register: registering tegra_udc to of_hal
[0230.133] of_register: registering inv20628-driver to of_hal
[0230.139] of_register: registering ads1015-driver to of_hal
[0230.144] of_register: registering lp8557-bl-driver to of_hal
[0230.150] of_register: registering bq2419x_charger to of_hal
[0230.155] of_register: registering cpc to of_hal
[0230.160] of_register: registering bq27441_fuel_gauge to of_hal
[0230.171] gpio framework initialized
[0230.175] of_register: registering tca9539_gpio to of_hal
[0230.180] of_register: registering tca9539_gpio to of_hal
[0230.186] of_register: registering i2c_bus_driver to of_hal
[0230.191] of_register: registering i2c_bus_driver to of_hal
[0230.197] of_register: registering i2c_bus_driver to of_hal
[0230.202] of_register: registering i2c_bus_driver to of_hal
[0230.208] pmic framework initialized
[0230.211] of_register: registering max77620_pmic to of_hal
[0230.217] regulator framework initialized
[0230.221] of_register: registering tps65132_bl_driver to of_hal
[0230.227] initializing target
[0230.232] gpio_driver_register: register ‘tegra_gpio_driver’ driver
[0230.241] fixed regulator driver initialized
[0230.258] initializing OF layer
[0230.262] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0230.278] I2C Bus Init done
[0230.281] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0230.291] I2C Bus Init done
[0230.294] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0230.304] I2C Bus Init done
[0230.307] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0230.317] I2C Bus Init done
[0230.320] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0230.330] I2C Bus Init done
[0230.333] of_children_init: Ops found for compatible string maxim,max77620
[0230.343] max77620_init using irq 118
[0230.348] register ‘maxim,max77620’ pmic
[0230.352] gpio_driver_register: register ‘max77620-gpio’ driver
[0230.358] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0230.369] I2C Bus Init done
[0230.372] Applying platform configs
[0230.379] platform-init is not present. Skipping
[0230.383] calling apps_init()
[0230.386] Failed to open “sd0” for publishing partitions
[0230.391] Proceeding to flashing Server
[0230.395] usbdcd_reinit Initialize driver to use already enumerated device
[0230.402] nv3p_priv_usbf_open USB configuration success
[0230.500] populate_storage_info: failed to open sd0 !
[0230.505] populate_platform_info: failed to populate storage info
[0230.511] pre_process_oem_commands: failed to populate platform info
[0230.517] pre_process_oem_commands: failed to process oem commands
[0230.524] oem_commands: processing oem command failed
[0260.344] max77620_clear_syswdt clearing watchdog
[0290.344] max77620_clear_syswdt clearing watchdog
[0320.344] max77620_clear_syswdt clearing watchdog
[0350.345] max77620_clear_syswdt clearing watchdog
[0380.345] max77620_clear_syswdt clearing watchdog
[0410.345] max77620_clear_syswdt clearing watchdog
[0440.345] max77620_clear_syswdt clearing watchdog
[0470.345] max77620_clear_syswdt clearing watchdog
[0500.345] max77620_clear_syswdt clearing watchdog
[0530.346] max77620_clear_syswdt clearing watchdog
[0560.346] max77620_clear_syswdt clearing watchdog
[0590.346] max77620_clear_syswdt clearing watchdog
[0620.346] max77620_clear_syswdt clearing watchdog
[0650.346] max77620_clear_syswdt clearing watchdog
[0680.346] max77620_clear_syswdt clearing watchdog
[0710.346] max77620_clear_syswdt clearing watchdog
[0740.347] max77620_clear_syswdt clearing watchdog
[0770.347] max77620_clear_syswdt clearing watchdog
[0800.347] max77620_clear_syswdt clearing watchdog
[0830.347] max77620_clear_syswdt clearing watchdog
[0860.347] max77620_clear_syswdt clearing watchdog
[0890.347] max77620_clear_syswdt clearing watchdog
[0920.348] max77620_clear_syswdt clearing watchdog
[0950.348] max77620_clear_syswdt clearing watchdog
[0980.348] max77620_clear_syswdt clearing watchdog
[1010.348] max77620_clear_syswdt clearing watchdog
[1040.348] max77620_clear_syswdt clearing watchdog
[1070.348] max77620_clear_syswdt clearing watchdog
[1100.349] max77620_clear_syswdt clearing watchdog
[1130.349] max77620_clear_syswdt clearing watchdog
[1160.349] max77620_clear_syswdt clearing watchdog
[1190.349] max77620_clear_syswdt clearing watchdog
[1220.349] max77620_clear_syswdt clearing watchdog
[1250.349] max77620_clear_syswdt clearing watchdog
[1280.349] max77620_clear_syswdt clearing watchdog
[1310.350] max77620_clear_syswdt clearing watchdog
[1340.350] max77620_clear_syswdt clearing watchdog
[1370.350] max77620_clear_syswdt clearing watchdog
[1400.350] max77620_clear_syswdt clearing watchdog
[1430.350] max77620_clear_syswdt clearing watchdog
[1460.350] max77620_clear_syswdt clearing watchdog
[1490.351] max77620_clear_syswdt clearing watchdog
[1520.351] max77620_clear_syswdt clearing watchdog
[1550.351] max77620_clear_syswdt clearing watchdog
[1580.351] max77620_clear_syswdt clearing watchdog
[1610.351] max77620_clear_syswdt clearing watchdog
[1640.351] max77620_clear_syswdt clearing watchdog
[1670.351] max77620_clear_syswdt clearing watchdog
[1700.352] max77620_clear_syswdt clearing watchdog
[1730.352] max77620_clear_syswdt clearing watchdog
[1760.352] max77620_clear_syswdt clearing watchdog
[1790.352] max77620_clear_syswdt clearing watchdog
[1820.352] max77620_clear_syswdt clearing watchdog
[1850.352] max77620_clear_syswdt clearing watchdog
[1880.353] max77620_clear_syswdt clearing watchdog
[1910.353] max77620_clear_syswdt clearing watchdog
[1940.353] max77620_clear_syswdt clearing watchdog
[1970.353] max77620_clear_syswdt clearing watchdog
[2000.353] max77620_clear_syswdt clearing watchdog
[2030.353] max77620_clear_syswdt clearing watchdog
[2060.354] max77620_clear_syswdt clearing watchdog

Could you share the flash command you are using?

I’m newbie with jetson b’d
And I’m just using sdkmanager for flashing
Is there any console commands to flashing with command line ?

Then could you share what did you choose when running sdkmanager?

As #2, you could check quick start guide.

Search the command “sudo ./flash”

I read the quick start guides but sdk manager installation incudes board write process.

And there are no instruction for emmc model (only for sd model)

And my jetson module has emmc (it means there are no sd socket)

because of installation process are not finished with final step. (Stucks on writing board) I can’t move to next steps.

Can i finishing sdk manager installation without the writing the board ?

And if there are separate process for emmc model, can i get the cli commands for emmc only model ?

According to your log, it is possible you are flashing your board with sdcard module config.

The quick start guide points out below.

4. Enter these commands on your Linux host to install (flash) the L4T release onto the
   Jetson developer kit:

   sudo ./flash.sh ${BOARD} mmcblk0p1

   This takes about 10 minutes, or more on a slow host computer.

The value of the environment variable $(board) determines the configuration that the flashing
script uses. The list below gives information on the available config file options for each
Jetson Module.

1. Jetson Nano (P3448) - Included with Jetson Nano Developer Kit. Has microSD card slot instead
   of eMMC for storage.
	jetson-nano-qspi 	Flashes QSPINOR memory.
	jetson-nano-qspi-sd 	Flashes both QSPINOR memory & SD card.

[b]2. Jetson Nano (P3448-0020) - For use in production devices.
	jetson-nano-emmc 	Flashes eMMC memory.[/b]

Sdkmanager is just a tool which also uses this flash.sh tool. You should be able to find Linux_for_Tegra folder on your host now.

Also, if you still want to keep using sdkmanager, please make sure you choose the board “3448-0020”.

thank-you WayneWWW

I can complete flashing : )