GPIO configuration in JETSON AGX ORIN

[ramesh.chr16]

we are using Jetson agx orin 32GB board .

1. Want to use the camera GPIO line(GPIO3_PAC.00) in pinmux sheet to our own purpose (using as status led).
   we have done changes for using the GPIO for status led in below dtsi file and reading the same in the kernel source , but its always failed to read the from the dtb file

   source/public/hardware/nvidia/platform/t23x/concord/kernel-dts/cvb/tegra234-p3737-camera-modules.dtsi
   

   Followed the below adaption guide to make the changes.

   Jetson AGX Orin Platform Adaptation and Bring-Up — Jetson Linux Developer Guide documentation

   Main DTS using : tegra234-p3701-0000-p3737-0000.dtb

   After flashing the images , as per the boot logs its taking “tegra234-p3701-0004-p3737-0000.dtb” file always, not sure why its taking this dtb file .
   our understanding is that its should take “tegra234-p3701-0000-p3737-0000.dtb” file.

[DaveYYY]

Hi,

0000 is the module which comes with a DevKit board.
0004 is the module which is sold alone without a DevKit, and has to be used with other third party carrier boards.
Please first make sure which one you are using.

[ramesh.chr16]

Hi ,

We have done changes in tegra234-p3737-camera-modules.dtsi and these changes are reflecting in tegra234-p3701-0000-p3737-0000.dtb file as the cvb/tegra234-p3737-camera-modules.dtsi is included in tegra234-p3701-0000-p3737-0000.dts file.

Similarly the tegra234-p3701-0000-p3737-0000.dts file was included in tegra234-p3701-0004-p3737-0000.dts file as shown below, but the changes made in tegra234-p3737-camera-modules.dtsi were not reflecting in tegra234-p3701-0004-p3737-0000.dtb file.

/dts-v1/;

include “tegra234-p3701-0000-p3737-0000.dts”

/ {
nvidia,dtsfilename = FILE;
nvidia,dtbbuildtime = DATE, TIME;

    compatible = "nvidia,p3737-0000+p3701-0004", "nvidia,p3701-0004", "nvidia,tegra234", "nvidia,tegra23x";

};

Thanks
Ramesh

[DaveYYY]

Then can you decompile the 0004 dtb, and directly copy changes that are available in the 0000 one?