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.

Sign up for GitHub

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

Jump to bottom

Yosys-vivado failure on picosoc-spimemio #295

Open
acomodi opened this issue Dec 9, 2020 · 2 comments
Open

Yosys-vivado failure on picosoc-spimemio #295

acomodi opened this issue Dec 9, 2020 · 2 comments

Comments

@acomodi
Copy link
Contributor

acomodi commented Dec 9, 2020

There is a yosys-vivado toolchain failure in one of the test projects, which is causing CI to fail. This is most probably due to the latest yosys package, which has been updated to use upstream yosys:

ERROR: picosoc-spimemio yosys-vivado basys3 test has failed (build type generic, build nr. 000)

ERROR MESSAGE:  [...]
7d04310e132\$lut for cells of type $lut.
Using template $paramod$5678aabaf38638ff6c60e03d865caa8704f4fb95\$lut for cells of type $lut.
Using template $paramod$500825ce3d3051f95f0970672a43b19de1ca0012\$lut for cells of type $lut.
Using template $paramod$3752cc190b504e0d74d40c2d0e5e82c39cb5ff29\$lut for cells of type $lut.
Using template $paramod$21efccf29b21389022231a5ef010f482e0b353f1\$lut for cells of type $lut.
No more expansions possible.

3.48. Executing XILINX_DFFOPT pass (optimize FF control signal usage).
terminate called after throwing an instance of 'std::out_of_range'
  what():  dict::at()
Aborted (core dumped)
picosoc-spimemio.mk:13: recipe for target 'picosoc-spimemio.edif' failed
acomodi added a commit to antmicro/fpga-tool-perf that referenced this issue Dec 9, 2020
@acomodi
WIP: temporary disable picosoc-spimemio for yosys-vivado
5190c5f 
See chipsalliance#295

Signed-off-by: Alessandro Comodi <acomodi@antmicro.com>
@daveshah1
Copy link

If this is happening with unmodified upstream Yosys, please report it as a bug there - this definitely shouldn't be failing this way even if hypothetically there is a problem with the design/flags.

@acomodi
Copy link
Contributor Author

acomodi commented Dec 9, 2020

@daveshah1 Sure, I wanted to keep track of this here, and, before opening an issue upstream I wanted to debug what might be the cause of the failure (maybe is a flags/design issue indeed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@daveshah1 @acomodi