Closed cr1901 closed 6 years ago
Closing as not a bug: https://gist.github.com/cr1901/2a2a3ef162b2a83238a19b9e0dc832e6#file-top-v-L9
Setting .PIN_TYPE
to 6'd0
solves the bit-width mismatch between arachne-pnr and my code.
I should trigger an error message, not an assertion. I think that makes it a bug.
I have created a MVCE of a single
SB_IO
primitive being instantiated to enable the I/O pullup, and the input being fed to an output pin. Runningbuild_top.bat
produces the following crash on Windows. I am currently unable to test on Linux:I do not know for sure whether:
arachne-pnr
is being fed bad output fromyosys
.yosys
output is fine, butarachne-pnr
chokes.Regardless, I wouldn't have expected a crash; the code from which this sample was derived was known to work in September 2016. I recently upgraded
yosys
from a September 2016 version when I was still using a June 2016 version ofarachne-pnr
; both the June 2016 and current HEAD crash with this output from my current build. So, I expect that some field in theyosys
-emitted BLIF changed between 2016 and now, andarachne-pnr
chokes.Here is some relevant version information:
Note the yosys used is a fork.