-
Notifications
You must be signed in to change notification settings - Fork 78
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
issues with xc7 instructions for openocd #106
Comments
can we rewrite the guide to use https://github.com/trabucayre/openFPGALoader? This tool is way simpler to use than openOCD and it supports xc7 boards we target
|
I'd be willing to give it a try if it simplifies things overall.
|
this is not an issue if we just use it as a third party tool. (BTW openocd is GPL licensed) |
@kgugala - I'm afraid we can't touch anything which is AGPL. GPL is fine. |
oh, OK. So we need to fix openocd instructions then |
@kgugala - If anyone has a good relationship with the openFPGALoader people, it might be worth talking to them and seeing if they would consider "downgrading" to just GPL (rather than AGPL) -- which means we could then use them. I'm not sure the AGPL makes a lot of sense for their software anyway - the additions in AGPL are mainly focused towards "web" technologies like databases, web apps, etc. |
Seems its more than one person but the main committer is gwenhael.goavec-merou@trabucayre.com |
In case it's relevant: I'm not seeing any obvious difference between |
If this addressed by a PR in flight, just close this.
I'm going through the examples at https://symbiflow-examples.readthedocs.io/en/latest/building-examples.html .
After the counter example is built, the user is told to execute the following to program the part with the bitstream:
There are two things wrong with this:
digilent_arty.cfg
is not at the provided path. In fact I cannot find it at all in the installed tool directory. I have only installed the xc7 tools.cd
to the correct build directory, ortop.bit
should be replaced with the path to the correct fileThe text was updated successfully, but these errors were encountered: