We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome,
Internet Explorer 11,
Safari. Thank you!
AR# 35212: Design Assistant for PCI Express - How to capture Endpoint Block Plus Wrapper internal signals using ChipScope Inserter?
Design Assistant for PCI Express - How to capture Endpoint Block Plus Wrapper internal signals using ChipScope Inserter?
This Answer Record describes how tocapture Endpoint Block Plus Wrapper internal signals using ChipScope Inserter. NOTE:This Answer Record is part of the Xilinx Solution Center for PCI Express(Xilinx Answer 34536).TheXilinx Solution Center for PCI Express is available to address all questions related to PCIe. Whether you are starting a new design with PCIe or troubleshooting a problem, use the Solution Center for PCIeto guide you to the right information.
Following are the steps to perform to capture signals with ChipScope inserter.
After generating the core in CORE Generator, modify xst.scr in the implement directory to set KEEP_HIERARCHY to true.
Run implement.bat/implement.sh depending on the operating system you are using.
Once the synthesis is complete the ngc file called xilinx_pci_exp_ep.ngc is generated in the results directory inside the implement directory.
Open ChipScope inserter and follow the steps as shown in the screen captures below:
Select the Trigger Width as required:
Select the "Data Width" and "Data Depth" as required:
Double-click on any of the ports shown in red below:
Click on appropriate section of the hierarchy to select the signals.
Once trigger, data, and clock signals have been selected, click OK and then click Insert>.
A new ".ngc" fileis generated with ChipScope core inside it, replacing the existing one.Before closing the ChipScope Inserter, save the project; a ".cdc" fileis generated. This ".cdc" file is required to view the signals in ChipScope Analyzer.
Re-implement the design by running implement.bat/implement.sh. Make sure a section of the script with commands to synthesize has been removed.