Why my jetson nano doesn't boot if I use a DTB file?

no. it can’t be. it stucks on nvidia logo from when I bought it. and the boot folder has alwyas been full of files.

root@zioma-desktop:~# dmesg
bash: /usr/bin/dmesg: Errore di input/output

these are the default files saved on the /boot folder of the xubuntu 20.04

these are the default files saved on the /boot folder of ubuntu 18.04

cat /sys/firmware/devicetree/base/compatible

nvidia,p3449-0000-b00+p3448-0000-b00nvidia,jetson-nanonvidia,tegra210

Just grep dts in your dmesg and it will tell which one is in use.

it is full of these errors :

[ 1141.870146] sdhci-tegra sdhci-tegra.0: Tuning done, restoring the best tap value : 22
[ 1142.272372] mmc0: Data CRC error
[ 1142.275636] sdhci: =========== REGISTER DUMP (mmc0)===========
[ 1142.281486] sdhci: Sys addr: 0x00000400 | Version: 0x00000303
[ 1142.287333] sdhci: Blk size: 0x00007200 | Blk cnt: 0x000000a2
[ 1142.293181] sdhci: Argument: 0x08bcadd0 | Trn mode: 0x0000002b
[ 1142.299025] sdhci: Present: 0x01fb0000 | Host ctl: 0x00000017
[ 1142.304869] sdhci: Power: 0x00000001 | Blk gap: 0x00000000
[ 1142.310711] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 1142.316552] sdhci: Timeout: 0x0000000e | Int stat: 0x00000000
[ 1142.322394] sdhci: Int enab: 0x02ff100b | Sig enab: 0x02fc100b
[ 1142.328236] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1142.334079] sdhci: Caps: 0x376cd08c | Caps_1: 0x10006f73
[ 1142.339923] sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1142.345764] sdhci: Host ctl2: 0x0000300b
[ 1142.349698] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000ffefe470
[ 1142.356256] sdhci: ===========================================
[ 1142.368762] sdhci-tegra sdhci-tegra.0: Tuning done, restoring the best tap value : 22
[ 1142.613428] mmc0: Data CRC error
[ 1142.616674] sdhci: =========== REGISTER DUMP (mmc0)===========
[ 1142.622511] sdhci: Sys addr: 0x00000400 | Version: 0x00000303
[ 1142.628346] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000193
[ 1142.634180] sdhci: Argument: 0x08be5f78 | Trn mode: 0x0000002b
[ 1142.640013] sdhci: Present: 0x01fb0000 | Host ctl: 0x00000017
[ 1142.645844] sdhci: Power: 0x00000001 | Blk gap: 0x00000000
[ 1142.651675] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 1142.657507] sdhci: Timeout: 0x0000000e | Int stat: 0x00000000
[ 1142.663339] sdhci: Int enab: 0x02ff100b | Sig enab: 0x02fc100b
[ 1142.669172] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 1142.675004] sdhci: Caps: 0x376cd08c | Caps_1: 0x10006f73
[ 1142.680838] sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[ 1142.686668] sdhci: Host ctl2: 0x0000300b
[ 1142.690592] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000ffefe470
[ 1142.697138] sdhci: ===========================================
[ 1142.709228] sdhci-tegra sdhci-tegra.0: Tuning done, restoring the best tap value : 22

I started to think that it is defective from some time. what do u think.

root@ziomario-desktop:# dmesg | grep dts
[ 0.232162] DTS File Name: /dvs/git/dirty/git-master_linux/kernel/kernel-4.9/arch/arm64/boot/dts/…/…/…/…/…/…/hardware/nvidia/platform/t210/porg/kernel-dts/tegra210-p3448-0000-p3449-0000-b00.dts
[ 0.440849] DTS File Name: /dvs/git/dirty/git-master_linux/kernel/kernel-4.9/arch/arm64/boot/dts/…/…/…/…/…/…/hardware/nvidia/platform/t210/porg/kernel-dts/tegra210-p3448-0000-p3449-0000-b00.dts
[ 0.469084] tegra-pmc 7000e400.pmc: scratch reg offset dts data not present

the flash procedure erase everything on the ssd card ? I have a doubt. If I flash the board,the installed xubuntu 20.04 will gone away ? is the answer is yes,It makes no sense at all to do that,because inside that custom ubuntu image have been applied all the patches needed to run windows 10 arm + qemu and kvm. I can’t destroy it.

I only asked you to flash your dtb. The command also only flashes the dtb.

But actually I also don’t think it is worthy of keeping this sdcard anymore if it keeps giving you kernel panic.

If you want to check if the board is defective or not, use another sdcard and flash the board with pure jetpack.

I’ve just connected the serial console and I created a log file. Do u want to give a look ? It has captured the reason why it usually does not want to boot. it is here :

SoC: tegra210
Model: NVIDIA Jetson Nano Developer Kit
Board: NVIDIA P3450-0000
DRAM: 4 GiB
MMC: sdhci@700b0000: 1, sdhci@700b0600: 0
Loading Environment from SPI Flash… SF: Detected mx25u3235f with page size 25B
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
starting USB…
Bus usb@7d000000: tegrausb: Invalid dr_mode 2 for host mode
probe failed, error -1
Bus xusb@70090000:
Firmware size 124416
Firmware timestamp: 0x5da88fc3, Version: 50.25 release

Register HCSParams1: 9000124 NbrPorts: 9
Starting the controller
USB XHCI 1.00
scanning bus xusb@70090000 for devices… 3 USB Device(s) found
scanning usb for storage devices… 0 Storage Device(s) found

Device 0: unknown device

Device 0: unknown device

That log says the system not able to load the kernel at all because the sd card is not able to get read.

If that only happens after you use that DTB, then it is not hardware defect

man,I’m not using any FDT argument on the sd card with the xubuntu 20.04. I have commented out the line. It has troubles booting even with the line commented. this is the extlinux.conf file

TIMEOUT 30
DEFAULT primary

MENU TITLE L4T boot options

LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image_kvm
#FDT /boot/b0-0000-kvm.dts
INITRD /boot/initrd
APPEND ${cbootargs}

can u tell me if I will destroy all the content of the sd card if I flash only the DTB file ?

The current issue is not related to DTB anymore.
No need to do any flash DTB only work.

Please just find another sdcard, flash it with whole sdkmanager and see if the board is still working.

yes I can boot the nano with the other sd card that I have,where I have installed ubuntu 18.04 with the latest jetpack. in that case the problem is the same. if I use a FDT argument,the board will freezes on the nvidia logo. and I need to use that KVM custom dts file because otherwise,windows 10 arm will not boot. (I read on the forum that it works like this). So,if on this sd card I’m using the latest jetpack and it won’t boot anyway with the FDT argument,the problem where is ? let’s see. now I will produce another log for this sd card.

Maybe you can do the things step by step instead of jumping too much.

Please check if this issue is due to “using FDT to point to dtb” or because of “the KVM dtb is not compatible “

For example, if you can point the FDT to original dtb and it boots up fine, then “using FDT” itself has no problem.

Also, share the log after you try anything.

here we go. this conf file :

produces this log : Tegra210 (P3450-0000) # ��[0000.125] [L4T TegraBoot] (version 00.00.2018.01-l4t) - Pastebin.com

(I’m with ubuntu 18.04 ; the latest jetpack)