Jetson Nano hybrid board (P3450-0000 with eMMC) - kernel hangs after bootconsole enabled

Robotics & Edge Computing Jetson Systems Jetson Nano
1

I bought a Jetson Nano on Amazon and discovered it’s a hybrid board - it reports as P3450-0000 (Developer Kit) but has an internal eMMC storage. DRAM is 2GB.

Symptoms:

  • Kernel always hangs after: [0.000000] bootconsole [uart8250] enabled

  • No further output, then reboot loop

  • Happens with both tegra210-p3448-0002-p3449-0000-b00.dtb and tegra210-p3448-0003-p3542-0000.dtb

What I tried:

  • Flashed JetPack 4.6.6 via SDK Manager multiple times

  • Manual U-Boot boot with different DTB files

  • Disabled gdm3, blacklisted camera module

  • Removed quiet from bootargs - no additional kernel output

Question: Which DTB file is correct for a 2GB board that reports as P3450-0000 but has eMMC? Could this be a CMA memory issue?

Thanks!

3

How did you tell the DRAM is 2GB? This kind of product didn’t exist.
It could be a missing PCN overlay error.

4

sorry i ment 4gb ram

i have bougt it from amazon here is the link

5

Please add this overlay file and flash your board again.

Overlay_PCN211181_r32.7.5.tbz2

6

Hi WayneWWW,

Update: I downloaded the PCN211181 overlay, applied it to my Linux_for_Tegra folder, and re-flashed the board using: sudo ./flash.sh jetson-nano-emmc mmcblk0p1

Unfortunately, the result is exactly the same:

  1. The UART log still shows: Board: NVIDIA P3450-0000 and DRAM: 2 GiB.

  2. The kernel still hangs/loops at: [ 0.000000] bootconsole [uart8250] enabled.

As I mentioned, the board was sold as a 4GB RAM version and physically appears to have the 4GB module, but the software seems stuck in this 2GB/P3450 identification.

Is there any way to force the installer or the bootloader to ignore the EEPROM ID and treat it as a P3448 (4GB) board? Or is there another specific DTB/configuration I should use for these hybrid eMMC boards that report as P3450?

Thanks for your patience!

7

No, your issue has nothing to do with “forcing” anything.

The value got 2GB is a known symptom when you didn’t apply the overlay correctly.

The overlay is to make the DRAM config correctly.

Please be aware that this overlay should not be applied to “Linux_for_Tegra” directly but to run on the “parent directory” of your Linux_for_Tegra.

Also, make sure every of your “P3448_A00_lpddr4_204Mhz_P987.cfg” got overwrite with the overlay correctly. I mean find “P3448_A00_lpddr4_204Mhz_P987.cfg” under your Linux_for_Tegra/bootloader directory and make sure only one file that has this name. If there are multiple, then make sure every of them got updated.