Pca954x probe failed on Jetson AGX Orin

Hello,
I have just faced with a problem working with a Jetson AGX Orin Developer Kit, P3737 carrier borad, LI-JAG-ADP-GMSL2-8CH GMSL2 board and ar0234 sensors. Jetpack version is 36.3, built from sources with no changes. tegra234-p3737-camera-dual-hawk-ar0234-e3653-overlay.dts is selected as a DTS overlay. I have this logs during the boot process:

[    4.148089] serial-tegra 3100000.serial: TX in PIO mode
[    4.148147] 3100000.serial: ttyTHS1 at MMIO 0x3100000 (irq = 112, base_baud = 0) is a TEGRA_UART
[    4.148630] serial-tegra 3110000.serial: RX in PIO mode
[    4.148634] serial-tegra 3110000.serial: TX in PIO mode
[    4.148669] 3110000.serial: ttyTHS2 at MMIO 0x3110000 (irq = 207, base_baud = 0) is a TEGRA_UART
[    4.150970] tegra_rtc c2a0000.rtc: registered as rtc1
[    4.150980] tegra_rtc c2a0000.rtc: Tegra internal Real Time Clock
[    4.151430] tegra-i2c 3160000.i2c: Adding to iommu group 1
[    4.156861] tegra-i2c 3180000.i2c: Adding to iommu group 1
[    4.166582] pca954x 2-0070: probe failed
[    4.167514] tegra-i2c 3190000.i2c: Adding to iommu group 1
[    4.173590] tegra-i2c 31b0000.i2c: Adding to iommu group 1
[    4.181390] tegra-i2c 31c0000.i2c: Adding to iommu group 1
[    4.186189] tegra-i2c 31e0000.i2c: Adding to iommu group 1
[    4.192651] tegra-i2c c240000.i2c: Adding to iommu group 1
[    4.199606] tegra-i2c c250000.i2c: Adding to iommu group 1
[    4.236639] cpufreq: cpufreq_online: CPU4: Running at unlisted initial frequency: 2009000 KHz, changing to: 2035200 KHz
[    4.240695] cpufreq: cpufreq_online: CPU8: Running at unlisted initial frequency: 2008000 KHz, changing to: 2035200 KHz
[    4.243907] sdhci-tegra 3460000.mmc: Adding to iommu group 2
[    4.244968] sdhci-tegra 3400000.mmc: Adding to iommu group 3

Seems like something went wrong with PCA954x i2c multiplexer initialization and it might be a reason why I can not see any signs of max96712 and ar0234 modules probes.
Can anybody helps me with that, are there any reasons why pca954x probe can fails?

@SimonZhu
May I have your comment for the driver device tree for the “LI-JAG-ADP-GMSL2-8CH GMSL2” for r36.3 release.

Thanks

Hello,
So, now I use tegra234-p3737-camera-dual-hawk-ar0234-e3653-overlay.dtsand all other out-of-shelf DTSs from the Jetpack with no modifications. From my perspective it should at least initializes pca954x and try to probe max96712 driver. Please correct me if I am wrong.

Suppose yes,
Could you check the pca954x by i2cdetect utility.

Sure,
Here is i2cdetect -l output:


If I got it right, according to the tegra234-p3737-camera-dual-hawk-ar0234-e3653-overlay.dts pca954x should be present on the i2c-2 (3180000.i2c) bus so here is sudo i2cdetect -y -r 2 output:
image
Seems like there is no a pca954x here or I did something wrong.

Right, looks like can’t detect the pca954x.
Maybe confirm with vendor for the HW design.

But it’s original Nvidia Jetson AGX Orin Developer Kit with no hardware changes.

I mean the camera board.

But shouldn’t pca954x be installed on a Jetson AGX Orin board?

I checked LI-JAG-ADP-GMSL2-8CH GMSL2 board and AGX Orin Carrier Board schematics and there is no pca954x there, so my only guess that it is placed on the main Jetson board. Unfortunately I couldn’t find schematics for it.

It should on the camera board.
If LI-JAG-ADP-GMSL2-8CH GMSL2 board don’t have it suppose the dts shouldn’t for this board.

There is no pca954x on both LI-JAG-ADP-GMSL2-8CH GMSL2 board and Orin dev kit. So it should not detect the pca954x.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.