-
Notifications
You must be signed in to change notification settings - Fork 168
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
_yosys fails to parse Yosys version from fomu-toolchain #409
Labels
Milestone
Comments
It is not possible to do option 2, since the output of nMigen has to be customized for the Yosys version it works with (RTLIL is not stable); so option 1 seems sensible. |
Will do. |
I would be fine with (3) but I think we should do (1) in parallel, since this is probably not the last time we encounter such Yosys builds. |
alanvgreen
added a commit
to alanvgreen/nmigen
that referenced
this issue
Jun 23, 2020
Do not use versions of yosys with unparseable version numbers. This ensures that nmigen always knows what verion of yosys it is generating RTLIL for. Issue amaranth-lang#409.
alanvgreen
added a commit
to alanvgreen/nmigen
that referenced
this issue
Jun 23, 2020
Do not use yosys binaries with unparseable version numbers. This ensures that nmigen always knows what version of yosys it is generating RTLIL for. The effect of this change is that if the version number of the system yosys is unparsable, nmigen will attempt to fallback to the builtin Yosys. Issue amaranth-lang#409.
alanvgreen
added a commit
to alanvgreen/nmigen
that referenced
this issue
Jun 23, 2020
Do not use yosys binaries with unparseable version numbers. This ensures that nmigen always knows what version of yosys it is generating RTLIL for. The effect of this change is that if the version number of the system yosys is unparsable, nmigen will attempt to fallback to the builtin Yosys. Issue amaranth-lang#409.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been yosys and nextpnr-ice40 from v1.5.6 of the fomu-toolchain, downloaded from https://github.com/im-tomu/fomu-toolchain/releases/tag/v1.5.6
The version number reported by the fomu-toolchain build of yosys is not compatible with the version number parser in _yosys.py. Here is the traceback from calling platform.build():
The above message is due to match being None, since the regex match failed.
Here is the yosys version string from the fomu build of yosys:
Here are a couple of possible solutions:
Of these, think 1 is best. I'm happy to try making a PR for either 1 or 2.
The text was updated successfully, but these errors were encountered: