11-07-2018 05:05 AM
Hello dear experts,
inoder to test my pci port, i have added the entire IP eyescan subsystem(xapp1198) into my project, and connected them through DRP interface. Now i need to generate a corresponding .elf file for the project.
i have generated and specified the .hdf file in SDK, and also imported the provided software source code. But when i opened the code there is error showed in picture. But in fact i havent changed anything in source code.
Anyone knows how to solve this problem? how should i modify the code?
11-07-2018 07:23 AM
Update:
i just commented out the line where the error is. now when i run "run_eyescan" in Vivado console, the result comes out is like a endless loop:
can someone help me? im so exhausted...
best regards
11-08-2018 02:38 AM
11-08-2018 09:02 AM
11-09-2018 02:26 AM
Thank you for your reply. now SDK reports no error anymore. But the result of running run_scan is still not right. the message is like:
do you konw whats the problem?
best regards
haofei
11-12-2018 08:15 PM
Here's where I would start:
1. ensure your DRP is connected correctly. The clocks too. Look in the schematic view to double check.
2. ensure your addressing is correct between the IPI design and the C code. Check both the BRAM and DRP addresses
3. start off with one lane; which I think you are.
4. ensure that the C-core matched the GT type you're using.
5. ensure your DRP clock frequency is constrained somewhere.
11-13-2018 09:01 AM
thank you very much for your advise.
i just used the user_clk_out signal comes from PCIE IP, which is the AXI interface clock, to drive the DRP Port. and nothing more constrains are applyed.
just connect user_clk_out to pcie_drp_clk , is it enough? how should i constrain it furthermore?
how should i check if the C-core matched the GT type?
best regrad
11-14-2018 04:02 AM
thank you very much for your advise.
i just used the user_clk_out signal comes from PCIE IP, which is the AXI interface clock, to drive the DRP Port. and nothing more constrains are applyed.
just connect user_clk_out to pcie_drp_clk , is it enough? how should i constrain it furthermore?
how should i check if the C-core matched the GT type?
best regrad
11-19-2018 07:16 AM
user_clk_out should work fine. Make sure the reset to the subsystem you use is synchronous to user_clk_out. I don't think the reset is your issue, but for this to work consistently, the synchronous reset is important.
Regarding the C-Code, let me know which SERDES (GTY, GTP ) and device you're using. Then post the C code you're using. Include the header.