| *** tpb has joined #vtr-dev | 00:00 | |
| *** digshadow has joined #vtr-dev | 05:26 | |
| kem_ | mithro: Have you looked at the RR graph generated from the shorted switch regression test architecture: https://github.com/verilog-to-routing/vtr-verilog-to-routing/blob/master/vtr_flow/arch/custom_grid/shorted_flyover_wires.xml ? | 14:32 |
|---|---|---|
| tpb | Title: vtr-verilog-to-routing/shorted_flyover_wires.xml at master · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com) | 14:32 |
| mithro | kem_: I _think_ I have them working | 17:14 |
| mithro | kem_: but it seems to make the design unroutable | 17:14 |
| mithro | benreynwar: Would you happen to be around? I need another small rr_graph tool :-P | 17:35 |
| benreynwar | mithro: Yeah, I can have a look tonight. What is it? | 17:40 |
| mithro | benreynwar: I need to give the tool a starting node and an ending node and want to check there is a pathway between them | 17:40 |
| mithro | benreynwar: I feel like that might already be part of that other tool? | 17:42 |
| benreynwar | mithro: Yep. It just needs exposing with a command line parameter. | 17:43 |
| mithro | benreynwar: Take a look at my ice40-generate branch | 17:45 |
| benreynwar | mithro: I'll take a look after work today. | 17:46 |
| mithro | benreynwar: It also looks like I broke the tool in some way | 17:47 |
| mithro | As it is reporting lots of inaccessible nodes... | 17:48 |
| mithro | benreynwar: Another thing would be a "rr_graph optimizer" -- the idea would be to merge all nodes which are connected together via a "short" | 17:58 |
| mithro | Oh - it's reporting the carry chains :-P | 18:00 |
| kem_ | mithro: Its hard to say what the issue is. We have basic regression tests to check that shorted switches work, so I would lean towards a specification issue. | 19:10 |
| kem_ | mithro: Have you tried pulling up the RR graph in the GUI an clicking on some of the shorted connections? They should be highlighted as a single unit. | 19:10 |
| kem_ | mithro: How many shorted connections are you adding? If its a lot, you might need to be careful to ensure they don't cause large parts of the RR graph to be shorted together (i.e. so only a single logical connection can use those nodes), which would cause routing problems. | 19:13 |
| mithro | kem_: I don't think I have done that | 20:04 |
| mithro | Yeap, been clicking on the wires in GUIs | 20:04 |
| mithro | kem_: need to look up what the colours mean again | 20:26 |
| mithro | benreynwar: Turns out it was *really* easy to make your existing tool work the way I wanted | 20:32 |
| mithro | benreynwar: I just added a filter to the sink/src ids | 20:32 |
| mithro | benreynwar: https://github.com/mithro/symbiflow-arch-defs/commit/b23cbdd35aa1815045c36b06893464672bee2c23 | 20:35 |
| tpb | Title: rr_graph: Allow filtering and output better names. · mithro/symbiflow-arch-defs@b23cbdd · GitHub (at github.com) | 20:35 |
| mithro | Blue: track to block input pin | 20:36 |
| mithro | Redish-pink: block output pin to track | 20:36 |
| mithro | Green: track to track | 20:36 |
| mithro | Purple: block output pin to block input pin (i.e. <directlist> connection) | 20:36 |
| mithro | Gray: Non-configurable edge | 20:36 |
| mithro | kem_: Is there a way to output conflicting paths? | 20:38 |
| kem_ | mithro: One way is to run routing with the GUI and turn the congestion toggle on | 20:46 |
| mithro | kem_: Yeah - I don't quite know how to read that... | 20:46 |
| kem_ | mithro: Basically the colour maps to how overused an RR node is (i.e. 1 means not overused, 3 means occupancy is 3x capacity) | 20:47 |
| mithro | kem_: So, everything is blue... and the numbers all seem to be less than 1 | 20:48 |
| kem_ | mithro: Interesting, I think the congestion heatmap only draws things that have an overuse ratio strictly > 1, so a nearly legal solution with only a couple overused nodes should only highlight a small number of nodes (i.e. channels mostly white) | 20:54 |
| mithro | Looking now | 20:57 |
| mithro | kem_: Oh, I hadn't realized the congestion is per net, if you keep clicking it it cycles through them | 22:56 |
| mithro | kem_: blue == track which can drive this track, red == tracks that can be driven by this track? | 23:55 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!