You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last year I have set up (on a windows pc) the toolchain for writing a custom .BIT file for a mesa 5i20 card. (I experimented with bspi iirc). Would it be an idea to have a docker container or vagrant setup so it's easy to change functions and pins (let's say "configuring" for the uninitiated) for cards?
The text was updated successfully, but these errors were encountered:
and I'm pretty sure there is an altera based one as well. If you want to change bitfiles for the older Spartan based cards, you will probably need an ISE based setup, and I haven't tried to dockerize that yet.
As soon as I finish the zturn stuff I am planning on updating the Vivado image to the latest version which has a supposedly working web downloader, and no requirement for a license file anymore. I can maybe take a look at doing an ISE image as well.
For the SOC's changing a config is basically down to editing the relevant board file. We do really need to document the format of the module descriptor and the pin struct in that file though. Shoot, I've made 3 custom pin files now and I still forget how it's formatted.
Last year I have set up (on a windows pc) the toolchain for writing a custom .BIT file for a mesa 5i20 card. (I experimented with bspi iirc). Would it be an idea to have a docker container or vagrant setup so it's easy to change functions and pins (let's say "configuring" for the uninitiated) for cards?
The text was updated successfully, but these errors were encountered: