clifford changed the topic of #yosys to: Yosys Open SYnthesis Suite: http://www.clifford.at/yosys/ -- Channel Logs: https://irclog.whitequark.org/yosys
daveshah has quit [Ping timeout: 240 seconds]
Degi_ has joined #yosys
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
daveshah has joined #yosys
ktemkin has quit [Ping timeout: 256 seconds]
ktemkin has joined #yosys
mirage335 has quit [Ping timeout: 252 seconds]
mirage335 has joined #yosys
citypw has joined #yosys
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
citypw has quit [Ping timeout: 240 seconds]
citypw has joined #yosys
dys has quit [Ping timeout: 264 seconds]
captain_morgan has quit [Remote host closed the connection]
captain_morgan has joined #yosys
citypw has quit [Remote host closed the connection]
citypw has joined #yosys
N2TOH_ is now known as N2TOH
emeb_mac has quit [Quit: Leaving.]
az0re has quit [Remote host closed the connection]
N2TOH_ has joined #yosys
N2TOH has quit [Ping timeout: 256 seconds]
zkms is now known as __builtin_trap
citypw has quit [Remote host closed the connection]
citypw has joined #yosys
adjtm has quit [Remote host closed the connection]
adjtm has joined #yosys
dys has joined #yosys
nengel has quit [Ping timeout: 240 seconds]
emeb has joined #yosys
elGamal has quit [Ping timeout: 256 seconds]
gtw has quit [Ping timeout: 256 seconds]
citypw has quit [Ping timeout: 240 seconds]
citypw has joined #yosys
citypw has quit [Ping timeout: 240 seconds]
az0re has joined #yosys
N2TOH has joined #yosys
N2TOH_ has quit [Ping timeout: 256 seconds]
az0re has quit [Remote host closed the connection]
elGamal has joined #yosys
elGamal has joined #yosys
elGamal has quit [Read error: Connection reset by peer]
elGamal has joined #yosys
az0re has joined #yosys
gtw has joined #yosys
nengel has joined #yosys
elfGamal has joined #yosys
elGamal has quit [Ping timeout: 260 seconds]
proteusguy has quit [Ping timeout: 265 seconds]
Vinalon has joined #yosys
awygle is now known as awygle_working
<Vinalon> Is it possible to use NextPNR's GUI to highlight the bels, wires, and pips associated with certain cells and nets?
<ZipCPU> Isn't that the point?
<Vinalon> I tried using the 'highlight' right-click menu, but it doesn't seem to highlight anything
<Vinalon> I thought so - I'm trying to get a feel for which cells and nets are using the most LUTs
<ZirconiumX> You don't need nextpnr for that :P
<ZirconiumX> Yosys can generally tell you it
<ZirconiumX> You just tell it not to flatten the design
<ZipCPU> Yosys is faster too
<ZirconiumX> e.g. synth_ice40/synth_ecp5 -noflatten
<ZirconiumX> And then you get a `stat` output for every module
<Vinalon> oh, cool - thanks.
<ZipCPU> Meh ... I'd flatten the design, but only synth that portion of the design I wanted to estimate the usage of
<Vinalon> that's what I tried at first, but it seems like a lot of the logic might get optimized out when it's not actually connected to any inputs/outputs.
proteusguy has joined #yosys
<ZirconiumX> I feel like context matters a lot here
<Vinalon> probably, but I don't want to waste everyone's time with dumb questions; "try using yosys instead" is good enough for me :)
<Vinalon> thanks all
Vinalon has quit [Quit: Leaving]
<ZirconiumX> ...Y'know, we'd never know if your questions were dumb if you left them unasked.
* ZirconiumX sighs
<ZipCPU> Yep
dys has quit [Ping timeout: 264 seconds]
<ZipCPU> I didn't have a good nextpnr design handy, or I would've double checked how to do that there
dys has joined #yosys
awygle_working is now known as awygle
az0re has quit [Remote host closed the connection]