: In the pre silicon example I have, there is a PCIe exerciser imbedded in the emulation model that communicates with an API running on arm. If we have a real PCIe interface with a Mentor PCIe bridge, can we connect an external exerciser to it or must we

:  In the pre silicon example I have, there is a PCIe exerciser imbedded in the emulation model that communicates with an API running on arm.  If we have a real PCIe interface with a Mentor PCIe bridge, can we connect an external exerciser to it or must we use a default interface

Parents
  • If you have a real PCIe exerciser device available that can perform the required tests, and you can implement the necessary Platform APIs to communicate with this external exerciser, then it is indeed a great option. Using a real PCIe exerciser in the pre-silicon environment can provide more accurate and reliable testing results, as it simulates real-world scenarios more closely.

    However, if the real PCIe exerciser is not available or not feasible to use in the pre-silicon environment, the embedded PCIe exerciser within the emulation model can still be a valuable resource. The embedded exerciser allows you to run tests and identify potential issues earlier in the design cycle, which can significantly reduce the cost and effort associated with addressing bugs and design flaws. Catching and resolving issues in the pre-silicon phase can save time and resources, as compared to having to redesign or respin the product after silicon implementation.

Reply
  • If you have a real PCIe exerciser device available that can perform the required tests, and you can implement the necessary Platform APIs to communicate with this external exerciser, then it is indeed a great option. Using a real PCIe exerciser in the pre-silicon environment can provide more accurate and reliable testing results, as it simulates real-world scenarios more closely.

    However, if the real PCIe exerciser is not available or not feasible to use in the pre-silicon environment, the embedded PCIe exerciser within the emulation model can still be a valuable resource. The embedded exerciser allows you to run tests and identify potential issues earlier in the design cycle, which can significantly reduce the cost and effort associated with addressing bugs and design flaws. Catching and resolving issues in the pre-silicon phase can save time and resources, as compared to having to redesign or respin the product after silicon implementation.

Children
No data