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

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,

  1. 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?
  2. do you create cfg for your board to flash?

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:

  1. 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 :

  2. I did not create my own cfg.

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.

Hi Wayne,

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.

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没有收到中断吗?

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

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

Could you also check the module as this link?

Hi Wayne,
今天我们的硬件工程师将设备带走测试了,稍晚点我会进行验证。
我想先确认你发的帖子里的另一件事,关于何时烧录0000或者0004 dtb版本。我看到开发者指南里关于执行lsusb时不同模组的ID作了描述:

每个模组使用哪个版本的dtb是否应该和这里的USB ID对应呢?
比如我的设备进入Force Recovery Mode后执行lsusb可以看到:

Bus 001 Device 009: ID 0955:7023 NVidia Corp.

那么使用flash脚本时使用的dtb就是0000版本,实际情况我确实烧录的是0000版本。
当使用0004版本时模组ID应为0955:7223,即Jetson AGX Orin (P3701-0004 with 32GB)

Hi YasirHu,

Could you try to use 32GB Orin module to develop and see if the issue is still?

Your product may use this kind too.

Hi Wayne,
我用R35.1原始BSP验证了,HDMI确实可以正常显示,但是HPD仍然不起作用。
我这里没有32GB Orin模组,暂时没办法进行验证。

Do you have xavier devkit to validate the patch on your current module? As my previous comment here.

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

I don’t have xavier devkit, sorry for that…

Hi YarisHu,

可以請你

  1. 檢查硬體
  2. 用我們的pinmux spreadsheet產生一個新的pinmux dtsi 檔案並且把board config裡面原本的pinmux路徑指到你產生的這個pinmux spreadsheet嗎?

根據我們在另外一條topic上與另一位用戶的驗證,

我們提供的dcb file + dts應該都沒有問題. 剩下的差異就只有你的硬體 還有pinmux了

另外, 如果你的module是 3701-500-0000, 代表你的pinmux跟kenrel dtb應該都會是3701-0000這一板, 不會有0004 或a04的檔名.


Could you please double confirm your hardware and generate the pinmux dtsi directly from the pinmux spreadsheet?

We just double confirmed the with another case from another customer. Their board can have both kinds of modules working with HDMI. Which means the dcb file and kernel patch should be correct.

BTW, if your module is 3701-500-0000, then the pinmux and kenrel dtb should be 3701-0000. The file name should not contain “0004” or “a04” keyword.