Should bug reports regarding the 'official' EOS-S3 toolchain be submitted here in the forums, or at the QuickLogic github repo[1] ?
Asking because the above repo hasn't been updated in about 2 years...
Some of the EOS-S3 constraint issues I've encountered have been fixed in the newer F4PGA toolchain[2], but its EOS-S3 flow is labeled as "currently unsupported" [3].
-Brian
[1] https://github.com/QuickLogic-Corp/quic ... -toolchain
[2] https://github.com/chipsalliance/f4pga
[3] https://f4pga.readthedocs.io/en/latest/f4pga/Usage.html
"Quicklogic EOS-S3 (currently unsupported, provided only for development purposes)"
Bug reporting for EOS-S3 FPGA toolchain
The QuickLogic support for EOS S3 has been rolled into the f4PGA release at https://github.com/chipsalliance/f4pga-examples
Instructions on installing and running the demo is available at https://f4pga-examples.readthedocs.io/e ... tting.html
Example project is available at https://github.com/search?q=qorc-onion- ... positories
You are correct f4PGA are not supporting EOS S3, so please log any issues here and QuickLogic will look to see how we can support.
--Robert
Instructions on installing and running the demo is available at https://f4pga-examples.readthedocs.io/e ... tting.html
Example project is available at https://github.com/search?q=qorc-onion- ... positories
You are correct f4PGA are not supporting EOS S3, so please log any issues here and QuickLogic will look to see how we can support.
--Robert
-
chilechevrolet
- Posts: 2
- Joined: Sat Aug 29, 2026 1:07 am
I’d probably post the bug reports here first, especially if the GitHub repo hasn’t seen any updates in two years. It would be good to know whether the EOS-S3 flow is still officially maintained or if development has effectively moved elsewhere.
I’d probably report EOS-S3-specific issues in this forum, especially since the F4PGA documentation says the EOS-S3 flow is unsupported. That way QuickLogic can see problems that might be specific to their device support.
For general F4PGA issues, the GitHub repo would make more sense. It would also be useful to know whether there’s a recommended version/commit of F4PGA for EOS-S3 development.
For general F4PGA issues, the GitHub repo would make more sense. It would also be useful to know whether there’s a recommended version/commit of F4PGA for EOS-S3 development.
Since F4PGA has fixes for some EOS-S3 constraint issues, I’d suggest reporting reproducible bugs in the repository where the issue actually occurs, with a minimal example and the toolchain version. That makes it easier for maintainers to verify the problem and track any fix. The bigger concern is whether anyone is still maintaining the official flow. If the QuickLogic repository is effectively inactive, a clear statement about the supported toolchain and whether F4PGA fixes can be upstreamed would help developers avoid duplicating work.brimdavis wrote: ↑Thu Jun 08, 2023 10:54 pm Should bug reports regarding the 'official' EOS-S3 toolchain be submitted here in the forums, or at the QuickLogic github repo[1] ?
Asking because the above repo hasn't been updated in about 2 years...
Some of the EOS-S3 constraint issues I've encountered have been fixed in the newer F4PGA toolchain[2], but its EOS-S3 flow is labeled as "currently unsupported" [3].
-Brian
[1] https://github.com/QuickLogic-Corp/quic ... -toolchain
[2] https://github.com/chipsalliance/f4pga words with letters
[3] https://f4pga.readthedocs.io/en/latest/f4pga/Usage.html
"Quicklogic EOS-S3 (currently unsupported, provided only for development purposes)"