We have a custom carrier board for Jetson AGX Xavier Industrial Module.
There is only a Display Port connected to the module on HDMI_DP2 port.
In device-tree file:
sor, sor1, sor3, display@15200000, display@15210000 and display@15230000, sor-2/hdmi-display nodes are disabled.
sor2 and sor2/dp-display nodes are enabled and sor2 active,panel is choosen as 0x45e which is phande value of sor2/dp-display node.
Thank you for the information. it was mapped to sor1. I have changed device-tree and now the behaviour is changed. There are new meesages related to the display at the opening as given below. But still, the monitor is not recognized.
Is there anything else that can be done?
I have compared the edited device-tree with the devkit’s device tree, I couldn’t see difference. In order to be sure and to try other alternatives, I have flashed the board with JETPACK 4.6.4 and edited the device-tree for DP output. All of the settings are as devkit’s DP settings except the following properties which are commented. (There is not any SWITCH on our custom carrier board.)
However there is not any display output on the monitor. Following messages are about display which appears at the startup…
$ sudo dmesg | grep display
[ 0.872002] iommu: Adding device 15210000.nvdisplay to group 46
[ 0.876681] platform 15210000.nvdisplay: IOVA linear map 0x00000000c6000000(2a000000)
[ 0.876765] t19x-arm-smmu: Adding 15210000.nvdisplay to ISO SMMU client
[ 1.706707] Could not get extcon-dev /host1x/nvdisplay@15210000:typec1(1)
[ 3.608346] Could not get extcon-dev /host1x/nvdisplay@15210000:typec1(1)
[ 3.760128] Could not get extcon-dev /host1x/nvdisplay@15210000:typec1(1)
[ 3.773697] Could not get extcon-dev /host1x/nvdisplay@15210000:typec1(1)
[ 4.736377] Could not get extcon-dev /host1x/nvdisplay@15210000:typec1(1)
[ 5.983891] Could not get extcon-dev /host1x/nvdisplay@15210000:typec1(1)
[ 5.998256] Could not get extcon-dev /host1x/nvdisplay@15210000:typec1(1)
I was editing the dtb file located in /boot/dtb folder on the board. I have recognized that changes are not being implemented in JETPACK 4.6.4. version. (It was being effective in JETPACK 5.1.2)
I have flashed the whole board and the behaviour is changed. Following messages are about display which appears at the startup…
tegra-ubuntu:~$ sudo dmesg | grep display
[ 0.890612] iommu: Adding device 15210000.nvdisplay to group 46
[ 0.894816] platform 15210000.nvdisplay: IOVA linear map 0x00000000c6000000(2a000000)
[ 0.894910] t19x-arm-smmu: Adding 15210000.nvdisplay to ISO SMMU client
[ 1.803851] tegradc 15210000.nvdisplay: disp0 connected to head1->/host1x/sor2
[ 1.803914] tegradc 15210000.nvdisplay: parse_dp_settings: No dp-lt-settings node
[ 1.804086] tegradc 15210000.nvdisplay: DT parsed successfully
[ 1.804133] tegradc 15210000.nvdisplay: Display dc. (ptrval) registered with id=0
[ 1.809922] tegradc 15210000.nvdisplay: vblank syncpt # 8 for dc 1
[ 1.809936] tegradc 15210000.nvdisplay: vpulse3 syncpt # 9 for dc 1
[ 1.826180] tegradc 15210000.nvdisplay: probed
[ 1.826780] tegradc 15210000.nvdisplay: fb registered
[ 1.830354] tegradc 15210000.nvdisplay: blank - powerdown
[ 37.640754] tegradc 15210000.nvdisplay: blank - powerdown
There is no new log on dmesg output when I hotplug the cable.
From several questions asked in forum about display issue, I am suspecting from HPD pin but not sure. According to general Display Port definitions it seems that HPD pin is an active-high signal. Is it also active-high in jetpack?
Is there a way to disable HPD detection and to drive a default video output from DP port?
Also in several questions about this issue, some dtsi files(for example tegra194-p2822-disp.dtsi) and source files(.c) talked about to being changed. However I couldn’t find those files in my JETPACK folder. Where I have to look for the source files?
(Note: PINMUX setting of HPD signal is set as DP_AUX_CH2_HPD.)
If you saw nothing from the dmesg after you hotplug the cable, then I think it is related to pinmux. Your pinmux is still GPIO but not SFIO. Make sure your cfg file does not have that pin set in gpio section.
It is most likely the case because SOR2 was by default using as GPIO for HDMI on devkit.
By the way, I have replaced the following cfg file, is it the correct one?
As I remember, previously I have downloaded some versions from that website. I have downloaded the latest version again Driver Package (BSP)
This is a compressed file in which there are files as same as my current JETPACK folder. So where is the *.c files in this compressed file system? I want to make some changes in source code and to see it’s effect on the startup log.
I have checked the devkit schematics and saw that HDMI_DP2 port is used as HDMI and sor2 is used for this output in the device-tree. We are also using HDMI_DP2 port as DP in our cusotm carrier board. Hence I have choosen sor2 as DP output. We have to choose sor2 as DP output, isn’t it?
I have checked the cfg file from flash log and replaced the correct file which was tegra19x-mb1-pinmux-p2888-0008-b01-p2822-0000-jaxi.cfg.
However flashing halt at a stage where last message from the board terminal was as following.
[0265.144] I> TBoot-CPU Recovery hang
Full log output is as following. flash_error__20231122__1132.txt (11.6 KB)
What can cause to the halt of the flash process?
As a second try, I have changed only pinmux.0x02440040 settings from the original CFG file and it has been successfully flashed to the board. And there are 0x450 value at the address 0x02440040 now.
Also there is display output at the DP port.