XNX always goes into recovery mode?

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hi NV_Team,

We have two XNX devices working for several days, one XNX run software reboot then can’ t bring up and lsusb on PC seems XNX in recovery mode. We take the XNX SOM and plug on the XNX Devkit CVB still in recovery mode. Here is the uart log. Please help to check it.
Thanks.

UART Log :

I> rst_source : 0x0
[0000.062] I> rst_level : 0x0
[0000.065] I> Boot-device: QSPI
[0000.068] I> Qspi flash params source = brbct
[0000.072] I> Qspi using bpmp-dma
[0000.075] I> Qspi clock source : pllp
[0000.079] I> QSPI Flash Size = 32 MB
[0000.082] I> Qspi initialized successfully
[0000.086] I> Active Boot chain : 1
[0000.089] I> Boot-device: QSPI
[0000.092] I> Qspi flash params source = brbct
[0000.098] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0000.105] I> Temperature = 28000
[0000.108] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.113] W> Skipping boost for clk: BPMP_APB
[0000.117] W> Skipping boost for clk: AXI_CBB
[0000.121] W> Skipping boost for clk: AON_CPU_NIC
[0000.125] W> Skipping boost for clk: CAN1
[0000.129] W> Skipping boost for clk: CAN2
[0000.133] I> Boot-device: QSPI
[0000.136] I> Boot-device: QSPI
[0000.139] I> Qspi flash params source = mb1bct
[0000.143] I> Qspi using bpmp-dma
[0000.146] I> Qspi clock source : pllc_out0
[0000.150] I> Qspi reinitialized
[0000.152] I> Qspi flash params source = mb1bct
[0000.158] E> NONE: Invalid value MemBct dram size: 0MB for slot: 2.
[0000.164] E> Task 39 failed (err: 0x102)
[0000.167] E> Top caller module: NONE, error module: NONE, reason: 0x02, aux_info: 0x01
[0000.175] I> MB1(1.5.1.6-t194-41334769-1740dd39) BIT boot status dump :
0000000000011111111110111111111111111111000100000000000000000000000000000000000000000000000000000000000000000000000000000000000011011000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0000.205] I> Reset to recovery mode
3

So the module could be flashed by sdkmanager under this situation?

4

Hi Wayne,

Yes.
After re-flash, the module can work.

5

Will that happen again after the reflash?

6

Yes.

After re-flash this module happen again, BTW it happened not fixed.

7

Could you share me the boot log of that module after it got flashed and can boot normally?

8

Hi Wayne,

After re-flash this module boot up normally, and the boot log file.

XNX_Boot_UART_Log.txt (32.2 KB)

9

Which jetpack release was in use here?

10

Hi Wayne,

JetPack4.5

nvidia@nx:~$ cat /etc/nv_tegra_release 
# R32 (release), REVISION: 5.0, GCID: 25531747, BOARD: t186ref, EABI: aarch64, DATE: Fri Jan 15 23:21:05 UTC 2021
11

I think it could be a known issue on jetpack4.5 for some NX modules… please upgrade to jp4.6.1 or later release.

12

Hi Wayne,

Thanks.
We will try to upgrade to Jetpack4.6.1 .

What is the known issue on JetPack4.5 for some NX modules ?

13

The ram code behavior has some problem which may lead to wrong RAM code got in use.

15

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