<hackerfoo>
^ I think this is VPR's way of saying it can't route to an `.output` from the do of a slice l?
<hackerfoo>
Maybe it's because I don't have enough inputs and outputs available in the new ROI.
<hackerfoo>
No, this is before that, when generating the architecture.
<hackerfoo>
I'm not sure what the SLICEL has to do with .output, then.
<hackerfoo>
Maybe the error message is wrong?
<hackerfoo>
Oh, there's a dummy design somewhere being run through VPR.
<hackerfoo>
common/wire.eblif
<hackerfoo>
I'm not sure why it fails, but it works if I remove the single input, output, and wire.
<hackerfoo>
I guess I shouldn't be surprised that things are broken enough that VPR can't route from an input to an output, but I wish it gave some sort of hint as to why.
<mithro>
hackerfoo: you can turn on verbose information on the clustering
<tpb>
Title: If Graphic packages are not installed VTR build fails · Issue #878 · verilog-to-routing/vtr-verilog-to-routing · GitHub (at github.com)
citypw has joined #symbiflow
citypw has quit [Ping timeout: 244 seconds]
Bertl_zZ is now known as Bertl
<litghost>
hackerfoo: That error means that from the ".output" there is no pb_type routing from the blackbox to a tile pin
<litghost>
hackerfoo: Actually try disabling the pin feasibility filter
<litghost>
"FAILED Pin Feasibility Filter"
<litghost>
We've had problems in the past where the pin feasiblity filter either was wrong, or prevent the diagnostic output that explained the failure
citypw has joined #symbiflow
sorear has quit [Ping timeout: 252 seconds]
sorear has joined #symbiflow
citypw has quit [Ping timeout: 248 seconds]
Bertl is now known as Bertl_oO
<hackerfoo>
> No possible routing path from cluster-external source (LB_SOURCE) to cluster-internal sink (LB_SINK accessible via architecture pins: outpad[0].outpad[0]): needed for net 'do' from net pin 'do.out[0]' to net pin 'out:do.outpad[0]'
<hackerfoo>
I don't know where `out` is coming from.
<hackerfoo>
Found this in testarch.echo: interconnect 2 OUTBUF.OUT outpad.outpad