-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instantiation of Xilinx PS hard IP #24
Comments
Hi, I will look at your other PR shortly. The way to use the PS is via a PS8 primitive- what you are attempting to use is a Xilinx IP core that wraps that. The IP core should be unencrypted Verilog so passing it to Yosys should work, you'll need to find all the files until you get down to a PS8 primitive. |
I'll google how to do that. Thanks for the directions! |
If you have a simple use case (e.g. just wanting a single clock), then it might be easier to use the PS8 directly rather than try and make the Xilinx verilog work: wire [3:0] plclk;
PS8 ps_i(
.PLCLK(plclk)
);
BUFG_PS bfg_i(
.I(plclk[0]),
.O(clk)
); is some code I have used on the zcu104 before. |
So far the information I can find on the zynq_ultra_ps_e is all encripted I don't think we could read in the verilog. I did found some .xci and .xml files with the ip information. But I don't think it would be possible to read them in. I will give a try at your example. By the way what is the PS8? Is it a PLL? I couldn't find it in neither the UltraScale Architecture Libraries Guide UG974 nor in the UltraScale Architecture Clocking Resources UG572 Thanks! |
Sadly, its not documented by Xilinx but PS8 is the low level interface to the Zynq block (processing system 8). It is what the Xilinx IP cores wrap. |
Description
I am working in PR #20 to add an example for the Ultra96 board.
The blinky example requires instantiating the PS (processing system) hard IP because the clock is obtained from there.
I created a blackbox module for the PS name
zynq_ultra_ps_e_0
in here.I am able to synthesize the design but when I call
nextpnr-xilinx
I get this error:Question
Is there a way to tell the tool where to get the information for the IP?
I can save the IP information as a TCL file, how could I read in that information?
Does the tool support mapping to specific hard IPs?
If it doesn't how could I contribute to it?
I have plenty of experience with TCL and Python but little with C++.
The text was updated successfully, but these errors were encountered: