-
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
Error encountered with FASM, antlr_to_tuple, running xc7 counter example #108
Comments
Could you please try:
and post the results? Thanks. |
Result:
Then
but the result is the same
|
The ANTLR parser has some dependencies outside of PyPI, which is why the fallback parser is necessary. Could you please post the results of:
Thanks. |
...descending into package hell...
If I go ahead with the clone and attempt to build:
|
I also run into the same issue with antlr_to_tuple, so it's not an isolated issue. |
Any idea why this isn't appearing in the CI? |
You'll definitely need @mithro CI has
|
I think the warning would be more helpful if it just referred to the build instructions. |
@HackerFoo I do have cmake installed. Here is the output of
|
I do have cmake -- as a Python module.
In other instructions that asked me to But, let me get to the bottom of why the apt install of cmake doesn't work for me. |
@andrewb1999 I can see that
|
@HackerFoo Looks like it's not getting the cython dependency correctly (same issue as @tcal-x )
|
|
My problems installing |
I ran this to take care of the Cython requirement:
Then I followed the instructions on the page https://github.com/symbiflow/fasm#build-instructions including the
and then the original SymbiFlow build of the counter example worked.
|
What is the status of this? |
https://github.com/SymbiFlow/symbiflow-arch-defs/blob/master/environment.yml should provide all necessary dependencies after f4pga/f4pga-arch-defs#1908 |
It looks like the install instructions specify an older version of the toolchain. Should this be automatically updated somehow? There are "latest" text files that specify the latest URL: https://github.com/litex-hub/litex-conda-eda/blob/master/pnr/vtr-optimized/build.sh#L34-L53
|
I've assigned this to myself to check if the issue has been resolved. |
Nothing has changed; I still see the original error. It seems we either need to address #115, or, as a band-aid, manually update the versions. |
Correction: the final warning from fasm looks like failure, but in fact a bitstream is produced, and it works correctly on the Arty 35T board ( I had noticed in Quicklogic guides for QORC, they specifically describe this warning and tell the user that it's ok. This is the warning:
|
@tcal-x - Yes, that is a warning but means the command will be much slower. We should make sure the fast path is what most people get by default. |
I was also running into this. Although there is a fallback, the warning would be printed to my fasm file, which would then break things:
I followed @HackerFoo 's instructions and did the following:
After which I realized I needed to:
This fixed thing for me and the fasm.parser ImportError is gone. Hope this helps others. |
EDIT: my mistake, I didn't see the submodule update! in fasm/, "make build" is now giving me this:
|
Couple things. First, we have an PyPi account setup, so if someone adds a PyPi publish to https://github.com/symbiflow/fasm, this issue becomes must easier to solve! Second, there are instructions in https://github.com/SymbiFlow/fasm/blob/master/README.md on how to build FASM with the ANTLR parser. Issue with more details: f4pga/f4pga-arch-defs#1846 |
Ok, I think it is resolved. I was able to generate the bitstream without the fallback warning:
|
After a clean install of xc7 tools according to the symbiflow-examples instructions, I get to the first example to run (https://symbiflow-examples.readthedocs.io/en/latest/building-examples.html):
and this runs Symbiflow but ends with this error:
Maybe things are just temporarily out of sync. Feel free to close this if this is a known/expected issue.
FYI @HackerFoo in case you have any information.
In case it matters, I'm on Ubuntu 20.04.
The text was updated successfully, but these errors were encountered: