Hi Team,
I am using Jetson Nano 4GB dev kit. When I try to power it up, Power LED remains ON for few seconds and then it goes off. I am using 15W adapter(5V, 3A). Please suggest.
Please get the serial console log:
Sure, Please allow me sometime I will get back to you.
Hi,
I tried to work on Serial Debug Console(by referring to above blog) but no luck, I could not proceed further after selecting serial port setup. I am using Ubuntu 18 OS on my host. I am attaching the video clip for your reference.
Please suggest.
Uploading: serial_debug_console.mp4…
Your upload didn’t even succeed.
Hi,
I am trying to upload the screen record, do not know why it is not taking.
But As I mentioned in my previous reply, I am not able to proceed further after selecting serial port setup. It is prompting me to the first page. So I could not configure the serial port setup.
Please help me what to do next.
Any tools that are capable of serial communication should do it.
Try screen or picocom if minicom does not work for you.
Hi Dave,
Thanks. Picocom worked for me. Please find the serial console log below:
picocom v2.2
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : yes
nolock is : yes
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
Type [C-a] [C-h] to see available commands
Terminal ready
[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 = 0
[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: 0xb2742
[0000.172] Entering ramdump check
[0000.175] Get RamDumpCarveOut = 0x0
[0000.178] 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.198] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.204] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.210] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.216] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.222] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.228] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.233] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.250] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.256] Platform-DebugCarveout: 0
[0000.259] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.265] Non secure mode, and RB not enabled.
[0000.269] BoardID = 3448, SKU = 0x0
[0000.272] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.276] Nano-SD: checking PT table on QSPI …
[0000.280] Read PT from (2:0)
[0000.296] Using BFS PT to query partitions
[0000.301] Loading Tboot-CPU binary
[0000.330] Verifying TBC in OdmNonSecureSBK mode
[0000.340] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.347] Bootloader downloaded successfully.
[0000.351] Downloaded Tboot-CPU binary to 0xa0000258
[0000.356] MAX77620_GPIO5 configured
[0000.359] CPU power rail is up
[0000.362] CPU clock enabled
[0000.366] Performing RAM repair
[0000.369] Updating A64 Warmreset Address to 0xa00002e9
[0000.374] BoardID = 3448, SKU = 0x0
[0000.377] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.381] Nano-SD: checking PT table on QSPI …
[0000.385] Loading NvTbootBootloaderDTB
[0000.452] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.523] Bootloader DTB Load Address: 0x83000000
[0000.528] BoardID = 3448, SKU = 0x0
[0000.531] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.535] Nano-SD: checking PT table on QSPI …
[0000.540] Loading NvTbootKernelDTB
[0000.606] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.678] Kernel DTB Load Address: 0x83100000
[0000.683] BoardID = 3448, SKU = 0x0
[0000.686] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.690] Nano-SD: checking PT table on QSPI …
[0000.696] Loading cboot binary
[0000.812] Verifying EBT in OdmNonSecureSBK mode
[0000.853] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0000.860] Bootloader downloaded successfully.
[0000.865] BoardID = 3448, SKU = 0x0
[0000.868] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.872] Nano-SD: checking PT table on QSPI …
[0000.876] PT: Partition NCT NOT found !
[0000.880] Warning: Find Partition via PT Failed
[0000.884] Next binary entry address: 0x92c00258
[0000.889] BoardId: 3448
[0000.893] Overriding pmu board id with proc board id
[0000.898] Display board id is not available
[0000.902] BoardID = 3448, SKU = 0x0
[0000.906] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.909] Nano-SD: checking PT table on QSPI …
[0001.014] Verifying SC7EntryFw in OdmNonSecureSBK mode
[0001.071] /bpmp deleted
[0001.073] SC7EntryFw header found loaded at 0xff700000
[0001.269] OVR2 PMIC
[0001.271] Bpmp FW successfully loaded
[0001.274] BoardID = 3448, SKU = 0x0
[0001.277] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.281] Nano-SD: checking PT table on QSPI …
[0001.287] WB0 init successfully at 0xff780000
[0001.291] Set NvDecSticky Bits
[0001.294] GSC2 address ff53fffc value c0edbbcc
[0001.301] GSC MC Settings done
[0001.303] BoardID = 3448, SKU = 0x0
[0001.307] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0001.311] Nano-SD: checking PT table on QSPI …
[0001.316] TOS Image length 53680
[0001.319] Monitor size 53680
[0001.322] OS size 0
[0001.337] Secure Os Aes-CMAC Verification Failed!
[0001.342] Error in NvTbootValidateTOS [11]
[0001.345] Validation of secure os failed!
[0001.349] Device Shutdown called …
Looks like re-flash with SDK Manager is required.
Yes Dave, I could find similar query in the below link and SDK manager helped to resolve it.
I will try to flash it with SDK manager and get back to you.
Hi Dave,
I am trying to reflash my Jetson kit with the sdkmanager. But it is getting stuck at the BSP phase and after some time I will notify me that “flashing is taking long time” and failing. Kindly help me resolve this. I am attaching the SDK logfiles FYR.
SDKM_logs_JetPack_4.6.3_Linux_for_Jetson_Nano_modules_2024-06-05_15-20-13.zip (345.3 KB)
Please dump the serial console log during flashing.
Hi Dave,
Please find the Serial Console Log below:
picocom v2.2
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : yes
nolock is : yes
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
Type [C-a] [C-h] to see available commands
Terminal ready
[0698.472] Enabled early print
[0698.475] [L4T TegraBoot] (version ������"�~��
@��Z�t����)
[0698.480] Processing in recovery mode
[0698.484] A02 Bootrom Patch rev = 1023
[0698.487] Power-up reason: pmc por
[0698.491] Established communication link with host
[0699.554] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0699.562] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0699.570] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0002.075] Enabled early print
[0002.078] [L4T TegraBoot] (version ������"�~��
@��Z�t����)
[0002.083] Processing in recovery mode
[0002.087] A02 Bootrom Patch rev = 1023
[0002.090] Power-up reason: software reset
[0002.094] Established communication link with host
[0003.149] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0003.157] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0003.165] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0002.220] Enabled early print
[0002.223] [L4T TegraBoot] (version ������"�~��
@��Z�t����)
[0002.229] Processing in recovery mode
[0002.232] A02 Bootrom Patch rev = 1023
[0002.236] Power-up reason: software reset
[0002.239] Established communication link with host
[0003.295] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0003.303] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0003.311] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0114.143] Enabled early print
[0114.146] [L4T TegraBoot] (version ������"�~��
@��Z�t����)
[0114.152] Processing in recovery mode
[0114.155] A02 Bootrom Patch rev = 1023
[0114.159] Power-up reason: software reset
[0114.163] Established communication link with host
[0115.200] Odmdata from BCT: 0x000a4000
[0115.204] DebugPort= 0x3
[0115.206] SkipQspiOnly= 0x0
[0115.259] BoardId read from EEPROM/NCT: 3448
[0115.263] BoardID = 3448, SKU = 0x0
[0115.290] NvTbootInit_Porg: Setting GPIO_A6 for HDMI …
[0115.295] max77620 setting MBLPD bit
[0115.299] No Battery Present
[0115.301] RamCode = 0
[0115.304] Platform has DDR4 type RAM
[0115.307] max77620 disabling SD1 Remote Sense
[0115.311] Setting DDR voltage to 1125mv
[0115.315] Serial Number of Pmic Max77663: 0xb2742
[0115.323] Entering ramdump check
[0115.326] Get RamDumpCarveOut = 0x0
[0115.329] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0115.335] Last reboot was clean, booting normally!
[0115.339] Sdram initialization is successful
[0115.343] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0115.349] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0115.355] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0115.361] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0115.367] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0115.373] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0115.379] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0115.385] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0115.401] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0115.407] Platform-DebugCarveout: 0
[0115.410] Downloaded BCT successfully
[0115.648] Downloaded Bootloader successfully
[0115.704] Downloaded rp1 successfully
[0115.783] MAX77620_GPIO5 configured
[0115.786] CPU power rail is up
[0115.789] CPU clock enabled
[0115.793] Performing RAM repair
[0115.796] Updating A64 Warmreset Address to 0x92c002e9
[0115.802] Enable APE clock/reset
[0115.805] Error in NvTbootGetTOSBinaryLength: 0x11 !
[0115.810] Loading Secure OS image failed.
[0115.814] Set NvDecSticky Bits
[0115.818] GSC2 address ff53fffc value c0edbbcc
[0115.824] GSC MC Settings done
[0115.828] Next binary entry address: 0x92c00258
[0115.832] BoardId: 3448
[0115.835] Overriding pmu board id with proc board id
[0115.840] Display board id is not available
[0115.844] Starting CPU & Halting co-processor
[0118.635]
[0118.636] Debug Init done
[0118.639] Marked DTB cacheable
[0118.642] Bootloader DTB loaded at 0x83000400
[0118.647] DeviceTree Init done
[0118.660] Pinmux applied successfully
[0118.664] gicd_base: 0x50041000
[0118.668] gicc_base: 0x50042000
[0118.671] Interrupts Init done
[0118.675] Using base:0x60005090 & irq:208 for tick-timer
[0118.680] Using base:0x60005098 for delay-timer
[0118.685] platform_init_timer: DONE
[0118.688] Timer(tick) Init done
[0118.692] osc freq = 38400 khz
[0118.696]
[0118.697] Welcome to L4T Cboot
[0118.700]
[0118.701] Cboot Version: 00.00.2018.01-t210-a2f2e4b8
[0118.706] calling constructors
[0118.709] initializing heap
[0118.711] initializing threads
[0118.714] initializing timers
[0118.717] creating bootstrap completion thread
[0118.722] top of bootstrap2()
[0118.724] CPU: ARM Cortex A57
[0118.727] CPU: MIDR: 0x411FD071, MPIDR: 0x80000000
[0118.732] initializing platform
[0118.740] Manufacturer: MF = 0xc2, ID MSB = 0x25
[0118.744] ID LSB = 0x36, ID-CFI len = 194 bytes
[0118.749] Macronix QSPI chip present
[0118.752] SPI device register
[0118.755] init boot device
[0118.758] allocating memory for boot device(SPI)
[0118.762] registering boot device
[0118.771] sdmmc node status = okay
[0118.775] sdcard instance = 0
[0118.778] sdmmc cd-inverted
[0118.780] sdcard gpio handle 0x5b
[0118.783] sdcard gpio pin 0xc9
[0118.786] sdcard gpio flags 0x0
[0118.789] vmmc-supply 0x9d
[0118.792] Instance: 0
[0118.794] Allocating memory for context
[0118.798] enabling clock
[0118.800] sd card init
[0118.803] Check card present and stable
[0118.806] Send command 0
[0118.813] Error in command_complete 18001 int_status
[0118.820] Error in command_complete 18001 int_status
[0118.827] Error in command_complete 18001 int_status
[0118.832] sending the command failed 0xffffffec in sdmmc_send_command at 109
[0118.839] Sending CMD_SD_SEND_IF_COND failed
[0118.843] Retrying CMD0/CMD8 sequence …
[0118.847] Send command 0
[0118.853] Error in command_complete 18001 int_status
[0118.860] Error in command_complete 18001 int_status
[0118.867] Error in command_complete 18001 int_status
[0118.872] sending the command failed 0xffffffec in sdmmc_send_command at 109
[0118.879] Sending CMD_SD_SEND_IF_COND failed
[0118.883] Identify SD card failed 0xffffffec in sdmmc_init at 1127
[0118.899] error opening sdcard-0
[0118.902] of_register: registering tegra_udc to of_hal
[0118.907] of_register: registering inv20628-driver to of_hal
[0118.913] of_register: registering ads1015-driver to of_hal
[0118.919] of_register: registering lp8557-bl-driver to of_hal
[0118.924] of_register: registering bq2419x_charger to of_hal
[0118.930] of_register: registering bq27441_fuel_gauge to of_hal
[0118.942] gpio framework initialized
[0118.945] of_register: registering tca9539_gpio to of_hal
[0118.951] of_register: registering tca9539_gpio to of_hal
[0118.956] of_register: registering i2c_bus_driver to of_hal
[0118.962] of_register: registering i2c_bus_driver to of_hal
[0118.967] of_register: registering i2c_bus_driver to of_hal
[0118.973] pmic framework initialized
[0118.976] of_register: registering max77620_pmic to of_hal
[0118.982] regulator framework initialized
[0118.986] of_register: registering tps65132_bl_driver to of_hal
[0118.991] initializing target
[0118.997] gpio_driver_register: register ‘tegra_gpio_driver’ driver
[0119.006] board ID = D78, board SKU = 0
[0119.010] Skipping Z3!
[0119.015] fixed regulator driver initialized
[0119.033] initializing OF layer
[0119.037] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0119.055] I2C Bus Init done
[0119.057] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0119.068] I2C Bus Init done
[0119.070] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0119.081] I2C Bus Init done
[0119.083] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0119.094] I2C Bus Init done
[0119.096] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0119.107] I2C Bus Init done
[0119.109] of_children_init: Ops found for compatible string maxim,max77620
[0119.120] max77620_init using irq 118
[0119.125] register ‘maxim,max77620’ pmic
[0119.129] gpio_driver_register: register ‘max77620-gpio’ driver
[0119.135] of_children_init: Ops found for compatible string nvidia,tegra210-i2c
[0119.146] I2C Bus Init done
[0119.149] Applying platform configs
[0119.156] platform-init is not present. Skipping
[0119.161] calling apps_init()
[0119.164] Failed to open “sd0” for publishing partitions
[0119.169] Proceeding to flashing Server
[0119.173] usbdcd_reinit Initialize driver to use already enumerated device
[0119.180] nv3p_priv_usbf_open USB configuration success
[0119.229] populate_storage_info: failed to open sd0 !
[0119.234] populate_platform_info: failed to populate storage info
[0119.240] pre_process_oem_commands: failed to populate platform info
[0119.246] pre_process_oem_commands: failed to process oem commands
[0119.252] oem_commands: processing oem command failed
Have you tried other SD cards?
I did not try with different SD cards, but I tried with one single SD card for multiple times. But it was not booting.
Get another one if possible.
Sure I will do it.
But why SDK manager boot is not working? If this is not working I am not sure whether SD card boot will work even after changing the SD card.
Just for my understanding,
Apparently the card is not getting detected correctly.
I am trying to boot it on internal emmc. So SD card should not matter.
Uh, OK.
So you are using a eMMC module instead of an SD card module?
Then please RMA the device.