-
Notifications
You must be signed in to change notification settings - Fork 14
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
error with LRAM initial values on LIFCL-17: no IP named LRAM_CORE_R11C0 #9
Comments
I made a "minimal" example, it's not that small because of all the parameters so I will attach the files here (with .txt suffix on the filenames to satisfy Github's rules). I'm not 100% sure the design is valid but Radiant synthesises it at least. |
In case it helps, the resulting .fasm file produced by Yosys seems to refer to the following:
|
Can you see if YosysHQ/nextpnr@13c037c fixes your problem? The basic example seems to build with that, at least. |
Thanks for the fast turnaround! It successfully produces a bitstream for my design now (the design still doesn't work but that's my own mistake I'm pretty sure). |
Ideally, if you can get it to a point where Radiant works and oxide doesn't then I'll be happy to have a further look for any other issues. |
Thanks for the offer. I think I am at that point now, I have a Litex design which Radiant synthesises and it boots but yosys+nextpnr+prjoxide produces a bitstream that does not boot. I think it must be a separate issue to this one because I am not relying on the LRAM initialisation in the design (just trying to verify that it loads the right values). But it's late on Friday here :-) so next week I will narrow it down and file a separate issue with what I am seeing. |
Okay, seems I was hitting a few issues... I took out all my LRAM initialization hacks, to make sure the issues were unrelated to this one. The first problem was that the NX-17 internal oscillator on the board I have runs about 8.6% faster than nominal, which is apparently still within range according to the datasheet. So it turns out in some of my designs, nextpnr was not really meeting timing for the faster clock but it didn't know about it because we declared the period constraint assuming 450MHz. I adjusted the constraint in: google/CFU-Playground#117 But aside from that, there does seem to be a weird problem where the yosys+nextpnr+prjoxide bitstream does not boot but the same design in Radiant works. I filed a new issue for that: #10 |
With the fix in #10, I was able to test the LRAM initialisation under yosys+nextpnr+prjoxide and I can confirm this is working nicely -- I have my design executing directly from LRAM :-) So we can close this issue, unless there is something more you wanted to leave it open for. |
I'm targetting LIFCL-17-8UWG72C, trying to use the
INITVAL_00
..INITVAL_7F
parameters to fill in initial values for LRAM. prjoxide panics, I guess because it doesn't know the location of all the LRAMs in this part?The text was updated successfully, but these errors were encountered: