Hi,
We have a custom made carrier board for Jetson Xavier NX. We are facing issue with HDMI. It says it is connected but we are not able to see the output when connected to the display. Kindly help on this.
Please find the below attached Uart logs.
[0003.788] I> qspi flash-0 params source = boot args
[0003.792] W> No board IDs available
[0003.795] E> Failed to get board id info!
[0003.801] I> sdmmc-3 params source = safe params
[0003.808] I> Found 41 partitions in QSPI_FLASH (instance 0)
[0003.809] W> Cannot find any partition table for 00000003
[0003.814] E> Failed to publish 00000003
[0003.823] I> Found 22 partitions in SDMMC_USER (instance 3)
[0003.839] I> regulator ‘vdd-hdmi-5v0’ already enabled
[0003.845] I> regulator ‘vdd-hdmi-5v0’ already enabled
[0003.845] I> hdmi cable connected
[0003.850] W> set volts not configured for ‘vdd-1v0’
[0003.854] W> set volts not configured for ‘vdd-1v8-hs’
[0003.854] I> retrieved tmds range from prod_list_hdmi_soc
[0003.856] E> cannot find any other nvdisp nodes
[0003.872] I> edid read success
[0003.884] I> edid read success
Are you asking boot logo or even the later desktop GUI?
Hi @WayneWWW ,
Not able to View any thing on the monitor not even the logo.
Then you should proceed sharing the full log but not just these few lines…
Try to attach it as a file unless you want other people keep scrolling the mouse…
uart_bootup_logs.txt (12.3 KB)
Are you sure this is full log? Your device is not even booting up. Not just a HDMI issue.
Yes, that’s the full log file attached.
We are trying to understand what exactly is happening. We need your help here.
What’s your opinion by checking on the logs, do you see any problem here? we want to understand.
Hi,
There is no opinion right now because I don’t know you or your board.
You should reply these questions first
-
Is this a custom board or NV devkit? I guess it is custom board.
-
Do you make this board or it is from some other board vendors?
- Its a custom board developed by us using Jetson Xavier NX Carrier Board reference design.
- we have designed this board, fabricated outside.
we have completed the bring up of the board and power supply sections are completely working fine.
For your reference, we had a discussion about this topic earlier.
Please enable the UEFI log by rebuilding the debug uefi from this github and dump the log again.
We have just checked by connecting SOM(already flashed with Jetpack 5.1.2) to nvidia development kit and observed that we can get video output on monitor. we also observed different boot up logs in this.
Also thinking like did we miss any initial configuration ??
Do we still need to enable UEFI??
If your module can work on devkit but failed on your board, then what do you think could be problem? Obviously your board has some hardware problem or mismatch.
Do you want to rework hardware without any clue or you want to follow the suggestion to enable UEFI log and see what got stuck?
We observed that UEFI is already flashed in the SOM by looking at:
L4TConfiguration.txt (974 Bytes)
Attached is the logs from nvidia development board (just for checking uefi):
carrierBoardLogs.txt (69.1 KB)
We found that HDMI lanes 0 and 2 are interchanged in our Hardware. Where can we correct it in the device tree?
there should be something like “xbar” keyword in device tree. Swapping the 0 and 2 in the array and it shall match your hardware.
Hi,
Having trouble in finding the right file.
-
The extlinux.conf file in the path /home/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs/boot/extlinux (from sdk manager) → has FDT /boot/dtb/kernel_tegra194-p3668-0001-p3509-0000.dtb extlinux.txt (851 Bytes)
-
Again there is tegra194-p3668-0001-p3509-0000.dtb file in /home/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/kernel/dtb path.
You are actually talking about same file.
A thing on host PC won’t take effect to your device unless you flash the board.
And extlinux.conf file will be updated during the flash process.
From this i understood tegra194-p3668-0001-p3509-0000.dtb is the right file.
But cannot find this keyword for HDMI in this file. I am referring HDMI is not working - #31 by WayneWWW
By the way i am using FDT viewer for reading DTB. Is there any better alternative that you use?
Hi @WayneWWW
we have an update.
we tried dtc -I dtb -O dts -o original.dts original.dtb → it created .dts file and now we can edit in text editor.
Looks like by default its in <2 1 0 3 4> order. Wondering what it means??
change it to 0 1 2 34 and it will match your hardware design where 0 and 2 are reversed.