How should I modify the device tree

[Kimber]

I am using the TX2 NX module (P3636) and I set the default output level of GPIO3_PEE.02 in the device tree tegra186-p3636-0001-p3509-0000-a01.dts to low, but the actual test result is high 1.8V.

This pin is normal when I change TEGRA_AON_GPIO(AA, 6) to TEGRA_AON_GPIO(EE, 2) in the file tegra186-p3636-0001-a00-eqos.dtsi.

In the tegra186-p3636-0001-p3509-0000-a01.dts file, how can I program the pin (EE, 2) separately?

[KevinFFF]

Hi 13940204662,

Are you using the devkit or custom board for TX2-NX?
What’s your Jetpack version in use?

You should check the flash log to know which dts/dtb is in use.

You could also refer to the following instruction to configure the pinmux.
Jetson TX2 NX Adaptation and Bring-Up - Pinmux Changes

[Kimber]

I can confirm that this device tree file tegra186-p3636-0001-p3509-0000-a01.dts is used.
This is a carrier of our own design.
I have set this pin to the GPIO function via the pinnum table, driver 0.

Please tell me how I can add this code, here is my code:

 tegra186-gpio-aon@c2f0000 {      
        	GPIO_OUT3 {
        	        compatible = "nvidia,tegra186-gpio-aon";
			gpio-hog;
			output-low;
			gpios = <&tegra_aon_gpio TEGRA_AON_GPIO(EE,2) GPIO_ACTIVE_HIGH>;
			label = "GPIO_OUT3";
			status = "okay";
		};  
        };

[KevinFFF]

@Kimber

I have set this pin to the GPIO function via the pinnum table, driver 0.

It should be default low after using pinmux spreasheet and python pinmux-dts2cfg.py transforming to cfg file if you configure correctly.

You don’t need to configure them in device tree manually.

[Kimber]

What instructions should I use to update the .cfg file into my module?

[KevinFFF]

You could just use flash script in the BSP package which includes the updated cfg, and use the flash command to flash your board to apply.