-
Notifications
You must be signed in to change notification settings - Fork 242
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
Project mode with CLI #10
Comments
Issue is addressed in #11 |
@olofk Would you mind verifying that this implementation is adequate for your desired workflow? |
Sorry for the late reply. Turns out that I'm getting |
@olofk this could be the case when there is no .json file at all, you would need to generate it first with blinky.sh |
Ah, of course. Sorry. I assumed the unexpected EOF was referring to the project json file. It works as expected now. For the future it would be nice to have target frequency and output file in the project file as well, but this issue can be closed now. Thanks |
The project mode seems quite handy for FuseSoC. My idea is to generate a project file with all required properties and then let the user open it in the GUI or use it on the command-line to generate the bitstream with just the project file as input (This is how many of the other tool backends are implemented).
I can't figure out how to use project files on the command-line though.
nextpnr-ice40 --load blinky.proj
just seems to load the file and then exit (also, adding --gui doesn't do anything when --load is used).The text was updated successfully, but these errors were encountered: