About pps in

[liu.jialu]

We use GPIO(pin:B8, GPIO3_PS.05) as pps input capture on orin, but it can’t work.

PPS sch like this:

the yellow signal is PPS_IN and blue signal is GPIO_CODEC_INT

In ORIN Linux, run

ppstest /dev/pps0

report error like this:

and device tree config like this:

pps {
compatible = “pps-gpio”;
// pin:B8 (GPIO3_PS.05)
gpios = <&tegra_main_gpio TEGRA194_MAIN_GPIO(S, 5) 0>;
};

the same custom board with AGX_XAVIER module, PPS_IN works well with ppstest in Linux, but with AGX_ORIN, it can’t capture the pps signal. then what’s the difference about the GPIO pin with xavier and orin module?

[liu.jialu]

according to the topic: Using pps-gpio on Orin

there’s an issue that pps fetch will timeout.
we’re still checking this internally.

then what’s the internally checking result?

[kayccc]

Sorry for the late response, have you managed to get issue resolved or still need the support? Thanks

[liu.jialu]

like topic About ORIN gpio value after rising edge said:
GPIO3_PAC.05 on Orin, but it’s GPIO3_PS.05 on Xavier.
on Orin we use the GPIO3_PAC.05 (B8, GPIO11).
xavier works well, but orin can’t capture the GPIO edge in time.

[JerryChang]

hello liu.jialu,

so, this Topic 241503 is duplicated issue, right?
please also share the Orin device tree config for using GPIO3_PAC.05.

[liu.jialu]

so, this Topic 241503 is duplicated issue, right?

yes, it’s a duplicate issue about the GPIO.

please also share the Orin device tree config for using GPIO3_PAC.05.

add bellow lines to file :
kernel_src/hardware/nvidia/platform/t23x/common/kernel-dts/t234-common-cvm/tegra234-cvm-p3701.dtsi

pps {
compatible = “pps-gpio”;
// pin:B8 (GPIO3_PAC.05)
gpios = <&tegra_main_gpio TEGRA234_MAIN_GPIO(AC, 5) GPIO_ACTIVE_LOW>;
};