If you're cascading Pericom switches then the tperst_n time needs to be at least multiplied - but this might not work, as the intermediate switch won't control downstream resets in the same manner.PERST_N was indeed left floating, however adding a PullDown did not seem to change the observed behavior.Are you using an evaluation add-in board with the switch or your own design?
If using an add-in board, does PERST_N float high with the CM4 RUN pin held low (or glitch high during power-on reset)?
We did some further testing in the meantime and the error only seems to occur if we use the two different PCIe-to-PCI Bridges we have available downstream of the switch. Other cards we tried seem to work without problems, though we only tried a limited number of devices.
Statistics: Posted by jdb — Fri Feb 23, 2024 4:52 pm
