Yes, we flash with the correct ODMDATA setting.
We were able to spend some time with the devkits, and we tried something unusual: we ignored the errors. Even though the console has a handful of errors, the pcie_ep@141a0000 actually initialized correctly.
The Errors:
root@orin-840:~# dmesg | grep pcie_ep
[ 5.941382] tegra194-pcie 141a0000.pcie_ep: Adding to iommu group 9
[ 5.955351] tegra194-pcie 141a0000.pcie_ep: Failed to get PERST GPIO: -517
[ 5.955361] tegra194-pcie 141a0000.pcie_ep: Failed to parse device tree: -517
[ 7.227340] tegra194-pcie 141a0000.pcie_ep: Using GICv2m MSI allocator
[ 7.234087] tegra194-pcie 141a0000.pcie_ep: Failed to get slot regulators: -517
[ 8.954495] tegra194-pcie 141a0000.pcie_ep: Using GICv2m MSI allocator
However, when we turn on the endpoint and reboot the rootport, the devkit to devkit link works!
BUT. Our custom carrier does not work. Following the exact same procedure, we get errors on the endpoint that look like:
[ 326.878577] CPU:0, Error: cbb-fabric@0x13a00000, irq=34
[ 326.878668] tegra194-pcie 141e0000.pcie_ep: PCIe controller is not set to EP mode (hdr_typ
e:0x7f)!
[ 326.883979] **************************************
[ 326.883982] CPU:0, Error:cbb-fabric, Errmon:2
[ 326.883991] Error Code : TIMEOUT_ERR
[ 326.893220] tegra194-pcie 141e0000.pcie_ep: Failed to complete initialization: -5
[ 326.898144] Overflow : Multiple TIMEOUT_ERR
(Before we had not even tried to start the endpoint because of the console errors).
We have flashed this multiple times in multiple ways (direct flash, over-the-air, etc) and we always get this message. For what its worth, we get the message every time the root port tries to initiate a link. But the link never closes.
Following: Orin C7 PCIe EP set Ethernet Interface over PCIe msi interrupt error, we tried to add the nvidia,host1x field, but it did not appear to change the results.
Any advice is welcome.