The Document Pinmux error.

We had flowed the document about “how to configure the pinmux”.

open the file "Jetson-TX2-Generic-Customer-Pinmux-Template.xlsm "
gen the dtsi file , with MS excel.(tegra18x-pinmux.dtsi tegra18x-gpio-default.dtsi tegra18x-padvoltage-default.dtsi)

put the dtsi files to kernel/pinmux.

gen the BCT file

root@tx2-Host:/home/jetpack31/64_TX2/Linux_for_Tegra_tx2/kernel/pinmux# python pinmux-dts2cfg.py --pinmux addr_info.txt gpio_addr_info.txt por_val.txt mandatory_pinmux.txt tegra18x-quill-p3310-1000-pinmux.dtsi tegra18x-quill-p3310-1000-gpio-default.dtsi 1.0 > tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg
ERROR: pin dap2_sclk_pc1(0x00000440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dap2_dout_pc2(0x00000440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dap2_fs_pc4(0x00000440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dap1_sclk_pj0(0x00000440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dap1_dout_pj1(0x00000440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dap1_fs_pj3(0x00000440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dmic1_clk_pm1(0x00004441) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dmic2_clk_pm3(0x00004441) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dmic2_dat_pm2(0x00004441) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dap4_sclk_pcc0(0x00004440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dap4_dout_pcc1(0x00004440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin dap4_fs_pcc3(0x00004440) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_pq0_pi0(0x00004446) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_pq1_pi1(0x00004446) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_pq3_pi3(0x00004446) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_cam4_pn3(0x00000445) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_cam5_pn4(0x00000445) field nvidia,tristate(0x00000010) is not matching, val = 0x00 expected = 0x01
ERROR: pin gpio_cam6_pn5(0x00000445) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_cam7_pn6(0x00000449) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin sdmmc1_clk_pd0(0x00004460) field nvidia,pull(0x0000000c) is not matching, val = 0x00 expected = 0x01
ERROR: pin sdmmc3_clk_pg0(0x00000440) field nvidia,pull(0x0000000c) is not matching, val = 0x00 expected = 0x01
ERROR: pin gpio_dis5_pu5(0x00000411) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00
ERROR: pin uart5_rx_px5(0x00000412) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_mdm4_py3(0x00000449) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gp_pwm6_pl6(0x00000410) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00
ERROR: pin gp_pwm7_pl7(0x00000410) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_wan5_ph0(0x00000446) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_wan6_ph1(0x00000446) field nvidia,tristate(0x00000010) is not matching, val = 0x00 expected = 0x01
ERROR: pin gpio_wan7_ph2(0x00000446) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_wan8_ph3(0x0000044a) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_sen1_pv1(0x00000444) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_sen2_pv2(0x00000444) field nvidia,tristate(0x00000010) is not matching, val = 0x00 expected = 0x01
ERROR: pin gpio_sen3_pv3(0x00000444) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00
ERROR: pin gpio_sen4_pv4(0x00000448) field nvidia,enable-input(0x00000040) is not matching, val = 0x01 expected = 0x00

The error is ok or not ???

We had not changed the file “Jetson-TX2-Generic-Customer-Pinmux-Template.xlsm” yet, Maybe some wrong with the xlsm ???

hello wuyankun1986,

could you please share the “Revision History” of the JetsonTx2 pinmux spreadsheet you’re using.
thanks

hello JerryChang,

The Revision With the title of “Jetson TX2 Module Pinmux 1.0 2017/05/01”

Revision History

Date Revison Description
5/1/17 v1.0 Initial Release

R28.1 with jetpack 3.1.

thanks.

can anyone help, thanks .

@JerryChange,

to repeat the problem is very easy. can you repeat it ,thanks.

hello wuyankun1986,

yes, we had confirmed there was an issue with the pinmux spreadsheet.
we had investigate this internally. will correct and update the spreadsheet later.
thanks

hello JerryChang,

we found that you had release a new version “1.04” 20171130

But we found the same as the 1.0 20170501 , and the version of 20170501 is gone.

we can’t find the version of 1.0 in the download center.

we use the tool “diff” , there is not different with each other.

Hi wuyankun1986,

The new version v1.04 of the Jetson Tx2 pinmux spreadsheet should be updated correctly now, please download again.

Thanks

@kayccc

yes, the file is different , but there are still some errors.

ERROR: pin sdmmc4_clk …
ERROR: pin uart5_rx_px5…
ERROR: pin gp_pwm6_pl6…
ERROR: pin gp_pwm7_pl7…

please check, we had fixed the xlsm configure by ourself.

hello wuyankun1986,

could you describe more about what’s the failure.
you met these when running the python scripts to generate dtsi? could you please share the whole error messages to the attachment for us.
also, did generated dtsi file workable for your remaining works?
thanks

@JerryChang,

No, meet the error, when running the python scripts to generate cfg.

root@tx2-Host:/home/jetpack31/64_TX2/Linux_for_Tegra_tx2/kernel/pinmux# ./runme.sh
ERROR: pin sdmmc4_clk(0x00002460) field nvidia,pull(0x0000000c) is not matching, val = 0x00 expected = 0x01
ERROR: pin uart5_rx_px5(0x00000412) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00
ERROR: pin gp_pwm6_pl6(0x00000410) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00
ERROR: pin gp_pwm7_pl7(0x00000410) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00
root@tx2-Host:/home/jetpack31/64_TX2/Linux_for_Tegra_tx2/kernel/pinmux# pwd
/home/jetpack31/64_TX2/Linux_for_Tegra_tx2/kernel/pinmux
root@tx2-Host:/home/jetpack31/64_TX2/Linux_for_Tegra_tx2/kernel/pinmux# cat runme.sh
#!/bin/bash

python pinmux-dts2cfg.py --pinmux addr_info.txt gpio_addr_info.txt por_val.txt mandatory_pinmux.txt tegra18x-jetson-tx2-config-template-pinmux.dtsi tegra18x-jetson-tx2-config-template-gpio-default.dtsi 1.0 > tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg

python pinmux-dts2cfg.py --pad pad_info.txt tegra18x-jetson-tx2-config-template-padvoltage-default.dtsi 1.0 > tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg
root@tx2-Host:/home/jetpack31/64_TX2/Linux_for_Tegra_tx2/kernel/pinmux#

we just modify the pinmux.dtsi,

find the node “sdmmc4_clk”

sdmmc4_clk {
nvidia,pins = “sdmmc4_clk”;
nvidia,function = “sdmmc4”;
nvidia,pull = <TEGRA_PIN_PULL_NONE>;
nvidia,tristate = <TEGRA_PIN_DISABLE>;
nvidia,enable-input = <TEGRA_PIN_ENABLE>;
}

TEGRA_PIN_PULL_NONE value = 0x00
TEGRA_PIN_PULL_DOWN value = 0x01
TEGRA_PIN_PULL_UP value = 0x02

so, change it to:

sdmmc4_clk {
nvidia,pins = “sdmmc4_clk”;
nvidia,function = “sdmmc4”;
nvidia,pull = <TEGRA_PIN_PULL_DOWN>;
nvidia,tristate = <TEGRA_PIN_DISABLE>;
nvidia,enable-input = <TEGRA_PIN_ENABLE>;
}

no error now,

xlms generate the dtsi, but the txt files come from the jetpack3.1

So maybe it’s the answer.

I have this issue too. wuyankun1986 can you confirm that your solution not only generates a pinmux.cfg without an error, but also works correctly on the hardware?

Also, I have a similar issue: in our design we want to use I2S as a slave - AFAIK this should be possible. In the pinmux XLSM I set the DAP2_SCLK (CLK) and DAP2_FS (LRCLK) as input.
However the pinmux-dts2cfg.py generates the following error messages:

pin dap2_sclk_pc1 field nvidia,enable/input is not matching, val = 0x01 expected = 0x00

Apparently the tool does not like having a slave I2S configuration.

I have this issue too. wuyankun1986 can you confirm that your solution not only generates a pinmux.cfg without an error, but also works correctly on the hardware?

Hi wachagi,
we develop our case on the developer kit. focus on the camera.(CSI,j21).
we had not tested the I2S, or SD card.
I can’t give any answer to you, sorry. Maybe you can try it.

we should modify the xlms by ourselves. to match our case. thanks.

Hello all,

I working on Jetson TX2 Board ID(3310) version(B02) sku(1000) revision(C.0).
I facing difficult to enable and disable gpio and I2C i made used latest pinmux xlsm and generated dtsi.
steps:
for PINMUX Cfg
python pinmux-dts2cfg.py --pinmux addr_info.txt gpio_addr_info.txt por_val.txt --mandatory_pinmux_file mandatory_pinmux.txt tegra18x-jetson-tx2-config-template-pinmux.dtsi tegra18x-jetson-tx2-config-template-gpio-default.dtsi 1.02 > tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg

for PAD cfg
python pinmux-dts2cfg.py --pad pad_info.txt tegra186-quill-char-e3301-1080-a00-padvoltage-default.dtsi 1.0 > tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg

cp tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg …/…/…/bootloader/t186ref/BCT/

but still i am not able see my changes.

DSPK_OUT_DAT GPIO3_PJ.07 made change as a input but default was output and gpio pin 399. Did i am following the correct steps are or not. please help out me.

hello parashuram.biradar,

please refer to Jetson TX2 MB1 Platform Configuration for the details of pinmux and GPIO configurations.
you should also check developer guide, Configuring the 40-pin Expansion Header for the pin configuration.

please also note that you’re replying an almost 2-years ago discussion thread.
you should initial a new one for better supports.
thanks