ORIN Custom Board PCIe Link Cannot Be Established

[orkun.kayam]

Hi there. I’ve designed a custom carrier board for ORIN Industrial; however, I cannot link two devices over PCIe. I’m controlling PEX_C5_RST_N signal from an MCU but whenever I plug the ORIN module into my board, ORIN pulls PEX_C5_RST_N to low. That means C5 stays in reset no matter what. The two changes I did in the pinmux were configuring PEX_C5_RST_N as input and adding a Pull-Up, and also adding a Pull-Up to the GPIO31 PCIE_PRSNT signal since I’m not providing this signal from the edge connector. I haven’t routed CLK_REQ signals either.

Still, I do not know why ORIN pulls the reset low, or why I can’t establish a link. I’d be glad if someone could help.

[WayneWWW]

Orin has its own driver to controller the timing of RST. You should not control that by yourself.

I haven’t routed CLK_REQ signals either.

This seems to be wrong too. Please follow the design guide document.

[orkun.kayam]

Since I’m using C5 and C7 as an endpoint and due to the system requirements, I have to control the reset, PERST#, on C5 and C7 via an MCU. Speaking of CLK_REQ, as far as I know, clock request is used when a device goes into sleep. When I was designing the carrier, just because there wouldn’t be a sleep case in the system, I didn’t route.

Seems my carrier needs a revision, doesn’t it?

[WayneWWW]

Are you talking about you are making Jetson PCIe C5 and PCIe C7 both as endpoint mode but not RP?

If so, what is your software change there?

[siresber]

In EP (JL 35.6.0),

For C5 EP, in the p3701.conf.common file the ODMDATA value is changed based on this instructions.

Pinmux and GPIO files are created with the Excel file and copied to the required paths based on this instructions.

Pinmux filename value which is in the p3701.conf.common file is changed with copied pinmux filename.