CBoot flow access USB_Stoarge debug message (Nano4G B01)

An question on boot system from USB_Storage without SD_CARD
I have one USB_Storge already could boot from NANO-4G B01 before.
But suddenly, Nano canot boot from my USB_Storge no reason
After check the USB_Storge from Linux x86 host, it could mounted successful and ls full filesystem partition.
Based on console messages, wwant to know how to confirm whether the nano access USB_Stoarge during cool boot?

  1. The message “Loading kernel from LNX” from CBoot/u-boot say it preparing load linux kenrel?
  2. The boot flow should be CBoot–>u-boot->kernel, But ‘Cboot’ was on chip ROM, right?
  3. In my case, u-boot image and kenrel image storage on USB_Storage, right?

[0002.871] Loading kernel from LNX
[0002.880] Found 19 BFS partitions in “spiflash0”
[0003.205] Failed to validate boot-image
[0003.209] Set to failover in the next boot

https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3271/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/bootflow_jetson_nano.html

[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: 0x2e1d6f
[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=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.234] 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.281] Read PT from (2:0)
[0000.296] Using BFS PT to query partitions
[0000.302] 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

[0001.388] Carveout took -126356 us
[0001.391] CPU initialization took 486792 us
[0001.395] Total time taken by TegraBoot 1346230 us

[0001.400] Starting CPU & Halting co-processor

64NOTICE: BL31: v1.3(release):b5eeb33f7
NOTICE: BL31: Built : 12:09:37, Jul 26 2021
ERROR: Error initializing runtime service trusty_fast
[0001.522] RamCode = 0
[0001.527] LPDDR4 Training: Read DT: Number of tables = 2
[0001.532] EMC Training (SRC-freq: 204000; DST-freq: 1600000)
[0001.545] EMC Training Successful

[0001.682] Welcome to L4T Cboot
[0001.685]
[0001.686] Cboot Version: 00.00.2018.01-t210-c952b4e6
[0001.691] calling constructors
[0001.694] initializing heap
[0001.696] initializing threads
[0001.699] initializing timers
[0001.702] creating bootstrap completion thread
[0001.707] top of bootstrap2()
[0001.709] CPU: ARM Cortex A57
[0001.712] CPU: MIDR: 0x411FD071, MPIDR: 0x80000000
[0001.717] initializing platform
[0001.724] Manufacturer: MF = 0xc2, ID MSB = 0x25

[0002.801] -------> se_aes_verify_sbk_clear: 747
[0002.806] se_aes_verify_sbk_clear: Error
[0002.809] SE operation failed
[0002.812] bl_battery_charging: connected to external power supply
[0002.821] display_console_ioctl: No display init
[0002.826] switch_backlight failed
[0002.832] device_query_partition_size: failed to open partition spiflash0:MSC !
[0002.839] MSC Partition not found
[0002.846] device_query_partition_size: failed to open partition spiflash0:USP !
[0002.853] USP partition read failed!
[0002.856] blob_init: blob-partition USP header read failed
[0002.862] android_boot Unable to update recovery partition
[0002.867] kfs_getpartname: name = LNX
[0002.871] Loading kernel from LNX
[0002.880] Found 19 BFS partitions in “spiflash0”
[0003.205] Failed to validate boot-image
[0003.209] Set to failover in the next boot
[0003.213] fail control word = 0xf6cee890
[0003.216] Rebooting …[0000.157] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.162] Processing in cold boot mode Bootloader 2
[0000.167] A02 Bootrom Patch rev = 1023
[0000.171] Power-up reason: software reset

No, cboot and uboot are both on the QSPI in the SOM.

@WayneWWW Based on console mesages I provided.

  1. What is executed context, cboot or uboot.
  2. From console log. How to know USB_Storage was mounted from loader.

[0002.871] Loading kernel from LNX
[0002.880] Found 19 BFS partitions in “spiflash0”
[0003.205] Failed to validate boot-image
[0003.209] Set to failover in the next boot

Hi,

I feel your bootloader has something corrupted.

You could directly reflash the board first.

@WayneWWW
Thanks your comment. Did you means upgrade bootloader?
Just want to confirm again it is no risk of upgrade loader due to Jetson Nano is A/B system on loader?

https://docs.nvidia.com/jetson/archives/r34.1/DeveloperGuide/text/SD/Bootloader/UpdateAndRedundancy.html#bootloader-update-payload-generator

Hi,

You cannot read rel-34 or rel-35 document because you are using jetson naon which is only to rel-32.

The only document you can refer to is here.
https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3273/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/bootloader_update_nano_tx1.html#wwconnect_header

I didn’t mean upgrade the bootloader. I mean “flash” the bootloader again with the previous version you are using.

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