-
Notifications
You must be signed in to change notification settings - Fork 44
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
terminate called after throwing an instance of 'std::out_of_range' #44
Comments
I have the same issue.
The design is non-trivial, around 10k LUTs + BRAMs + DSPs. |
The code is weird. |
Experiment : I added a However I get a crash later in mapping LUTRAM-related cells : |
To track progress/discussions, I opened the pull request to fix this for nextpnr-himbaechel: |
When running nextpnr-xilinx targeting a basys3 board like so:
nextpnr-xilinx --chipdb ../xc7a35t.bin --xdc ../basys3_nextpnr.xdc --json pong.json --write pong.routed.json --fasm pong.fasm --log nextpnr.log
I get this error:
terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 2) >= this->size() (which is 0)
This seems like the same thing that is seen in this issue, but I'm not sure how to locate a stack trace and figure out what's going on.
My constraints file (basys3_nextpnr.xdc) is here
The text was updated successfully, but these errors were encountered: