We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using the autotuner of asap7/ibex I get number of failed runs with a similar error:
Failed to find a path between pin and source aps: ( 231 3 3 ) (Idx) / ( 84156 12 ) (coords) ( 235 3 3 ) (Idx) / ( 84204 12 ) (coords) extBBox (xDim, yDim, zDim) = (239, 527, 10) [ERROR DRT-0255] Maze Route cannot find path of net boot_addr_i[18] in worker of routeBox ( 83160 0 ) ( 84226 3780 ). Error: detail_route.tcl, 47 DRT-0255
No error
OR eabc5a77aee337d84051465d8bd75f141d656e02 ORFS b9e0081d0782667066a16f901209b7e89d8c8915
https://drive.google.com/file/d/11L9R9AEmiZKREUNTQkdfAn87KEL8JpSH/view?usp=sharing
[INFO DRT-0195] Start 0th optimization iteration. Completing 10% with 0 violations. elapsed time = 00:00:20, memory = 1888.18 (MB). Completing 20% with 0 violations. elapsed time = 00:00:37, memory = 2846.69 (MB). Failed to find a path between pin and source aps: ( 231 3 3 ) (Idx) / ( 84156 12 ) (coords) ( 235 3 3 ) (Idx) / ( 84204 12 ) (coords) extBBox (xDim, yDim, zDim) = (239, 527, 10) [ERROR DRT-0255] Maze Route cannot find path of net boot_addr_i[18] in worker of routeBox ( 83160 0 ) ( 84226 3780 ). Error: detail_route.tcl, 47 DRT-0255
No response
The text was updated successfully, but these errors were encountered:
67/100 runs had this error
Sorry, something went wrong.
osamahammad21
No branches or pull requests
Describe the bug
When using the autotuner of asap7/ibex I get number of failed runs with a similar error:
Expected Behavior
No error
Environment
To Reproduce
https://drive.google.com/file/d/11L9R9AEmiZKREUNTQkdfAn87KEL8JpSH/view?usp=sharing
Relevant log output
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: