The boards I use are jetson tx2 nx core board and custom carrier board. In order to make the hdmi output of sor0 effective, I updated the dtb file. I compiled the modified dts in /public_sources/Linux_for_Tegra/source/public/kernel_src, and copied the compiled tegra186-p3636-0001-p3509-0000-a01.dtb file to the /boot/dtb directory. I have modified the extlinux.config file.
The /boot/extlinux/extlinux.config file is as follows:
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
FDT /boot/dtb/tegra186-p3636-0001-p3509-0000-a01.dtb
INITRD /boot/initrd
APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2
I put tegra186-p3636-0001-p3509-0000-a01.dtb into $(HOME)/nvidia/nvidia_sdk/JetPack_4.6.3_Linux_JETSON_TX2_TARGETS/L inux_for_Tegra/kernel/dtb directory. Use command sudo ./flash.sh -r -k DTB jetson-xavier-nx-devkit-tx2-nx mmcblk0p1 in host PC with ubuntu 18.04 OS to flash it. The attachment is the dts file generated from tegra186-p3636-0001-p3509-0000-a01.dtb using DTC tool. tegra186-p3636-0001-p3509-0000-a01.dts (239.2 KB)
I’ve moved your topic to correct category for TX2.
From your flash log, you are using tegra186-p3636-0001-p3509-0000-a01.dtb as device tree.
Is there any issue after you flash the board to update the device tree?
Your previous command is used to flash the partition for DTB, but it might still using the dtb (because -r option means using exist system.img) under /boot/dtb/ so that I suggest you to flash the whole board and it would also update the dtb files in rootfs.