<hackerfoo>
Getting closer. I was able to generate rr_graph.real.xml. Now I need to fix this: PCF constraint "set_io in[0] V17" from line 2 constraints net in[0] which is not in available netlist: in, out
<hackerfoo>
Hopefully not too much more to go.
<hackerfoo>
V17 isn't one of the pins I selected (W2/3 & V2/3)
_whitelogger has joined #symbiflow
citypw has joined #symbiflow
Bertl is now known as Bertl_zZ
rvalles has quit [Ping timeout: 252 seconds]
citypw has quit [Ping timeout: 268 seconds]
rvalles has joined #symbiflow
rvalles has quit [Ping timeout: 252 seconds]
rvalles has joined #symbiflow
Bertl_zZ is now known as Bertl
citypw has joined #symbiflow
adjtm_ has quit [Ping timeout: 268 seconds]
citypw has quit [Ping timeout: 248 seconds]
Bertl is now known as Bertl_oO
<litghost>
hackerfoo: What target are you running
<litghost>
hackerfoo: The current process is sdc -> ioplace
<tpb>
Title: Avoid failing on empty pip lists (which may occur). by litghost · Pull Request #1017 · SymbiFlow/prjxray · GitHub (at github.com)
<litghost>
mithro: I think I have the last fix in
<hzeller[m]>
What are the premap..v verilog files generated by yosys used for https://github.com/SymbiFlow/symbiflow-arch-defs/blob/master/xc7/yosys/synth.tcl#L7 ? It does not seem to be needed for the remaining vpr process (I comment them out in symbiflow-simple-sample). I suspect this is just used as a debugging output but it is not something needed in a typical workflow ? Or, in other words: can I assume that input verilog
<hzeller[m]>
output eblif is what typically is needed in a workflow invoking yosys ?