-
Notifications
You must be signed in to change notification settings - Fork 15
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
SEDC support? #24
Comments
In theory it's not too difficult to add, although it is indeed currently unsupported. However, for the SEDC to function correctly it would also need the ECCs in the bitstream (which are only used for SEDC and therefore currently don't matter) to be written correctly. From memory there would also need to be some prjtrellis modifications to correctly mask LUTRAM initialization from the ECC calculation which isn't currently done (although most of the ECC logic is correct). It's a bit of a shameless plug, but if you're using this in a commercial application then it would be possible to get this done quicker if you were willing to take out a support contract with YosysHQ. Otherwise it'd be interesting to know a bit more about your use case for this (you can also contact me privately via the email in my GH profile if you prefer). |
Well, in terms of our use case, we are the FemtoStar Project - I won't make this a shameless plug for our efforts either, but we're a currently-all-volunteer community of developers, working on a constellation of small satellites for open, privacy-respecting telecommunications. Nothing is orbital yet, but we've made good progress on development, thanks in part to the FOSS FPGA community. Our website is at https://femtostar.com/. We have been prototyping with the ECP5 and iCE40 (both using yosys+nextpnr, of course - all our work is FOSS, and our toolchains should be too) for over a year, but have recently become interested in the Nexus-family FPGAs, and just yesterday I got some of our code running on an LIFCL-40-EVN. It works, but given our satellites are intended to support operation in orbits of up to 1000 kilometers, radiation is an important consideration, and for that we would like to take advantage of as many reliability features as Nexus has to offer (not just the latch-up-immunity benefits of silicon-on-insulator), so that includes SEDC. We can, of course, continue to work without it (it's not as if the iCE40 or ECP5 even offer it), but if SEDC is something that could be supported with relative ease, it's certainly something we'd like to have working if we're going to put hardware supporting it in orbit. |
Sure that seems like an interesting enough use case! I will have a look to see if this can be done. |
I actually might have a group that would be willing to fund work on SEDC / ECC for the Lattice Nexus line in open source tooling (group also interested in using the Lattice Nexus line in low earth orbit satellites and high altitude aircraft). Do you want to start an email thread with my work email - tansell@google.com ? |
Lattice Nexus-family FPGAs include SEDC hardware for error detection and correction. A part of the sysCONFIG block, and documented here, it exposes a few inputs for configuration and a few outputs for status and error detection information. In Radiant, it can be instantiated from the IP Catalog, which seemingly mostly just generates a wrapper around an instantiated
SEDC
primitive. The instantiation looks like this:However, prjoxide does not seem to document this primitive, and it's seemingly not included anywhere in the source for prjoxide or nextpnr. Attempting to place and route this with nextpnr-nexus fails with
ERROR: Cell type 'SEDC' instantiated as 'sedc' is not supported by this device.
It seems like prjoxide just hasn't documented how SEDC works yet. I'm not really familiar enough with the prjoxide fuzzing/development process to try to implement this myself, or really to determine how complex that would be. If I'm wrong and this has already been documented and implemented, how should the SEDC primitive be instantiated when using the yosys+nextpnr+prjoxide toolchain? If not, what's the status of work on SEDC documentation in prjoxide?
The text was updated successfully, but these errors were encountered: