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
For the time being, CORE-R5.xpr and CORE-R6.xpr should be identical. Yet, CORE-R6.xpr does not close timing (see screenshots), while `CORE-R5.xpr? does.
With this commit 81749ea, we achieve timing closure on R6.
We need to investigate, if CORE-R6.xpr has a bug and/or how it is different from CORE-R5.xpr or why we don't get timing closure.
For the V5.1 release we did not use the bitstream generated by CORE-R6.xpr but copied the bitstream generated by CORE-R5.xpr, because for the time being both platforms are identical when it comes to the C64 core.
The text was updated successfully, but these errors were encountered:
For the time being,
CORE-R5.xpr
andCORE-R6.xpr
should be identical. Yet,CORE-R6.xpr
does not close timing (see screenshots), while `CORE-R5.xpr? does.With this commit 81749ea, we achieve timing closure on R6.
We need to investigate, if
CORE-R6.xpr
has a bug and/or how it is different fromCORE-R5.xpr
or why we don't get timing closure.For the V5.1 release we did not use the bitstream generated by
CORE-R6.xpr
but copied the bitstream generated byCORE-R5.xpr
, because for the time being both platforms are identical when it comes to the C64 core.The text was updated successfully, but these errors were encountered: