Skip to content
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

Merged
merged 13 commits into from
Oct 2, 2023
Merged

MachXO2/XO3/XO3D timing data use #1222

merged 13 commits into from
Oct 2, 2023

Conversation

mmicko
Copy link
Member

@mmicko mmicko commented Sep 28, 2023

@mmicko mmicko requested a review from gatecat September 28, 2023 08:15
@mmicko
Copy link
Member Author

mmicko commented Sep 28, 2023

Updated trellis, looks all fine after merge

machxo2/arch.cc Outdated Show resolved Hide resolved
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) *
Copy link
Member

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

Copy link
Member Author

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)

@gatecat gatecat merged commit 95e7598 into master Oct 2, 2023
16 checks passed
@gatecat gatecat deleted the xo3_timing branch October 2, 2023 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants