Custom board HDMI hotplug detect(HPD) did't work

WayneWWW · September 13, 2022, 9:17am

What is your method to flash the board after you add things to the device tree?

Have you checked if the runtime device tree really has the change you added?

YasirHu · September 13, 2022, 9:22am

After modify pinmux or devicetree, I run flash.sh like below:

sudo ./flash.sh -r jetson-agx-orin-devkit mmcblk0p1

I have checked the devicetree change by check if there is os_gpio_hotplug_a or not.
The pinmux and devicetree changes should really done.

WayneWWW · September 13, 2022, 9:23am

Hi,

Also want to clarify, is this issue only “HDMI hotplug failure” or even no hotplug case has problem (boot up with monitor connected)?

WayneWWW · September 13, 2022, 9:28am

Hi,

Please try with this dcb dtsi file. I just had internal check and it looks like the one from rel-34.1 does not support hotplug. Sorry about this.
tegra234-dcb-p3701-0000-a02-p3737-0000-a01-hdmi-4-ga5.0.2.dtsi (26.8 KB)

YasirHu · September 14, 2022, 1:40am

Hi WayneWWW:
I have tested the dtsi file you send, but HPD still not worked, neither R34.1.1 or R35.1 .

WayneWWW · September 14, 2022, 2:07am

請問你插拔hdmi的時候dmesg或uart log有沒有跳出類似這種log? 另外, 你沒有回覆我前面的問題. 請問你是hdmi完全不能用, 還是只是hotplug有問題？

Could you check if your dmesg or uart gives out below log when you hotplug the hdmi cable?
Also, you didn’t reply my previous question. Is your issue “HDMI totally not working” or just “hotplug fails to work”?

 804.323624] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[  804.333736] ---[ end trace d40210c2e73c52c0 ]---
[  804.919793] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[  804.929432] ---[ end trace d40210c2e73c52c1 ]---
[  805.119763] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[  805.129374] ---[ end trace d40210c2e73c52c2 ]---
[  805.134173] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[  805.143714] ---[ end trace d40210c2e73c52c3 ]---
[  805.148491] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[  805.158017] ---[ end trace d40210c2e73c52c4 ]---

YasirHu · September 14, 2022, 2:19am

Hi WayneWWW:
My HDMI could display, just hotplug fails to work.
HDMI pins linked to MAX96751 directly on my PCB. So there is not a cable in fact. I just pull down or pull up the GPIO TEGRA234_MAIN_GPIO(M, 0). This works fine when I use orin devkit with a DP to HDMI cable, but not with my custom board which use really HDMI output.
When I pull down or pull up TEGRA234_MAIN_GPIO(M, 0), did not see the log you send.

WayneWWW · September 14, 2022, 3:33am

Hi,

請問你的"pull down or pull up the GPIO" 是指說從pin腳上控制還是你從軟體控制？
可以分享一下你如何判斷 device tree跟pinmux有沒有被正確燒進去？可以試試把/proc/device-tree dump出來檢查到底有沒有對應的patch被加入

dtc -O dts -o dump.dts -I fs /proc/device-tree

請問你目前從/sys/kernel/debug/gpio 上有沒有看到 gpio M,0 後面有顯示 “os_gpio_hotplug_a” 或是類似的名稱 (hpd)?

Does your “pull down or pull up the GPIO” mean “control from the pin hardware” or do you control from the software?
Can you share how you tell if the device tree and pinmux are being flashed correctly? You could dump the /proc/device-tree and check if the patch is really applied.
Could you see gpio M,0 from /sys/kernel/debug/gpio, with “os_gpio_hotplug_a” or a similar name (hpd) as usecase?

YasirHu · September 14, 2022, 5:27am

Hi

control from the pin hardware, I have confirmed it using oscilloscope.
Generally I would run cd to some directory at /proc/device-tree like display@13800000, then run ls to check what I change in device tree is flashed or not.
I have dump the /proc/device-tree and saw the os_gpio_hotplug_a I add.
dump.dts (420.4 KB)
There is no os_gpio_hotplug_a or similar name at GPIO M,0

root@tegra-ubuntu:/home/# cat /sys/kernel/debug/gpio |grep PM
 gpio-424 (PM.00               )
 gpio-425 (PM.01               )
 gpio-426 (PM.02               )
 gpio-427 (PM.03               )
 gpio-428 (PM.04               )
 gpio-429 (PM.05               )
 gpio-430 (PM.06               )
 gpio-431 (PM.07               )

WayneWWW · September 14, 2022, 5:34am

Could you check if “tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi” and “tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi” got flashed to your board? The flash log shall tell.

YasirHu · September 14, 2022, 6:05am

I have checked the flash log, but I found the dtsi files of pinmux and gpio that I flashed is tegra234-mb1-bct-pinmux-p3701-0000.dtsi and tegra234-mb1-bct-gpioint-p3701-0000.dts.
flash-log (78.6 KB)

The gpio dtsi file output from pinmux spreadsheet is renamed to tegra234-mb1-bct-gpio-p3701-0000.dtsi which is included in both tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi and tegra234-mb1-bct-pinmux-p3701-0000.dtsi. And those two pinmux dtsi files’ content are same, both from a dtsi file output by pinmux spreadsheet, I just rename it twice.
I also change EQOS settings in pinmux, and now RGMII works fine, so the pinmux should flash correctly.

YasirHu · September 19, 2022, 9:18am

@WayneWWW 我检查了flash脚本输出的日志，里面显示我烧写的pinmux配置和gpio配置是 tegra234-mb1-bct-pinmux-p3701-0000.dtsi和 tegra234-mb1-bct-gpioint-p3701-0000.dts .并没有烧写你提到的“tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi”
flash-log (78.6 KB)

pinmux表格输出的文件gpio配置文件被我重新名为 tegra234-mb1-bct-gpio-p3701-0000.dtsi。pingmux表格输出的pinmux配置文件被我重命名为 tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi 和 tegra234-mb1-bct-pinmux-p3701-0000.dtsi ，这两个文件内部都包含了tegra234-mb1-bct-gpio-p3701-0000.dtsi。
tegra234-mb1-bct-gpio-p3701-0000.dtsi (3.9 KB)
tegra234-mb1-bct-pinmux-p3701-0000.dtsi (64.6 KB)
tegra234-mb1-bct-pinmux-p3701-0000.dtsi (64.6 KB)
我在pinmux配置中还设置了EQOS相关的引脚用于使能RGMII连接switch器件，目前RGMII工作正常，因此我认为pinmux表格生成的bct配置文件已经成功烧写了。

Jeffli · September 21, 2022, 2:49am

Hi YasirHu,
tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi is one of default dts in BCT, just as Wayne mentioned ,do you edit this file according to #7 comment? why you rename 0000.dtsi to a04.dts, they are two dts files

Jeffli · September 21, 2022, 4:06am

Hi YasirHu,
from flash log, a04 is not flashed ,so omit a04.dts. tegra234-mb1-bct-pinmux-p3701-0000.dtsi to flash should be also ok,

but from tegra234-mb1-bct-pinmux-p3701-0000.dtsi , seems gpio file include is still default Orin-jetson_agx_orin-gpio-default.dtsi, not update to pinmux gpio, could you double-check?

image1603×527 19.1 KB
do you create cfg for your board to flash?

YasirHu · September 21, 2022, 5:17am

Hi Jeffli,
I have checked my tegra234-mb1-bct-pinmux-p3701-0000.dtsi, it is the same as Wayne mentioned at #7 comment.
For your another two questions:

Sorry for the wrong attach file I upload before, it is output from pinmux spreadsheet original. In fact I have edited tegra234-mb1-bct-pinmux-p3701-0000.dtsi for adapting gpio dtsi file, like this :

Screenshot from 2022-09-21 13-14-281207×889 116 KB
I did not create my own cfg.

WayneWWW · September 21, 2022, 6:53am

Hi,

Could you share your

cat /etc/nv_boot_control.conf"

from your device so that we can know the exact kind of module you are using?

We have different kind of Orin module in market and different module is using different pinmux file. We want to prevent the mismatch case first.

YasirHu · September 21, 2022, 6:59am

Hi Wayne,

WayneWWW · September 22, 2022, 4:24am

Hi @YasirHu

昨天剛好有另外一組用戶驗證完我們的patch.

在這邊提醒幾點. 我們有發現每個客人/用戶燒錄的kernel dtb還有pinmux dtsi似乎都不太一樣. 有些人kernel 用0004版本, pinmux 用0000版本. 有些pinmux是使用a04版本, kernel反而用0000版本

所以請確認一下flash log. 你patch過的dtb/ dtsi確實都是你燒進去的那份

另外, 如果你有AGX Xavier devkit底板. 你也可以用它測試. 我們先前有在這塊底板測試過Orin HDMI.

We just had another customer validated the patches yesterday.

And some points to remind here. We notice there are multiple of combinations got flashed to the board.

For example, some user is using a04 kernel dtb and a04 pinmux. But in your case, both of pinmux and kernel dtb got flahsed to your board are both “0000” files.

Thus, please make sure you really patched to the correct file. But not directly flashing without check.

Also, if you have Xavier AGX devkit, you can put the module on it and test too. We’ve validated that before.

YasirHu · September 23, 2022, 1:01am

Hi Wayne,
我看了我的flash脚本运行日志，确认我烧录的pinmux dtsi文件为tegra234-mb1-bct-pinmux-p3701-0000.dtsi

