I did by using same command as him, ./flash.sh on devkit then i switch the module on custom board.
So the whole process is to rebuild kernel when the source files are modified, then always reflash manually to be sure that modification are made.
Please do not flash like that. That one is not correct because “-r” will re-use the previous system image. Which means something are not updated…
You should remove the -r. It will take more time but it will ensure everything in system image is new (kernel and dtb are from system image).
My mistake, i never added the -r option, just didnt see it when reading the topic
Also
By quicky passing through the topic you just shared there is one thing i did not do and its changing the function of GPIO pin
This was not mentionned anywhere else on the topics ive read.
This is actually just in the first post of the link you shared.
I admit. I completly missed it.
I did the modification and am currently reflashing my board.
1 Like
Hi!
So I verified that the pinmux and device tree were correctly modified and flashed by checking the flash log. Also i verified that the dcb_blob was the same as the one you shared.
Here is the flash log :
flash.log (488.3 KB)
With the important part being :
[ 0.8078 ] Kernel DTB used: kernel_tegra234-p3701-0000-p3737-0000.dtb
[ 0.8514 ] Pre-processing config: tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
I applied the hotplug patch by adding to device tree node display@13800000 :
os_gpio_hotplug_a = <&tegra_main_gpio TEGRA234_MAIN_GPIO(M, 0) GPIO_ACTIVE_HIGH>;
I applied to the aformentionned files those modifications :
Finally, once i checked everything, i reflashed the jetson on the devkit and switched back to my custom board to test the hdmi. I tried removing hdmi cable then powering the jetson and then replug the hdmi → nothing appears. Then i tried plugging the hdmi before opening the jetson → nothing. I do get this message when plugging hdmi:
Sorry if i make you repeat!
I’m getting used to the nvidia jetson configuration system now but im still a newbie.
So what should i do next?
Loic
Hi Loic,
Could you share the board schematic of the HDMI part for review?
Hi!
Here are the schematics, we physically swap the Lane 0 and 2 of HDMI to respect design guide by removing resistances and soldering cables.
Hi,
Yea, I found it like 2 days ago and it seems pretty similar to my use case like you say! Thing is with them it was the aux line which were swapped. I double checked my case and it is correctly connected ( the dp_aux_ch2_p is connected to the Clock signal from connector, meanwhile the dp_aux_ch2_N is connected to Data).
So i guess it’s back to checking hardware.
Tho, one thing i realised is that my GPIO state is always “hi” even when I unplugged the HDMI. I used this command to read gpio PM.00 state: cat /sys/kernel/debug/gpio | grep PM.00. Is it normal?
Thank you!
Loic
Sorry that actually I spent most of time on another post as this
This user’s case is similar as yours. And turns out his hardware design has problem. Thus, I am confident that the software should work if pinmux, dcb and dts are correct.
Please go through the post and if they are all ready, go back to review your hardware.
Hi!
So we revised our hardware and realise the GPIO07 was causing the problem, it stopped the 5V to reach the i2c lines which made it not work. So we enabled the tri-state for the gpio07 pin and now we can see the boot display! Yay!
However, we get a new error after booting :
gaus@tegra-ubuntu:~$ [ 22.802321] nvidia-modeset: ERROR: GPU:0: The requested.
[ 22.819142] nvidia-modeset: ERROR: GPU:0: The requested configuration of dis.
[ 24.392869] nvidia-modeset: ERROR: GPU:0: The requested configuration of dis.
[ 24.409964] nvidia-modeset: ERROR: GPU:0: The requested configuration of dis.
Here is the Xorg.0.log :
Xorg.0.log (9.0 KB)
This screen I’m using has a VGA-HDMI adaptor. So I decided to also try it on another display, the error looks the same.
Here is he Xorg.0.log attached to the screen.
Xorg.0.log (8.9 KB)
Glad we passed through the hard part!
Loict
Is that “another display” a native HDMI or still VGA-HDMI adapter?
native HDMI, sorry for not being clear
Could it be because of the debug_uefi.bin im using instead of normal uefi?
I don’t think that is related to debug UEFI.
But you could try to use default one first.
Please share full dmesg. Xorg log is not sufficient to debug now.
Just did, it did not change anything.
Here is the full dmesg and boot log.
Your log seems got truncated in each line if the length is too long… Please resize your terminal size…
What is the exact DCB image you give to the device tree? I think the setting is not correct.
Oh yea sorry! 1 sec, here.
dmesg.txt (69.1 KB),
when talking about the dcb, do you want the file with all the hexa blob?
if so here it is
display_test.dtsi (26.2 KB)
(i copy paste it inside kernel sources and point to it by using include statement instead of previous dcb)
else i can give you the output of the dcb_tool:
########## Tegra DCB BLOB ###############
########### Display Devices #############
Display Devices::
Display Devices : [0]
Type : [TMDS]
CCB : [0]
Heads : 0:[Y] 1:[Y]
Sor : [0 ]
HDMI capable : [1]
Connector : [0]
Bus : [0]
Display Devices : [1]
Type : [TMDS]
CCB : [0]
Heads : 0:[Y] 1:[Y]
Sor : [0 ]
HDMI capable : [1]
Connector : [0]
Bus : [0]
############### CCB Entries ###############
CCB::
*CCB entries that have both I2C and AUX ports unused (value = 31) are not displayed
CCB Index : 0
I2C Port : [6]
AUX Port : [0]
########### Connector entries #############
Connectors::
Connector Index : 0x0
Type : [HDMI]
Hotplug : A:[Y]
Connector Index : 0x0
Type : [HDMI]
Hotplug : A:[Y]
Update here:
I just realised when i was copying the newly builded kernel files, it did not copy at the right place. So i fixed it and reflashed the jetson with the right dcb and hotplug. But it did not fix our problem, we have the same problem as before and it does not show the booting display anymore…
dmesg.log (66.9 KB)
Xorg.0.log (9.3 KB)
Only difference is when i remove HDMI i get this warning continuously :
[ 49.108154] ---[ end trace 5f22c25d91248375 ]---
[ 49.112932] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.122500] ---[ end trace 5f22c25d91248376 ]---
[ 49.127278] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.136848] ---[ end trace 5f22c25d91248377 ]---
[ 49.141626] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.151189] ---[ end trace 5f22c25d91248378 ]---
[ 49.155967] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.165536] ---[ end trace 5f22c25d91248379 ]---
[ 49.170313] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.179886] ---[ end trace 5f22c25d9124837a ]---
[ 49.184665] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.194234] ---[ end trace 5f22c25d9124837b ]---
[ 49.199011] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.208576] ---[ end trace 5f22c25d9124837c ]---
[ 49.213352] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.222911] ---[ end trace 5f22c25d9124837d ]---
[ 49.227689] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.237262] ---[ end trace 5f22c25d9124837e ]---
[ 49.242040] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.251612] ---[ end trace 5f22c25d9124837f ]---
[ 49.256392] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.265956] ---[ end trace 5f22c25d91248380 ]---
[ 49.270735] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.280295] ---[ end trace 5f22c25d91248381 ]---
[ 49.285074] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.294643] ---[ end trace 5f22c25d91248382 ]---
[ 49.299423] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.308998] ---[ end trace 5f22c25d91248383 ]---
[ 49.313785] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.323343] ---[ end trace 5f22c25d91248384 ]---
[ 49.328120] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.337690] ---[ end trace 5f22c25d91248385 ]---
[ 49.342470] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.352035] ---[ end trace 5f22c25d91248386 ]---
[ 49.356811] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 49.366380] ---[ end trace 5f22c25d91248387 ]---
[ 49.371166] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
Just to be clear, this is the dtb entry i use :
display@13800000 {
os_gpio_hotplug_a = <&tegra_main_gpio TEGRA234_MAIN_GPIO(M, 0) GPIO_ACTIVE_LOW>;
status = "okay";
};
since our hardware is similar to jetson xavier agx devkit.
Your dcb image is still wrong.
Your xorg log shows you have 2 display heads on Orin. But it is not possible because Orin only supports one head…
DCB shall match to this user’s case…
Well using the dcb image from 34.1 release, it worked perfectly!! I now have a working HDMI display. Thank you alot for your patience and help!
Loic