I will try that. We are using Jetpack 5.1.2 (rel-35.2.1).
Updated and reflashed. Still receiving the same issue. Here is dmesg:
ubuntu@ECAuto2:~$ sudo dmesg | grep -i “1418”
[ 6.538789] tegra194-pcie 14180000.pcie: Adding to iommu group 9
[ 6.551236] tegra194-pcie 14180000.pcie: Using GICv2m MSI allocator
[ 7.732379] tegra194-pcie 14180000.pcie: Using GICv2m MSI allocator
[ 7.742915] tegra194-pcie 14180000.pcie: host bridge /pcie@14180000 ranges:
[ 7.753994] tegra194-pcie 14180000.pcie: IO 0x0038100000…0x00381fffff 0
[ 7.766373] tegra194-pcie 14180000.pcie: MEM 0x2728000000…0x272fffffff 0
[ 7.775072] tegra194-pcie 14180000.pcie: MEM 0x2440000000…0x2727ffffff 0
[ 8.892841] tegra194-pcie 14180000.pcie: Phy link never came up
[ 8.899010] tegra194-pcie 14180000.pcie: PCI host bridge to bus 0000:00
I uploaded my tegra234-p3737-pcie.dtsi file. Does that look correct?
Jetpack5.1.2 is rel-35.4.1. Not rel-35.2.1…
Please dump below node so that I can make sure the pinmux setting you are using is really correct.
-
cat /sys/kernel/debug/pinctrl/2430000.pinmux/pinconf-group
-
sudo busybox devmem 0x02213000
-
sudo busybox devmem 0x02213020
It looks like my pinmux is not being recognized. Here are the results from your query:
ubuntu@ECAuto2:~$ sudo cat /sys/kernel/debug/pinctrl/2430000.pinmux/pinconf-grou
p
cat: /sys/kernel/debug/pinctrl/2430000.pinmux/pinconf-group: No such file or dir
ectory
ubuntu@ECAuto2:~$ sudo busybox devmem 0x02213000
0x00000000
ubuntu@ECAuto2:~$ sudo busybox devmem 0x02213020
0x00000000
ubuntu@ECAuto2:~$
Run as sudo if you want to access /sys/kernel/debug…
I did, for all 3 commands. Highlighted above.
then please run as root and go to /sys/kernel/debug/ and show me what you got there…
ubuntu@ECAuto2:~$ sudo busybox devmem 0x02213000
0x00000000
ubuntu@ECAuto2:~$ sudo busybox devmem 0x02213020
0x00000000
These two look correct. These are GPIO register for PK0 and PK1 pin and all bit are 0. This means gpio is not enabled. Expected result because we want to set them as SFIO.
If you don’t know what I am talking about. Please tell…
I don’t need your excel. No need to share that…
Please go to pinctrl directory in above screenshot…
I tried to share my pimux file, but the system is flagging as a virus and wont allow.
Please just follow instructions… no need to share any other files. Just focus on what we are doing now is sufficient…
root@ECAuto2:/sys/kernel/debug/pinctrl# ls -ltr
total 0
-r–r–r-- 1 root root 0 Jan 1 1970 pinctrl-maps
-r–r–r-- 1 root root 0 Jan 1 1970 pinctrl-handles
-r–r–r-- 1 root root 0 Jan 1 1970 pinctrl-devices
drwxr-xr-x 2 root root 0 Jan 1 1970 2430000.pinmux
drwxr-xr-x 2 root root 0 Jan 1 1970 c360000.pmc
root@ECAuto2:/sys/kernel/debug/pinctrl#
Found it.
pinmux-groups is under
/sys/kernel/debug/pinctrl/2430000.pinmux/
What should I be looking for in that file?
Just try to clarify what we are doing now…
I asked you to follow the document as this screenshot to modify pinmux.
Now we are dumping the pinmux setting on the board to know if the setting really matches above or not…
pk0 and pk1… we need to check the status from pinmux-groups…
OK Here are the status for pk0 & pk1 from pinmux-groups:
59 (pex_l0_clkreq_n_pk0):
pull=0
tristate=1
enable-input=1
open-drain=0
io-reset=0
rcv-sel=0
io-hv=0
loopback=0
schmitt=0
pull-down-strength=0
pull-up-strength=0
drive-type=0
func=pe0
pad-power=160 (pex_l0_rst_n_pk1):
pull=0
tristate=0
enable-input=0
open-drain=0
io-reset=0
rcv-sel=0
io-hv=0
loopback=0
schmitt=0
pull-down-strength=0
pull-up-strength=0
drive-type=0
func=pe0
pad-power=1
NVME external drive not recognized with AGX Orin SoMs - #8 by smcentee
Above comment checked the ODMDATA, which is correct.
Latest comment checked the pinmux, which is correct too.
The last thing to check if phys are correct. Please dump your runtime device tree as this command.
dtc -I fs -O dts -o ./extracted.dts /proc/device-tree
ok done. What should I be looking for in ‘extracted.dts’? The file is quite large.
Attach it here and I will help check…
If you have problem attaching the file, rename it to devicetree.txt and attach.