hys@hys-Latitude-3400:~/work/orin$ cat flashlog |grep pinmux
copying pinmux_config(/home/hys/nvidia/R35.1/Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000.dtsi)... done.
./tegraflash.py  --bl uefi_jetson_with_dtb.bin  --odmdata gbe-uphy-config-22,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-0,gbe0-enable-10g  --overlay_dtb L4TConfiguration.dtbo,tegra234-p3737-overlay-pcie.dtbo,tegra234-p3737-audio-codec-rt5658-40pin.dtbo,tegra234-p3737-a03-overlay.dtbo,tegra234-p3737-a04-overlay.dtbo,L4TRootfsInfo.dtbo,tegra234-p3737-camera-dual-imx274-overlay.dtbo,tegra234-p3737-camera-e3331-overlay.dtbo,tegra234-p3737-camera-e3333-overlay.dtbo,tegra234-p3737-camera-imx185-overlay.dtbo,tegra234-p3737-camera-imx390-overlay.dtbo  --bldtb tegra234-p3701-0000-p3737-0000.dtb --applet mb1_t234_prod.bin --cmd "flash; reboot"  --cfg flash.xml --chip 0x23 --concat_cpubl_bldtb --cpubl uefi_jetson.bin --device_config tegra234-mb1-bct-device-p3701-0000.dts --misc_config tegra234-mb1-bct-misc-p3701-0000.dts --pinmux_config tegra234-mb1-bct-pinmux-p3701-0000.dtsi --gpioint_config tegra234-mb1-bct-gpioint-p3701-0000.dts --pmic_config tegra234-mb1-bct-pmic-p3701-0000.dts --pmc_config tegra234-mb1-bct-padvoltage-p3701-0000.dtsi --deviceprod_config tegra234-mb1-bct-cprod-p3701-0000.dts --prod_config tegra234-mb1-bct-prod-p3701-0000.dts --scr_config tegra234-mb2-bct-scr-p3701-0000.dts --wb0sdram_config tegra234-p3701-0000-p3737-0000-TE990M-wb0sdram.dts --br_cmd_config tegra234-mb1-bct-reset-p3701-0000.dts --dev_params tegra234-br-bct-p3701-0000.dts,tegra234-br-bct_b-p3701-0000.dts --mb2bct_cfg tegra234-mb2-bct-misc-p3701-0000.dts  --bins "psc_fw pscfw_t234_prod.bin; mts_mce mce_flash_o10_cr_prod.bin; mb2_applet applet_t234.bin; mb2_bootloader mb2_t234.bin; xusb_fw xusb_t234_prod.bin; dce_fw display-t234-dce.bin; nvdec nvdec_t234_prod.fw; bpmp_fw bpmp_t234-TE990M-A1_prod.bin; bpmp_fw_dtb tegra234-bpmp-3701-0000-3737-0000.dtb; sce_fw camera-rtcpu-sce.img; rce_fw camera-rtcpu-t234-rce.img; ape_fw adsp-fw.bin; spe_fw spe_t234.bin; tos tos-optee_t234.img; eks eks.img"  --sdram_config tegra234-p3701-0000-p3737-0000-TE990M-sdram.dts  --cust_info custinfo_out.bin  --secondary_gpt_backup  --bct_backup  --boot_chain A 
[   2.7697 ] Pre-processing config: tegra234-mb1-bct-pinmux-p3701-0000.dtsi
[   3.3830 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --wb0sdram tegra234-p3701-0000-p3737-0000-TE990M-wb0sdram_cpp.dtb --pinmux tegra234-mb1-bct-pinmux-p3701-0000_cpp.dtb --pmc tegra234-mb1-bct-padvoltage-p3701-0000_cpp.dtb --pmic tegra234-mb1-bct-pmic-p3701-0000_cpp.dtb --brcommand tegra234-mb1-bct-reset-p3701-0000_cpp.dtb --prod tegra234-mb1-bct-prod-p3701-0000_cpp.dtb --gpioint tegra234-mb1-bct-gpioint-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb --deviceprod tegra234-mb1-bct-cprod-p3701-0000_cpp.dtb
[   3.3847 ] Parsing config file :tegra234-mb1-bct-pinmux-p3701-0000_cpp.dtb 
[   3.4007 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --wb0sdram tegra234-p3701-0000-p3737-0000-TE990M-wb0sdram_cpp.dtb --pinmux tegra234-mb1-bct-pinmux-p3701-0000_cpp.dtb --pmc tegra234-mb1-bct-padvoltage-p3701-0000_cpp.dtb --pmic tegra234-mb1-bct-pmic-p3701-0000_cpp.dtb --brcommand tegra234-mb1-bct-reset-p3701-0000_cpp.dtb --prod tegra234-mb1-bct-prod-p3701-0000_cpp.dtb --gpioint tegra234-mb1-bct-gpioint-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb --deviceprod tegra234-mb1-bct-cprod-p3701-0000_cpp.dtb
[   3.4026 ] Parsing config file :tegra234-mb1-bct-pinmux-p3701-0000_cpp.dtb

在pinmux dtsi文件中也include我生成的gpio dtsi

看完你发的帖子之后我有个疑问，就是我拉高/拉低HPD引脚的时候并没有出现帖子中的warning log

这说明我的HPD没有收到中断吗？

WayneWWW · September 23, 2022, 1:18am

这说明我的HPD没有收到中断吗？

Unfortunately, I think it means yes. No interrupt got asserted.