You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the resulting json file seems to not include information on port bounds for [9:2], which makes it impossible for nextpnr to resolve indexing of d in the .pcf input, e.g.,
set_io d[9] B5
The text was updated successfully, but these errors were encountered:
I'd suggest the attached patch. Not sure if the start_offset attribute fits best on "ports" or "netnames", or what the difference is. And maybe it should be omitted in the common case that it's zero.
After this patch, the section of the json output looks like
This is related to issue YosysHQ/nextpnr#206. Consider input file
When synthesized using
the resulting json file seems to not include information on port bounds for [9:2], which makes it impossible for nextpnr to resolve indexing of d in the .pcf input, e.g.,
The text was updated successfully, but these errors were encountered: