Error at first boot: [0000.167] E> NONE: Invalid value MemBct dram size: 0MB for slot: 0

Robotics & Edge Computing Jetson Systems Jetson Xavier NX
1

Dear Nvidia Support,

We have been using Xavier NX (P3668) 16GB eMMC model since 2023. I created massflash blob based on JetPack 4.6 / L4T R32.6.1. It has worked well until lately. With some P3668 modules the massflash claimed successful. But the cold boot hits error. Console output is as following:

========

[0000.025] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0000.034] I> MB1 (prd-version: 1.5.1.7-t194-41334769-98030a79)
[0000.039] I> Boot-mode: Coldboot
[0000.042] I> Chip revision : A02P
[0000.045] I> Bootrom patch version : 15 (correctly patched)
[0000.050] I> ATE fuse revision : 0x200
[0000.054] I> Ram repair fuse : 0x0
[0000.057] I> Ram Code : 0x4
[0000.059] 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] W> No valid slot number is found in scratch register
[0000.092] W> Return default slot: _a
[0000.095] I> Active Boot chain : 0
[0000.098] I> Boot-device: QSPI
[0000.101] I> Qspi flash params source = brbct
[0000.107] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0000.114] I> Temperature = 55000
[0000.117] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.122] W> Skipping boost for clk: BPMP_APB
[0000.126] W> Skipping boost for clk: AXI_CBB
[0000.130] W> Skipping boost for clk: AON_CPU_NIC
[0000.134] W> Skipping boost for clk: CAN1
[0000.138] W> Skipping boost for clk: CAN2
[0000.142] I> Boot-device: QSPI
[0000.145] I> Boot-device: QSPI
[0000.147] I> Qspi flash params source = mb1bct
[0000.152] I> Qspi using bpmp-dma
[0000.155] I> Qspi clock source : pllc_out0
[0000.158] I> Qspi reinitialized
[0000.161] I> Qspi flash params source = mb1bct
[0000.167] E> NONE: Invalid value MemBct dram size: 0MB for slot: 0.
[0000.173] E> Task 39 failed (err: 0x102)
[0000.176] E> Top caller module: NONE, error module: NONE, reason: 0x02, aux_info: 0x01
[0000.184] I> MB1(1.5.1.7-t194-41334769-98030a79) BIT boot status dump :
000000000001111111111011111111111111111100010000000000000000000000000000000000000000000000000000000000000
[0000.214] I> Reset to recovery mode

==================

I believe the patch, XNX-16GB-r32.6.1-overlay.tbz2, should be the solution. My questions are:

  1. how can I tell if a module is in 669 level and version >= 301 as stated in the release notes? I tested two modules. A module can boot up has part number 900-83668-0030-000. A module can not boot up with the part number 900-83668-0000-0T0.
  2. Since the files are in the massflash blob, should I copy the files to replace those in the blob, or I need to recreate the massflash blob?

Thanks.

3

Hi stuart.xu,

Are you using the devkit or custom board for Xavier NX?

Is you issue specific to the PCN modules?

We will suggest applying the overlay in BSP package and create the massflash blob.

4

I use the devkit board for flashing.

I am not sure if the non-working modules are thosed mentioned in the PCN.

5

How do you get this overlay package?
Why you think it could help for your case? I thought it is the PCN overlay package so it may help for your issue on specific PCN modules.

Please put the failed modules on the devkit and try flashing with the latest Jetpack(4.6.6 or 5.1.5) to veirfy

6

I searched the error code “Invalid value MemBct dram size: 0MB for slot: 0” in the Forums, all point to the patch in the release notes. So I thought the patch may be a fix for my problem. I can try with it.

BTW, how can I find the model’s level number and version number?

7

It may be found from the outside of the module itself or read from the EEPROM inside the module.
Please clarify if the issue is specific to certain PCN module.

8

I am not sure if the failed module is those mentioned in PCN. One of the failed modules’ part number is 900-83668-0000-0T0, its S/N is 1650425081405.

9

Hi KevinFFF,

I have not installed the JetPack4.6.6. Since there are much customization in my build, I would prefer to seeing if it can be fixed in current JetPack4.6. I collected the flash log and console output with the failed module. Please have a look and advise if I can have a solution for the problem. Thanks.
20260128-163951_19961_flash_1-1-notWork.log (370.1 KB)
console-output-notWork.log (9.6 KB)

10

Okay, it seems you might be affected by PCN210641 as following:

image
image1817×345 29.2 KB

Please apply overlay-xnx-PCN210641-bsp32.5.1.tgz to Jetpack 4.6 to see if it could help for your case.