proteusguy has quit [Ping timeout: 265 seconds]
_whitelogger has joined #yosys
proteusguy has joined #yosys
proteusguy has quit [Ping timeout: 268 seconds]
proteusguy has joined #yosys
craigo has joined #yosys
PyroPeter has quit [Ping timeout: 246 seconds]
PyroPeter has joined #yosys
attie has joined #yosys
attie has quit [Ping timeout: 276 seconds]
jakobwenzel has quit [Ping timeout: 240 seconds]
Jybz has joined #yosys
kraiskil has joined #yosys
Jybz has quit [Quit: Konversation terminated!]
emeb_mac has quit [Quit: Leaving.]
jakobwenzel has joined #yosys
rohitksingh has joined #yosys
dys has joined #yosys
attie has joined #yosys
jakobwenzel has quit [Ping timeout: 240 seconds]
jakobwenzel has joined #yosys
attie has quit [Ping timeout: 246 seconds]
pie_ has quit [Ping timeout: 240 seconds]
pie_ has joined #yosys
vidbina has joined #yosys
kraiskil has quit [Ping timeout: 240 seconds]
fsasm has joined #yosys
vidbina has quit [Ping timeout: 265 seconds]
proteusguy has quit [Quit: Leaving]
proteusguy has joined #yosys
proteus-guy has joined #yosys
proteus-guy has quit [Excess Flood]
proteusguy has quit [Excess Flood]
proteusguy has joined #yosys
jryans has quit [Remote host closed the connection]
nrossi has quit [Remote host closed the connection]
fevv8[m] has quit [Read error: Connection reset by peer]
pepijndevos[m] has quit [Write error: Connection reset by peer]
pepijndevos[m] has joined #yosys
attie has joined #yosys
kraiskil has joined #yosys
nrossi has joined #yosys
jryans has joined #yosys
fevv8[m] has joined #yosys
dys has quit [Ping timeout: 276 seconds]
citypw has joined #yosys
<
tnt>
Does yosys have an option to just error out when a latch is inferred ?
<
tnt>
that's like 99.9% of the time an error in a fpga design ...
<
pepijndevos>
tnt select -assert-none t:$latch maybe?
<
whitequark>
there's read_verilog -nolatches
attie has quit [Ping timeout: 252 seconds]
<
whitequark>
which would result in a 'x
<
tnt>
Right, but that doesn't stop the build. I really just want it to crash.
<
tnt>
pepijndevos: I'll give that a shot.
<
pepijndevos>
When yosys tells me "Trying to prove $equiv for \gnt_1: failed.", does that mean it found an error, or just that it could not prove it?
<
pepijndevos>
And... any hints on finding the cause for this?
<
pepijndevos>
ERROR: Technology map yielded processes -> this is not supported (use -autoproc to run 'proc' automatically).
<
pepijndevos>
I tried to whitebox and flatten the post-synthesis result
<
pepijndevos>
It seems flatten doesn't even have an -autoproc option
attie has joined #yosys
<
pepijndevos>
I have no clue what is going on anymore. I think my simulation flip-flop models are subtly broken, but no clue what's going on
<
mwk>
tnt: it's going to be called $dlatch, not $latch
<
mwk>
and you need that assert after the proc pass, but before synthesis
<
mwk>
so it's rather unwieldy
X-Scale has quit [Ping timeout: 240 seconds]
X-Scale has joined #yosys
<
whitequark>
pepijndevos: I'm not sure if equiv works for latches, actually
<
whitequark>
wait, no, thread collision
attie has quit [Ping timeout: 240 seconds]
wifasoi has joined #yosys
attie has joined #yosys
emeb has joined #yosys
wifasoi has quit [Ping timeout: 240 seconds]
attie has quit [Ping timeout: 268 seconds]
citypw has quit [Ping timeout: 276 seconds]
attie has joined #yosys
attie has quit [Ping timeout: 240 seconds]
attie has joined #yosys
attie has quit [Ping timeout: 246 seconds]
Thorn has quit [Ping timeout: 268 seconds]
fsasm has quit [Ping timeout: 265 seconds]
Jybz has joined #yosys
rohitksingh has quit [Ping timeout: 264 seconds]
Thorn has joined #yosys
craigo has quit [Ping timeout: 240 seconds]
Jybz has quit [Quit: Konversation terminated!]
emeb_mac has joined #yosys
rombik_su has joined #yosys
vidbina has joined #yosys
kraiskil has quit [Ping timeout: 246 seconds]
rombik_su has quit [Read error: Connection reset by peer]
kraiskil has joined #yosys
kraiskil has quit [Read error: Connection reset by peer]
<
janrinze>
when building nextpnr without gui we don't need the huge chipdb binaries?
<
ZirconiumX>
janrinze: You still do
<
ZirconiumX>
Because the huge chipdb binaries contain all the routing information nextpnr needs
<
janrinze>
hmm. strange. I just built it now but the database files are nowhere to be found. Perhaps different names now?
<
daveshah>
That's because they are linked into the binary
tpb has quit [Remote host closed the connection]
tpb has joined #yosys