Hi,
I have a 4K monitor connected over HDMI but cannot seem to get a 4k output from it. Its with L4TR35.3.1.
dh@dh-desktop:~$ ls /boot/dtb/
kernel_tegra234-p3767-0000-p3768-0000-a0.dtb
dh@dh-desktop:~$ cat /proc/device-tree/nvidia,dtsfilename
/home/hmecd001409/BSP/Jackson/top_dir/kernel_sources/Linux_for_Tegra/source/public/kernel/kernel-5.10/arch/arm64/boot/dts/…/…/…/…/…/…/hardware/nvidia/platform/t23x/p3768/kernel-dts/tegra234-p3767-0000-p3768-0000-a0.dts
dh@dh-desktop:~$ uname -a
Linux dh-desktop 5.10.104 #5 SMP PREEMPT Fri Jun 16 15:23:10 IST 2023 aarch64 aarch64 aarch64 GNU/Linux
dh@dh-desktop:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
1920x1080 60.00*+ 60.00 59.94 50.00 29.97 23.98
1280x720 59.94
1024x768 60.00
800x600 60.32
720x576 50.00
720x480 59.94
640x480 59.94 59.93
Please suggest on this.
1)Do we need to make any change in the DTB?
2)Do we need to check on Hardware?
3)ay other suggestion?
A change in DTB is a must-have…
As for the check for hardware, I don’t know you or your board. I cannot answer…
By default if you flash the board with p3509-xxx-p3767 board config, it will enable HDMI.
p3767-0000-p3768-0000 dtb is for Orin Nano devkit which only has DP port.
Hi,
We have followed the devkit design. I will share the details.
You mean to say we need to modify dtb to make HDMI to work or for 4K HDMI?
We flashed using p3509-xxx-p3767 - so by default it should support 4K HDMI right?
If you see “DP-1” in your xrandr, it means it is still a DP mode driver. Orin Nano devkit only supports DP, so if you use p3768 board config, it will only output DP. Connect a HDMI to it won’t have correct resolution supported.
P3509 is xavier nx devkit. We have a board config to enable it with Orin nano/nx module. This one has HDMI enabled. So using this can have fully HDMI function.
Hi, thank you. can you share the details of board cofig and where to make changes?
Check your Linux_for_Tegra directory and you will find the board config…
we use initrd to flash the device, so which config file I should use in this case?
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal
A change in DTB is a must-have…
As for the check for hardware, I don’t know you or your board. I cannot answer…
By default if you flash the board with p3509-xxx-p3767 board config, it will enable HDMI.
p3767-0000-p3768-0000 dtb is for Orin Nano devkit which only has DP port.
Use ls *.conf command in your Linux_for_Tegra directory and read above comment.
Hi,
I am little confused here:
1)I want to enable HDMI with 4K in Orin NX
2)I used flash command as to flash external NVMe sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal to flash
3)I am not exctly getting what are the changes required or where to make changes
should I change only config files? where and what changes?
4)Do I need to change the dtb files in source? where and what changes?
Enter the command “ls -al *.conf” in your Linux_for_Tegra directory.
Do this on your host PC first. Share me what you saw.
I totally know what you want. Just follow the comment here first and I will tell you what to do next. OK?
hmecd001409@DSC:~/BSP/Jackson/temp_flash_dir/BSP_flashBinary/Linux_for_Tegra$ ls -al *.conf
lrwxrwxrwx 1 root root 30 Mar 19 20:44 clara-agx-xavier-devkit.conf → e3900-0000+p2888-0004-b00.conf
-rw-rw-rw- 1 root root 2175 Mar 19 20:44 e3900-0000+p2888-0004-b00.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 holoscan-devkit.conf → p3711-0000+p3701-0002.conf
lrwxrwxrwx 1 root root 30 Mar 19 20:44 igx-orin-devkit.conf → p3740-0002-c01+p3701-0008.conf
lrwxrwxrwx 1 root root 40 Mar 19 20:44 jetson-agx-orin-devkit-as-jao-32gb.conf → p3737-0000+p3701-0000-as-p3701-0004.conf
lrwxrwxrwx 1 root root 40 Mar 19 20:44 jetson-agx-orin-devkit-as-nano4gb.conf → p3737-0000+p3701-0000-as-p3767-0004.conf
lrwxrwxrwx 1 root root 40 Mar 19 20:44 jetson-agx-orin-devkit-as-nano8gb.conf → p3737-0000+p3701-0000-as-p3767-0003.conf
lrwxrwxrwx 1 root root 40 Mar 19 20:44 jetson-agx-orin-devkit-as-nx-16gb.conf → p3737-0000+p3701-0000-as-p3767-0000.conf
lrwxrwxrwx 1 root root 40 Mar 19 20:44 jetson-agx-orin-devkit-as-nx-8gb.conf → p3737-0000+p3701-0000-as-p3767-0001.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 jetson-agx-orin-devkit.conf → p3737-0000+p3701-0000.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 jetson-agx-orin-devkit-industrial.conf → p3737-0000+p3701-0000.conf
lrwxrwxrwx 1 root root 31 Mar 19 20:44 jetson-agx-orin-devkit-maxn.conf → p3737-0000+p3701-0000-maxn.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 jetson-agx-xavier-devkit.conf → p2822-0000+p2888-0004.conf
lrwxrwxrwx 1 root root 32 Mar 19 20:44 jetson-agx-xavier-ind-noecc.conf → p2822-0000+p2888-0008-noecc.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 jetson-agx-xavier-industrial.conf → p2822-0000+p2888-0008.conf
lrwxrwxrwx 1 root root 31 Mar 19 20:44 jetson-agx-xavier-industrial-mxn.conf → p2822-0000+p2888-0008-maxn.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 jetson-orin-nano-devkit.conf → p3768-0000+p3767-0000.conf
lrwxrwxrwx 1 root root 31 Mar 19 20:44 jetson-orin-nano-devkit-nvme.conf → p3768-0000+p3767-0000-nvme.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 jetson-xavier.conf → p2822-0000+p2888-0004.conf
lrwxrwxrwx 1 root root 27 Mar 19 20:44 jetson-xavier-maxn.conf → p2972-0000-devkit-maxn.conf
lrwxrwxrwx 1 root root 34 Mar 19 20:44 jetson-xavier-nx-devkit.conf → p3509-0000+p3668-0000-qspi-sd.conf
lrwxrwxrwx 1 root root 36 Mar 19 20:44 jetson-xavier-nx-devkit-emmc.conf → p3509-0000+p3668-0001-qspi-emmc.conf
lrwxrwxrwx 1 root root 31 Mar 19 20:44 jetson-xavier-nx-devkit-qspi.conf → p3509-0000+p3668-0000-qspi.conf
lrwxrwxrwx 1 root root 30 Mar 19 20:44 jetson-xavier-slvs-ec.conf → p2972-0000-devkit-slvs-ec.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 p2822-0000+p2888-0001.conf → p2822-0000+p2888-0004.conf
-rw-rw-rw- 1 root root 2238 Mar 19 20:44 p2822-0000+p2888-0004.conf
-rw-rw-rw- 1 root root 3556 Mar 19 20:44 p2822-0000+p2888-0008.conf
-rw-rw-rw- 1 root root 3522 Mar 19 20:44 p2822-0000+p2888-0008-maxn.conf
-rw-rw-rw- 1 root root 3132 Mar 19 20:44 p2822-0000+p2888-0008-noecc.conf
-rw-rw-rw- 1 root root 2214 Mar 19 20:44 p2972-0000-devkit-maxn.conf
-rw-rw-rw- 1 root root 2013 Mar 19 20:44 p2972-0000-devkit-slvs-ec.conf
lrwxrwxrwx 1 root root 26 Mar 19 20:44 p2972.conf → p2822-0000+p2888-0004.conf
lrwxrwxrwx 1 root root 34 Mar 19 20:44 p3449-0000+p3668-0000-qspi-sd.conf → p3509-0000+p3668-0000-qspi-sd.conf
lrwxrwxrwx 1 root root 36 Mar 19 20:44 p3449-0000+p3668-0001-qspi-emmc.conf → p3509-0000+p3668-0001-qspi-emmc.conf
-rw-rw-rw- 1 root root 1967 Mar 19 20:44 p3509-0000+p3668-0000-qspi.conf
-rw-rw-rw- 1 root root 2497 Mar 19 20:44 p3509-0000+p3668-0000-qspi-sd.conf
-rw-rw-rw- 1 root root 2450 Mar 19 20:44 p3509-0000+p3668-0001-qspi-emmc.conf
-rw-rw-rw- 1 root root 3548 Mar 19 20:44 p3509-a02+p3767-0000.conf
-rw-rw-rw- 1 root root 2148 Mar 19 20:44 p3509-a02+p3767-0000-maxn.conf
-rw-rw-rw- 1 root root 3713 Mar 19 20:44 p3711-0000+p3701-0002.conf
-rw-rw-rw- 1 root root 2305 Mar 19 20:44 p3737-0000+p3701-0000-as-p3701-0004.conf
-rw-rw-rw- 1 root root 2469 Mar 19 20:44 p3737-0000+p3701-0000-as-p3767-0000.conf
-rw-rw-rw- 1 root root 2463 Mar 19 20:44 p3737-0000+p3701-0000-as-p3767-0001.conf
-rw-rw-rw- 1 root root 2512 Mar 19 20:44 p3737-0000+p3701-0000-as-p3767-0003.conf
-rw-rw-rw- 1 root root 2508 Mar 19 20:44 p3737-0000+p3701-0000-as-p3767-0004.conf
-rw-rw-rw- 1 root root 3906 Mar 19 20:44 p3737-0000+p3701-0000.conf
-rw-rw-rw- 1 root root 2632 Mar 19 20:44 p3737-0000+p3701-0000-maxn.conf
-rw-rw-rw- 1 root root 4016 Mar 19 20:44 p3740-0002-b00+p3701-0002.conf
-rw-rw-rw- 1 root root 2171 Mar 19 20:44 p3740-0002-b01+p3701-0002.conf
-rw-rw-rw- 1 root root 2177 Mar 19 20:44 p3740-0002-c01+p3701-0008.conf
-rw-rw-rw- 1 root root 3741 Aug 28 18:01 p3768-0000+p3767-0000.conf
-rw-rw-rw- 1 root root 2093 Mar 19 20:44 p3768-0000+p3767-0000-maxn.conf
-rw-rw-rw- 1 root root 1620 Mar 19 20:44 p3768-0000+p3767-0000-nvme.conf
hmecd001409@DSC:~/BSP/Jackson/temp_flash_dir/BSP_flashBinary/Linux_for_Tegra$
Now do you see there is something called p3509-a02+p3767-0000.conf?
That is what I said here:
A change in DTB is a must-have…
As for the check for hardware, I don’t know you or your board. I cannot answer…
By default if you flash the board with p3509-xxx-p3767 board config, it will enable HDMI.
p3767-0000-p3768-0000 dtb is for Orin Nano devkit which only has DP port.
This is the board config that will enable HDMI.
jetson-orin-nano-devkit.conf: (the one I am using in my flash command)
fi
}
DEFAULT_EMC_FUSE=“0”;
PINMUX_CONFIG=“tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi”;
PMC_CONFIG=“tegra234-mb1-bct-padvoltage-p3767-dp-a03.dtsi”;
BPFDTB_FILE=“tegra234-bpmp-3767-0000-a02-3509-a02.dtb”;
DTB_FILE=“tegra234-p3767-0000-p3768-0000-a0.dtb”;
TBCDTB_FILE=“${DTB_FILE}”;
EMMC_CFG=“flash_t234_qspi_sd.xml”;
p3509-a02+p3767-0000.conf:
DEFAULT_EMC_FUSE=“0”;
PINMUX_CONFIG=“tegra234-mb1-bct-pinmux-p3767-hdmi-a03.dtsi”;
PMC_CONFIG=“tegra234-mb1-bct-padvoltage-p3767-hdmi-a03.dtsi”;
BPFDTB_FILE=“tegra234-bpmp-3767-0000-a02-3509-a02.dtb”;
DTB_FILE=“tegra234-p3767-0000-p3509-a02.dtb”;
TBCDTB_FILE=“${DTB_FILE}”;
EMMC_CFG=“flash_t234_qspi_sd.xml”;
So do I need to use Pinmux Jetson_Orin_NX_Series_+HDMI A03 and then replace it with original pinmux and then change the config file accordingly so that it uses the HDMI configs?
Yes, you have to modify the config file.
Actually it should be HDMI A04 but not A03. Make sure the pinmux spreadsheet is latest version.
OK, I am using 09-02-2023 1.01, should I use the latest available in Jetson download centre? and is it compatible with L4T 35.3.1? I guess its rev1.09 now
WayneWWW:
HDMI A04 but not A03
A03, A04 What these numbers indicate?
It is the board version we are using internally. Every custom board shall follow A04 pinmux.
So just ignore the A03 version.
Hi,
I have made the changes as discussed and flashed freshly, do not see any change in the display resolution :
nvidia@nvidia-desktop:~/Desktop$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 621mm x 341mm
1920x1080 60.00*+ 59.94 50.00
1680x1050 59.95
1440x900 59.89
1280x1024 75.02 60.02
1280x960 60.00
1280x800 59.81
1280x720 60.00 59.94 50.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
720x576 50.00
720x480 59.94
640x480 75.00 72.81 59.94 59.93
nvidia@nvidia-desktop:~/Desktop$
Do you suggest to check anything?
or am I missing something here? I will check my dtb file anyhow.