-
Notifications
You must be signed in to change notification settings - Fork 243
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.
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
MachXO2/XO3/XO3D timing data use #1222
Conversation
Updated trellis, looks all fine after merge |
machxo2/arch.cc
Outdated
|
||
int dx = abs(src_loc.first - dst_loc.first), dy = abs(src_loc.second - dst_loc.second); | ||
|
||
return (120 - 22 * device_speed) * |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you have more trouble routing with this PR, it might be worth just trying increasing the 120 and seeing what happens - as xo2 is slower than ecp5, the delay estimates and predictions may well need to be higher too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added higher value, but also made sure that we always use actual speed, so speed 5 is same for XO3 (where only 5 and 6 are available) and for XO2 ( where we have all speeds from 1 to 6)
require YosysHQ/prjtrellis#234 and YosysHQ/prjtrellis-db#14