Skip to content
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

nextpnr-ice40 vers .9 and .10 give "unmatched constraint" warnings for each pin defined in .pcf #5

Open
ProbabilityEngineer opened this issue Jan 23, 2024 · 5 comments

Comments

@ProbabilityEngineer
Copy link

When building with nextpnr-ice40 in version .9 and .10 I get warnings such as:
"Warning: unmatched constraint 'clk_in' (on line 5)" for each set_io line in the .pcf.
You can still build and upload from the command line.

In Icestudio I get:
"There are errors in the Design...
ERROR: 10 'o' is unconstrained in
PCF (override this error with --pcf-allow-unconstrained)"
Icestudio stops building at these errors.

I don't know if this is a bug or a design change.

If I replace nextpnr-ice40 with the .08 version it doesn't throw warnings in command line. This doesn't stop the errors in Icestudio! Returning to the .08 package in full fixes the problem.

I repeated this behavior on nandland go board and ice40-hx1k-evb board with examples led and bilnky.

I did not get this evhavior with ulx3s-85f ecp5 board.

@ProbabilityEngineer ProbabilityEngineer changed the title nextpnr-ice40 vs .9 and .10 give "unmatched constraint" warnings for each pin defined in .pcf nextpnr-ice40 vers .9 and .10 give "unmatched constraint" warnings for each pin defined in .pcf Jan 23, 2024
@cavearr
Copy link
Member

cavearr commented Jan 23, 2024

Hi @Sam99C, I'm working on the new version of the toolchain for osx arm64 with your advice, I was working on other things and I didn't check the nwjs project since August and I didn't know that they finally released the native version of arm, many thanks for the feedback, very soon we have a native osx arm version.

Yesterday and today I have been working on it and now I am preparing version 0.10 with the new versions of oss-cad-suite, openfpgaloader, etc. (now working version of wip is 0.9).

I need to test many boards until I publish them and it will take me a couple of days.

The 0.8 toolchain is very old and the tools evolve a lot. Your errors are probably design errors, which at the time (in the publication of 0.8 they were valid but now with the evolution of the tools there will be checks that fail) if you send me your .ice I will try to help you.

If you want to join the fpgawars group and put your problem, there are more colleagues who can help you,
https://groups.google.com/g/fpga-wars-explorando-el-lado-libre

Although it is apparently in Spanish, we usually communicate in English.

@ProbabilityEngineer
Copy link
Author

Hey there, thanks for getting back to me so fast!

I don't have a project with a problem, I'm an absolute beginner playing with the examples! I was just testing things to see if I could make a workaround for gatekeeper objecting to the toolchain so I could make an install guide on youtube. It sounds like I should just wait for a native version before making videos.

I only have a nandland go board but if I can help with testing please get in touch.

Thanks for all your hard work! I wouldn't be able to play with FPGAs without Icestudio to get me started!

@cavearr
Copy link
Member

cavearr commented Jan 24, 2024

Hi @Sam99C !! don't worry if you want to try and experiment with this, go ahead!! and tell me all of you need.

If you prefer wait for the new version, it's ok!

And thanks to you for use Icestudio and give me feedback, and try to document and fix things.

If you make videos, tutorials, etc, tell me please!

@zapta
Copy link
Contributor

zapta commented Nov 11, 2024

Hi @ProbabilityEngineer, do you have a sample project that we can use to reproduce it?

@ProbabilityEngineer
Copy link
Author

I have a feeling I fixed this, possibly by diffing the versions of the toolchain, but I don’t remember. Either that or it was fundamental to the updated toolchain and I changed the project I was working on. I don’t have a computer right now so I can’t dig into it further, sorry. Remind me in a month if you want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants