Starting CPU & Halting co-processor PT: Partition LNX NOT found

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

----Jetson Nano eMMC version ----

Booting start UART debugging Message

[0000.220] [L4T TegraBoot] (version 00.00.2018.01-l4t-8728f3cb)
[0000.225] Processing in cold boot mode Bootloader 2
[0000.230] A02 Bootrom Patch rev = 1023
[0000.234] Power-up reason: pmc por
[0000.237] No Battery Present
[0000.239] pmic max77620 reset reason
[0000.243] pmic max77620 NVERC : 0x50
[0000.246] RamCode = 0
[0000.248] Platform has DDR4 type RAM
[0000.252] max77620 disabling SD1 Remote Sense
[0000.256] Setting DDR voltage to 1125mv
[0000.260] Serial Number of Pmic Max77663: 0x62e74
[0000.268] Entering ramdump check
[0000.271] Get RamDumpCarveOut = 0x0
[0000.274] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.279] Last reboot was clean, booting normally!
[0000.283] Sdram initialization is successful
[0000.288] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.294] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.299] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.305] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.311] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.317] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.323] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.329] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.345] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.351] Platform-DebugCarveout: 0
[0000.354] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.360] Non secure mode, and RB not enabled.
[0000.364] *** Booting BFS0.
[0000.367] Initialize FailControl
[0000.370] Read PT from (0:3)
[0000.385] Csd NumOfBlocks=0
[0000.424] PT crc32 and magic check passed.
[0000.428] Using BFS PT to query partitions
[0000.432] PT: Partition LNX NOT found !
[0000.436] *** Booting KFS0.
[0000.438] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.445] BoardID = 3448, SKU = 0x2
[0000.448] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.453] Read GPT from (0:3)
[0000.462] Using GPT Primary to query partitions
[0000.466] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.473] Loading Tboot-CPU binary
[0000.479] Verifying TBC in OdmNonSecureSBK mode
[0000.489] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.496] Bootloader downloaded successfully.
[0000.500] Downloaded Tboot-CPU binary to 0xa0000258
[0000.505] MAX77620_GPIO5 configured
[0000.508] CPU power rail is up
[0000.511] CPU clock enabled
[0000.515] Performing RAM repair
[0000.518] Updating A64 Warmreset Address to 0xa00002e9
[0000.523] BoardID = 3448, SKU = 0x2
[0000.526] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.532] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.538] Loading NvTbootBootloaderDTB
[0000.555] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0000.627] Bootloader DTB Load Address: 0x83000000
[0000.631] BoardID = 3448, SKU = 0x2
[0000.634] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.640] Loading NvTbootKernelDTB
[0000.657] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0000.728] Kernel DTB Load Address: 0x83100000
[0000.732] BoardID = 3448, SKU = 0x2
[0000.736] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.742] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.749] Loading cboot binary
[0000.760] Verifying EBT in OdmNonSecureSBK mode
[0000.801] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0000.808] Bootloader downloaded successfully.
[0000.812] BoardID = 3448, SKU = 0x2
[0000.816] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.822] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.828] PT: Partition NCT NOT found !
[0000.832] Warning: Find Partition via PT Failed
[0000.836] Next binary entry address: 0x92c00258
[0000.840] BoardId: 3448
[0000.845] Overriding pmu board id with proc board id
[0000.850] Display board id is not available
[0000.854] BoardID = 3448, SKU = 0x2
[0000.857] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.863] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.877] Verifying SC7EntryFw in OdmNonSecureSBK mode
[0000.933] /bpmp deleted
[0000.935] SC7EntryFw header found loaded at 0xff700000
[0000.972] /clock@70110000 not present in the kernel dtb
[0000.977] Bpmp FW successfully loaded
[0000.980] BoardID = 3448, SKU = 0x2
[0000.983] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0000.989] NvTbootFailControlDoFailover: No failover; Continuing …
[0000.997] WB0 init successfully at 0xff780000
[0001.001] Verifying NvTbootWb0 in OdmNonSecureSBK mode
[0001.006] Set NvDecSticky Bits
[0001.010] GSC2 address ff53fffc value c0edbbcc
[0001.016] GSC MC Settings done
[0001.019] BoardID = 3448, SKU = 0x2
[0001.022] Not Nano-SD or !QSPI-ONLY, check GPT table first …
[0001.029] TOS Image length 53680
[0001.032] Monitor size 53680
[0001.034] OS size 0
[0001.040] Secure Os AES-CMAC Verification Success!
[0001.044] TOS image cipher info: plaintext
[0001.048] Loading and Validation of Secure OS Successful
[0001.064] SC7 Entry Firmware - 0xff700000, 0x4000
[0001.069] NvTbootPackSdramParams: start.
[0001.074] NvTbootPackSdramParams: done.
[0001.078] Tegraboot started after 149411 us
[0001.082] Basic modules init took 741333 us
[0001.086] Sec Bootdevice Read Time = 54 ms, Read Size = 3682 KB
[0001.091] Sec Bootdevice Write Time = 0 ms, Write Size = 0 KB
[0001.097] Next stage binary read took 7378 us
[0001.101] Carveout took -34773 us
[0001.104] CPU initialization took 240551 us
[0001.108] Total time taken by TegraBoot 954489 us

[0001.113] Starting CPU & Halting co-processor

64NOTICE: BL31: v1.3(release):b5eeb33
NOTICE: BL31: Built : 14:22:20, Apr 20 2022
ERROR: Error initializing runtime service trusty_fast
Unhandled Exception in EL3.
x30 = 0x00000000ff800094
x0 = 0x00000000ff80f000
x1 = 0x0000000000000000
x2 = 0x0000000000000000
x3 = 0x0000000000000040
x4 = 0x0000000000000000
x5 = 0x0000000000000003
x6 = 0x0000000000000008
x7 = 0x00000000ff80d000
x8 = 0x00000000ff8023ec
x9 = 0x0000000000000000
x10 = 0x0000000000000000
x11 = 0x0000000000000000
x12 = 0x0000000000000000
x13 = 0x0000000000000000
x14 = 0x0000000000000000
x15 = 0x0000000000000000
x16 = 0x0000000000000000
x17 = 0x0000000000000000
x18 = 0x0000000000000011
x19 = 0x00000000ff800018
x20 = 0x0000000088000320
x21 = 0x00000000880003d8
x22 = 0x83306903a0872d72
x23 = 0x300269b77a00711d
x24 = 0x0a652e32c2b4541e
x25 = 0x40c0c4ed497ca4c7
x26 = 0xe57268c1965e12ab
x27 = 0x0000000000000001
x28 = 0x0000000000000000
x29 = 0xce28d45218e439b0
scr_el3 = 0x0000000000000238
sctlr_el3 = 0x0000000000cd183f
cptr_el3 = 0x0000000000000000
tcr_el3 = 0x000000008080351d
daif = 0x00000000000003c0
mair_el3 = 0x00000000004404ff
spsr_el3 = 0x00000000600002cc
elr_el3 = 0x00000000fb88038c
ttbr0_el3 = 0x00000000ff814b00
esr_el3 = 0x0000000086000006
far_el3 = 0x00000000fb88038c
spsr_el1 = 0x0000000000000000
elr_el1 = 0x0000000000000000
spsr_abt = 0x0000000000000000
spsr_und = 0x0000000000000000
spsr_irq = 0x0000000000000000
spsr_fiq = 0x0000000000000000
sctlr_el1 = 0x0000000030d00800
actlr_el1 = 0x0000000000000000
cpacr_el1 = 0x0000000000000000
csselr_el1 = 0x0000000000000000
sp_el1 = 0x0000000000000000
esr_el1 = 0x0000000000000000
ttbr0_el1 = 0x0000000000000000
ttbr1_el1 = 0x0000000000000000
mair_el1 = 0x0000000000000000
amair_el1 = 0x0000000000000000
tcr_el1 = 0x0000000000000000
tpidr_el1 = 0x0000000000000000
tpidr_el0 = 0x0000000000000000
tpidrro_el0 = 0x0000000000000000
dacr32_el2 = 0x0000000000000000
ifsr32_el2 = 0x0000000000000000
par_el1 = 0x0000000000000000
mpidr_el1 = 0x0000000080000000
afsr0_el1 = 0x0000000000000000
afsr1_el1 = 0x0000000000000000
contextidr_el1 = 0x0000000000000000
vbar_el1 = 0x0000000000000000
cntp_ctl_el0 = 0x0000000000000000
cntp_cval_el0 = 0x0000000000000000
cntv_ctl_el0 = 0x0000000000000000
cntv_cval_el0 = 0x0000000000000000
cntkctl_el1 = 0x0000000000000002
fpexc32_el2 = 0x0000000000000700
sp_el0 = 0x00000000ff80d5c0
isr_el1 = 0x0000000000000000
cpuectlr_el1 = 0x0000001b00000047
cpumerrsr_el1 = 0x0000000000000000
l2merrsr_el1 = 0x0000000000000000
gicc_hppir = 0x00000000000003ff
gicc_ahppir = 0x00000000000003ff
gicc_ctlr = 0x00000000000001eb
gicd_ispendr regs (Offsets 0x200 - 0x278)
Offset: value
0000000000000200: 0x0000000000000000
0000000000000204: 0x0000000000000000
0000000000000208: 0x0000000000000000
000000000000020c: 0x0000000000000000
0000000000000210: 0x0000000000000000
0000000000000214: 0x0000000000000000
0000000000000218: 0x0000000000000000
000000000000021c: 0x0000000000000000
0000000000000220: 0x0000000000000000
0000000000000224: 0x0000000000000000
0000000000000228: 0x0000000000000000
000000000000022c: 0x0000000000000000
0000000000000230: 0x0000000000000000
0000000000000234: 0x0000000000000000
0000000000000238: 0x0000000000000000
000000000000023c: 0x0000000000000000
0000000000000240: 0x0000000000000000
0000000000000244: 0x0000000000000000
0000000000000248: 0x0000000000000000
000000000000024c: 0x0000000000000000
0000000000000250: 0x0000000000000000
0000000000000254: 0x0000000000000000
0000000000000258: 0x0000000000000000
000000000000025c: 0x0000000000000000
0000000000000260: 0x0000000000000000
0000000000000264: 0x0000000000000000
0000000000000268: 0x0000000000000000
000000000000026c: 0x0000000000000000
0000000000000270: 0x0000000000000000
0000000000000274: 0x0000000000000000
0000000000000278: 0x0000000000000000
000000000000027c: 0x0000000000000000

Jetson Nano has been operating in buildings without human hands for a long time.
It is Embedded communication system.

We want to know What is problems in Jetson Nano Module?

Tested on Another Custom Board. same result.
Not yet, eMMC flash burning.

2

please try to flash the board with sdkmanager first.

3

FIrst. we try to flash eMMC Memory. We want to know what is the problem exactly ?.

4

Hi,

I don’t know. There is no point and no need to analyze what happened at this moment. Flash your module on NV devkit with sdkmanager first.

5

@WayneWWW is right that you’ll have to flash again, but if you want to save something for diagnostics, then:

  • Get a clone of the rootfs (this can be loopback mounted and examined on a host PC).
  • Get a full serial console boot log. The kernel error you listed is only partial, it lacks the stack dump and what occurred prior to this.

Note that this was during exception level 3 (EL3, there is EL0 through EL3). This is not necessarily security related, but that’s the “security” state. Basically, lower exception levels don’t drop to lower levels, and must transition to a higher state (except for the EL3). EL3 is able to transfer to other exception levels. An example is an EL0 user space program talking to a kernel driver, which transitions to EL1. Eventually, if EL1 wants to go back to EL0, you’d see it transition first to EL3, and this would transition back to EL0. What you’re seeing is basically a failure during transition of states (not necessarily a security thing, but the EL3 is considered a security state because it can transition to a lower exception level). If interested, you can read about it here:
https://developer.arm.com/documentation/ddi0488/d/programmers-model/armv8-architecture-concepts/exception-levels
(anything ARMv8 shares this)

One thing I would do with the loopback mounted clone is to examine the output of this:
ls -ltr /var/cache/apt/archives/*

That sorts those files by date, and the last files appearing are the ones most recently updated. This might show you apt updates. If your system does not have any kind of updates (e.g., not networked for that), then this too is a clue. There also might be some logs going back to the original failure in “/var/log” (although log rotation might have eliminated those if you booted too many times).

Incidentally, regarding serial console logs, it is possible that serial console login still works (although I wouldn’t be too optimistic about that since there is an EL3 error).

Almost forgot: If this is a Nano with an SD card, then cloning that is trivial from a Linux PC.

6
  • Get a clone of the rootfs (this can be loopback mounted and examined on a host PC).

We try to mount and clone to PC , But Not Read working.
Is it Partion Fail?

Below
[ 4.1917 ] [ ] 00% <---------- not Act

not read
not read641×576 56.5 KB

7

What was your exact clone command? Is your host a VM? Can we verify if this is an SD card model versus eMMC (you clone the SD card instead of eMMC if it is and SD card model…clone is basically intended for eMMC)?

8

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