<hackerfoo> Oddly, only the unbonded IO pads are present in the arch.xml.
<hackerfoo> Ah, they are probably being removed since they are in synth_tiles.json.
_whitelogger has joined #symbiflow
<hackerfoo> Here's the latest error:
<hackerfoo> So VPR can't route from the IOB IBUF to a LUT.
_whitelogger has joined #symbiflow
_whitelogger has joined #symbiflow
Bertl is now known as Bertl_zZ
Vonter has quit [Ping timeout: 248 seconds]
Vonter has joined #symbiflow
cherry has joined #symbiflow
cherry has quit [Remote host closed the connection]
Vonter_ has joined #symbiflow
Vonter has quit [Read error: Connection reset by peer]
celadon_ has quit [Quit: ZNC 1.7.4+deb4 - https://znc.in]
celadon has joined #symbiflow
tux3 has quit [Quit: ZNC - https://znc.in]
tux3 has joined #symbiflow
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
Vonter_ has quit [Read error: Connection reset by peer]
Vonter has joined #symbiflow
Bertl_zZ is now known as Bertl
Bertl is now known as Bertl_oO
<litghost> hackerfoo: It would be good to trace the routing path from the IOB and find where the "break" is located
<litghost> xc7/utils/prjxray_find_inode.py is wire string -> inode / connection db and xc7/utils/prjxray_lookup_inode.py provide inode -> wire string / connection db
<sf-slack2> <kgugala> @mithro this commit adds techmap generation for routing muxes https://github.com/SymbiFlow/symbiflow-arch-defs/pull/703/commits/7b6c9f89036582b5e147977954fcf7ecb7307c38
<tpb> Title: mux_gen + v2x: Support generating FASM annotations for muxes. by mithro · Pull Request #703 · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)
<sf-slack2> <kgugala> here is an example of generated tech map https://pastebin.com/niu3vnkm
<litghost> In addition, route_diag tool can attempt to route from any inode to any other inode
<tpb> Title: mux-techmap - Pastebin.com (at pastebin.com)
<litghost> hackerfoo: So make sure VPR can route from the wire after the IOI tile to the inode in question
<litghost> hackerfoo: If that works, then route from the IOB inode to the IOI wire
<litghost> hackerfoo: The problem is either IOB pb_type -> IOI wire, or IOI wire to general fabric
<hackerfoo> litghost: Okay, thanks
<sf-slack2> <mkurc> hackerfoo: Are you importing ILOGIC site along with IOI3 tiles? I'm asking as there is no direct route from IOB to the fabric. You have to route through the ILOGIC site.
<hackerfoo> mkurc: Yes
<sf-slack2> <mkurc> Ok
space_zealot has joined #symbiflow
space_zealot has quit [Ping timeout: 268 seconds]
<sf-slack2> <kejace> I tried replicating this for the arty. I'm now getting a similar error
<sf-slack2> <kejace> And on a second attempt ```PYTHONPATH=../symbiflow-arch-defs/utils python3 ../symbiflow-arch-defs/xc7/utils/prjxray_create_ioplace.py --pcf basys3.pcf --map ../symbiflow-arch-defs/build/xc7/archs/artix7/devices/xc7a50t-arty-roi-virt/synth_tiles_pinmap.csv --blif counter.eblif --out counter_io.place PCF constraint "set_io clk W5" from line 2 constraints pad W5 which is not in available pad map: A9 C2 D10 E3 GND T10 VCC
<sf-slack2> Makefile:85: recipe for target 'counter_io.place' failed make: *** [counter_io.place] Error 1 rm counter_io.place```
<sf-slack2> <kejace> It is clear that this is from me attempting to use the `basys3.pcf`
<sf-slack2> <kejace> Is the solution to this to create an accompanying `arty.pcf`?
<sf-slack2> <kejace>
<litghost> Ya
<tpb> Title: symbiflow-arch-defs/arty.pcf at master · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)
<mithro> FYI - I'm at the hardware hacking village at CCCamp19 right now!
<tpb> Title: VTR cannot handle clustering of multiple atoms of the same type · Issue #250 · SymbiFlow/vtr-verilog-to-routing · GitHub (at github.com)
<sf-slack2> <kgugala> @mithro I updated the #250 issue on github
<sf-slack2> <kejace> @litghost thanks, I got it to compile and build this way and although all of the LEDs light up and they don't blink, I think that I can work on a ClaSH example from here on
<litghost> kejace: You might want to start with a sanity check example, e.g. buttons (tie sw[0] to led[0], etc)
<litghost> kejace: I've mostly been testing on basys3 because it has more LED's and buttons, so it possible that something is wrong with the arty flow
<litghost> kejace: But in theory it should work
<sf-slack2> <kejace> Got it, I'll try to make a complete `.pcf` for the arty. I'll model it after this: https://github.com/Digilent/vivado-boards/blob/master/new/board_files/arty-a7-35/E.0/part0_pins.xml
<tpb> Title: vivado-boards/part0_pins.xml at master · Digilent/vivado-boards · GitHub (at github.com)
<litghost> kejace: I would start with just the 4 switches and 4 LEDs, and go from there. The ROI harness in use on the Arty is fairly limited
<mithro> kejace: Are you at CCCamp19?
<sf-slack2> <kejace> Hehe, I wish, I just heard about it now. I'm in NYC
<hackerfoo> [dusty@hank:~/src/symbiflow-arch-defs/build/xc7/archs/artix7/devices]$ python3 ${SF_ROOT}/xc7/utils/prjxray_lookup_inode.py --rrgraph_node_map rr_graph_xc7a50t-basys3-x1y0_test.rr_graph.real.xml.node_map.pickle --connection_database xc7a50t-basys3-x1y0-roi-virt/channels.db --inode 247988
<hackerfoo> Traceback (most recent call last):
<hackerfoo> ...(truncated)
<hackerfoo> litghost: Also for the other key, so neither RR node is in the map.
<litghost> hackerfoo: The map only has IPIN/CHANX/CHANY/OPIN
<litghost> hackerfoo: Not SINK/SOURCE
<litghost> hackerfoo: And the error prints SINK/SOURCE
<hackerfoo> Can I look those up somewhere?
<litghost> hackerfoo: You can grep the rrgraph to walk from SINK to an IPIN (and SOURCE to OPIN)
<hackerfoo> Okay
<litghost> hackerfoo: The rrgraph by default has no whitespace, I use "xmllint --format in.xml > out.xml" to aid grepping
<hackerfoo> Thanks. I was trying to find a way to do something like that.
<sf-slack2> <kejace> I'm navigating the Makefile to understand why the pinmap is so small ```web-scale ➜ symbiflow-simple-sample git:(master) ✗ cat ../symbiflow-arch-defs/build/xc7/archs/artix7/devices/xc7a50t-arty-roi-virt/synth_tiles_pinmap.csv name,x,y,z,is_clock,is_input,is_output E3,42,26,0,1,1,0 C2,79,24,0,0,1,0 A9,9,49,0,0,1,0 T10,9,5,0,0,0,1 D10,9,3,0,0,0,1 VCC,22,25,0,0,1,1 GND,35,26,0,0,1,1```
<sf-slack2> <kejace> For example, they correspond to the following from (https://github.com/Digilent/vivado-boards/blob/master/new/board_files/arty-a7-35/E.0/part0_pins.xml) ``` <pin index="0" name ="clk" iostandard="LVCMOS33" loc="E3"/> <pin index="41" name ="reset" iostandard="LVCMOS33" loc="C2"/> <pin index="94" name ="usb_uart_rxd" iostandard="LVCMOS33" loc="A9"/> <pin index="95" name ="usb_uart_txd" iostandard="LVCMOS33" loc="D10"/>
<sf-slack2> <pin index="30" name ="led_4bits_tri_o_3" iostandard="LVCMOS33" loc="T10"/>```
<tpb> Title: vivado-boards/part0_pins.xml at master · Digilent/vivado-boards · GitHub (at github.com)
<sf-slack2> <kejace> Let's say I wanted to add `<pin index="31" name ="push_buttons_4bits_tri_i_0" iostandard="LVCMOS33" loc="D9"/>`
<sf-slack2> <kejace> What file should I edit?
<sf-slack2> <kejace> I guess this relates to `hackerfoo`'s comment above ```Oddly, only the unbonded IO pads are present in the arch.xml. hackerfoo (IRC)APP [8:54 PM] Ah, they are probably being removed since they are in synth_tiles.json.```
<hackerfoo> kejace: No, I'm working on something else. Maybe look at this: https://github.com/SymbiFlow/prjxray/blob/master/minitests/roi_harness/README.md
<tpb> Title: prjxray/README.md at master · SymbiFlow/prjxray · GitHub (at github.com)
<hackerfoo> I'm working on breaking out of the ROI, but you will need to create a new harness if you want to access more pins.
<sf-slack2> <kejace> Ok, thanks, this is helpful
_whitelogger has joined #symbiflow
_whitelogger_ has joined #symbiflow
_whitelogger_ has joined #symbiflow
_whitelogger__ has joined #symbiflow
_whitelogger__ has joined #symbiflow
_whitelogger__ has joined #symbiflow
_whitelogger___ has joined #symbiflow
_whitelogger___ has joined #symbiflow
_whitelogger___ has joined #symbiflow
_whitelogger___ has joined #symbiflow
<tpb> Title: find-rr-node: use xmlstarlet to look for rr_graph node information · HackerFoo/hackerfoo-go-functions@e338337 · GitHub (at github.com)
<tpb> Title: find-rr-node: use xmlstarlet to look for rr_graph node information · HackerFoo/hackerfoo-go-functions@e338337 · GitHub (at github.com)
<tpb> Title: find-rr-node: use xmlstarlet to look for rr_graph node information · HackerFoo/hackerfoo-go-functions@e338337 · GitHub (at github.com)
<tpb> Title: find-rr-node: use xmlstarlet to look for rr_graph node information · HackerFoo/hackerfoo-go-functions@e338337 · GitHub (at github.com)
<hackerfoo> It uses xmlstarlet to dump the nodes and edges in the rr_graph matching an id
<hackerfoo> It uses xmlstarlet to dump the nodes and edges in the rr_graph matching an id
<hackerfoo> It uses xmlstarlet to dump the nodes and edges in the rr_graph matching an id
<hackerfoo> It uses xmlstarlet to dump the nodes and edges in the rr_graph matching an id
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger has joined #symbiflow
space_zealot has quit [Ping timeout: 264 seconds]
_whitelogger has joined #symbiflow
bjorkintosh has quit [Ping timeout: 250 seconds]
tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow
space_zealot has quit [Ping timeout: 264 seconds]