-
Notifications
You must be signed in to change notification settings - Fork 415
Route 3d #2330
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
Route 3d #2330
Conversation
…cess functions to work with it
…signment for custom pinlocations
…cture functionality
…verilog-to-routing into inter_die_communication
…verilog-to-routing into inter_die_communication
…rilog-to-routing into inter_die_communication
…verilog-to-routing into inter_die_communication
…rilog-to-routing into inter_die_communication
…upport 3d rrgraph
…n 3d but should work for 2d arch files
…verilog-to-routing into inter_die_communication
…verilog-to-routing into inter_die_communication
…ayer_offset itself
…verilog-to-routing into inter_die_communication
VPR Command: Problem: |
For S-IV with all IPINs and OPINs connectd to other layers: vtr_flow/arch/multi_die/stratixiv_arch.timing.xml |
@amin1377 I have attached koios architecture files under arch/multi_die. Both OPINS and IPINS: vtr_flow/arch/multi_die/k6FracN10LB_mem20K_complexDSP_customSB_22nm.xml Only OPINS: vtr_flow/arch/multi_die/k6FracN10LB_mem20K_complexDSP_customSB_22nm_OPINs.xml |
…to-routing/vtr-verilog-to-routing into inter_die_communication
Here is the branch result for 2d benchmarks (Titan and VTR) to double check that my changes didn't degrade the QoR for 2d designs. The branch is compared to current master branch. |
@vaughnbetz ready to merge. |
Description
In this PR, I have modified the RRGraph generation to support more than one available die (e.g., 3D FPGA). I have changed the tag in arch file to describe an attribute named "layer_offset". The layer_offset for each physical pin will specify which layer this pin is connected to. Hence, an IPIN/OPIN located at layer 0 can be connected to the upper die with layer_offset=1.
Since we have more than one die available, we want to give the user the ability to specify which die(dice) has global routing resources (wire segment, switch blocks, ..). Hence, a new optional attribute is defined for the tag called "has_routing_resources" and it can hint the RRGraph to build or ignore the routing resource graph for each die.
Related Issue
This PR is entirely dependent on place_3d, shouldn't be merged before the place_3d PR.
Types of changes
Checklist: