please help confirm my last question. Then I think we are good here.
BTW, I think it is a little pointless to share that service if you don’t reveal the content of pcie-c5-fpga-reset.sh
By default if i use SDK Manager then the device boot up perfectly. The only issue is that C5 is disabled.
So instead of using SDK manager, i downloaded:
Jetson_Linux_R35.6.4_aarch64.tbz2
Tegra_Linux_Sample-Root-Filesystem_R35.6.4_aarch64.tbz2
Modified the two files one with ODMDATA and other with C5 then ran below command in recovery mode of XAVIER:
sudo ./flash.sh jetson-agx-xavier-devkit mmcblk0p1
Reset Script:
```bash
sudo tee /usr/local/bin/pcie-c5-fpga-reset.sh << ‘EOF’
#!/bin/bash
PCIE_DEV=“141a0000.pcie”
DRIVER_PATH=“/sys/bus/platform/drivers/tegra194-pcie”
echo 1 > /sys/bus/pci/devices/0005\:00\:00.0/remove 2>/dev/null
sleep 1
echo ${PCIE_DEV} > ${DRIVER_PATH}/unbind 2>/dev/null
sleep 3
echo ${PCIE_DEV} > ${DRIVER_PATH}/bind 2>/dev/null
sleep 3
echo 1 > /sys/bus/pci/rescan
logger “pcie-c5-fpga-reset: done”
EOF
sudo chmod +x /usr/local/bin/pcie-c5-fpga-reset.sh
```
Actually, sdkmanager is equal to Jetson_Linux_R35.6.4_aarch64+ Jetson_Linux_R35.6.4_aarch64.
I am still not sure how you get this error log.
FATAL ERROR [FILE=platform/drivers/uphy/uphy-tegra194.c, ERR_UID=475]: nvhs_uphy_pll_init failed
Bootstrap@0x501d1444 sp 0x50183e80 stack: 501820cc - 50183ff
Is it with default ODMDATA or it is with something that you modified?
I feel the above change is more like the key items to make PCIe work. But not the ODMDATA itself.
Unless I figure out what really happened on your device with that error, I would not suggest fully follow the steps mentioned here.