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
Right now it appears that regardless of PIN_TYPE, the CLOCK_ENABLE and {INPUT,OUTPUT}_CLOCK in a pin pair with z=0,1 must match. This is mostly fine for clocks but gets extremely annoying for CLOCK_ENABLE, and worse, the constraint still has to be preserved if you use the pin as a comb input/output.
Nextpnr could take this into account and ignore the nets tied to CLOCK_ENABLE/*_CLOCK if the PIN_TYPE instructs it so.
The text was updated successfully, but these errors were encountered:
Actually, I remember now, it was in the Glasgow RGMII applet. I'd have to change the code a little to create a reproducer but it shouldn't be too hard.
Right now it appears that regardless of PIN_TYPE, the CLOCK_ENABLE and {INPUT,OUTPUT}_CLOCK in a pin pair with z=0,1 must match. This is mostly fine for clocks but gets extremely annoying for CLOCK_ENABLE, and worse, the constraint still has to be preserved if you use the pin as a comb input/output.
Nextpnr could take this into account and ignore the nets tied to CLOCK_ENABLE/*_CLOCK if the PIN_TYPE instructs it so.
The text was updated successfully, but these errors were encountered: