Closed lushaylabs closed 1 month ago
There is an issue on windows where nextpnr-himbaechel is by default searching for the chibdb under:
The issue ended up being in nextpnr so I opened a PR there https://github.com/YosysHQ/nextpnr/pull/1314
So this PR is good to go from my side
hi @mmicko this is my first time contributing to this repo, is there anything I should do for this pr? like add a reviewer or something like that
Sorry @lushaylabs just was too busy. Will take care of this PR.
no worries, and thank you, just wanted to check to make sure I wasn't missing something from my end
@lushaylabs Sorry was bit busy today, but there are couple of things wrong. You create chipdb files using pip installed apycula and not one from build (that can potentially be different), also you depend on apicula-bba which is not used at all. Himbaechel build should be just binary, and independent of architecture, only chip databases should be built as separate packages as native (so once built since that is just data no code). If you do not mind I would take care of these changes. Idea is to be easy later to add new architecture.
I guess I should force flat install since apycula does not work when in egg
I used the pip version of apycula, the previous version (nextpnr-gowin) had an option to accept a precalculated bba file so this wasn't needed. It would pull the bba export and build nextpnr. nextpnr-himbaechel doesn't have this option so I had to add the 'python3-native' dependency and install the pip version as a pre-step scripts/nextpnr-himbaechel.sh
A have merged your changes and added changes I mentioned above. Please do try it in your setup and ping me with results. Sorry I did not took a look at this one before.
Added nextpnr himbaechel for Gowin chips