clifford changed the topic of #yosys to: Yosys Open SYnthesis Suite: http://www.clifford.at/yosys/ -- Channel Logs: https://irclog.whitequark.org/yosys
klotz has quit [Quit: klotz]
citypw has joined #yosys
s_frit has quit [Ping timeout: 268 seconds]
rohitksingh has joined #yosys
show1 has quit [Ping timeout: 268 seconds]
rohitksingh has quit [Ping timeout: 248 seconds]
blackbit has quit [Excess Flood]
blackbit has joined #yosys
show1 has joined #yosys
ZipCPU|Laptop has quit [Ping timeout: 268 seconds]
jakobwenzel has joined #yosys
dys has quit [Ping timeout: 265 seconds]
dys has joined #yosys
fsasm has joined #yosys
m4ssi has joined #yosys
_whitelogger has joined #yosys
_whitelogger has joined #yosys
ZipCPU|Laptop has joined #yosys
vidbina_ has joined #yosys
dh73 has joined #yosys
mjoldfield has quit [Read error: Connection reset by peer]
mjoldfie_ has joined #yosys
X-Scale has quit [Ping timeout: 265 seconds]
X-Scale` has joined #yosys
X-Scale` is now known as X-Scale
mjoldfie_ has quit [Read error: Connection reset by peer]
mjoldfield has joined #yosys
rohitksingh has joined #yosys
vidbina_ has quit [Ping timeout: 248 seconds]
vidbina_ has joined #yosys
<somlo> daveshah: for building prjtrellis on fedora rawhide (with python 3.9): https://pastebin.com/Ea8DHdRA
<tpb> Title: [Diff] diff --git a/libtrellis/CMakeLists.txt b/libtrellis/CMakeLists.txt index d34d2e - Pastebin.com (at pastebin.com)
<somlo> would rather I did a PR, or is this good enough? :)
<daveshah> somlo: done, thanks
<daveshah> btw, I wonder if Greg's recent change to the LiteX DRAM init might also fix the TrellisBoard issues you had at 55MHz?
<somlo> daveshah: I just finished building an up-to-date LiteX+Rocket bitstream for the trellis
<somlo> passed memtest on the first try when I pushed it to the board, and also after a few (5-ish) reset-switch pushes, and 3-4 subsequent reprogrammings with openocd
<somlo> so I think we may be on to something :)
<somlo> and it's at 60MHz, but at least this bitstream build feels solid
<daveshah> Very good
<somlo> maybe I should build it again and re-test a few times, not sure how specific to each p&r run this stuff is...
<somlo> I was going to refresh my toolchain (yosys/trellis/nextpnr), so I'll see what happens once I build the bitstream with the latest new hotness
rohitksingh has quit [Ping timeout: 245 seconds]
citypw has quit [Ping timeout: 260 seconds]
emeb has joined #yosys
<somlo> daveshah: rebuilt the bitstream (same sources, same toolchain), and it failed twice (out of ten attempts) when pushing via openocd, and worked each time (about another ten attempts) when hitting the reset switch
<somlo> so I'd say this is definitely better than before
<daveshah> Interesting, thanks for testing
cr1901_modern has quit [Read error: Connection reset by peer]
rohitksingh has joined #yosys
<somlo> daveshah: I'll have another data point after I rebuild all toolchain components from their latest github snapshots
<somlo> (not that I expect the litex/trellisboard memtest thing to be affected, but still :)
fsasm has quit [Ping timeout: 272 seconds]
rohitksingh has quit [Ping timeout: 260 seconds]
rohitksingh has joined #yosys
vidbina_ has quit [Ping timeout: 260 seconds]
m4ssi has quit [Remote host closed the connection]
<somlo> I was building yosys #de6006f (freshest as of a few hours ago), and I got a core dump while trying to run "tests/various/bug1531.ys"
<somlo> any chance this is just my not-so-fresh (mid-2019) version of abc?
fsasm has joined #yosys
rohitksingh has quit [Ping timeout: 268 seconds]
rohitksingh has joined #yosys
dys has quit [Ping timeout: 248 seconds]
GenTooMan has quit [Remote host closed the connection]
GenTooMan has joined #yosys
<ZirconiumX> somlo: What's your ABC version?
bitmapper has joined #yosys
<somlo> ZirconiumX: git 02393a2 (cca. Dec. 17, 2019) as packaged by Fedora
<somlo> now trying with 8eb6aed (today's latest), on the off chance something relevant (that would affect the latest yosys) changed since then
<ZirconiumX> Do you build Yosys from source?
_whitelogger has joined #yosys
<somlo> worked great for the last year or two I've been doing it (I build my own RPMs with mock, to get a fresh yosys, and it didn't seem to mind the external abc thing before :)
<ZirconiumX> I know the version of ABC vendored with Yosys got updated recently-ish to fix a bug with ABC9 &mfs
<somlo> but I'm assuming every once in a while I'll hit a spot where Fedora's packaged ABC is out of date wrt latest yosys github :)
<somlo> so I've been wondering if now's one of those...
<tpb> Title: Bump ABCREV for upstream fix · YosysHQ/yosys@9005bb9 · GitHub (at github.com)
<somlo> oh, ok, so I should be able to figure out what abc git hash that was, and rebuild *that* as an RPM
<ZirconiumX> That was slightly over two weeks
<ZirconiumX> That would work
<somlo> oh, cool, then I think we solved the mystery -- thanks!
<somlo> once I try this out and verify that it works, I should probably file a bug in Fedora to have them bump their upstream package as well...
<somlo> s/upstream/official-repo/ (upstream is too overloaded a term to work in this context :)
<ZirconiumX> I think this is the commit with the fix in
<somlo> awesome, thanks again!
<ZirconiumX> It seems ABC still has some bugs relevant to Yosys, but oh well
Jybz has joined #yosys
rohitksingh has quit [Ping timeout: 272 seconds]
ZipCPU|Laptop has quit [Ping timeout: 240 seconds]
rohitksingh has joined #yosys
<somlo> ZirconiumX: tests/various/bug1531.ys coredumps even with the latest abc (8eb6aed)
<somlo> so I'm thinking it's *not* the abc version that's causing it, at this point
<ZirconiumX> somlo: I can't reproduce it
rohitksingh has quit [Ping timeout: 265 seconds]
<somlo> is yosys vendoring any other dependency besides abc?
<ZirconiumX> JSON11 I think
<ZirconiumX> Shouldn't be relevant here
<somlo> my goal (besides having a working up-to-date yosys for my own use) is to be ready to package it for Fedora whenever the next version bump happens (I co-maintain it there)
<somlo> so just building it for myself as a "one-off" will only accomplish goal #1 :)
<somlo> maybe if I bisect it and figure out what yosys commit went from "passes tests" to "bombs this one test" in my own fedora/mock build environment will somehow illuminate just what else about fedora/mock is "wrong" as far as yosys is concerned... :)
<somlo> that at least gives me something potentially productive to do, that doesn't require thinking too hard :D
rohitksingh has joined #yosys
rohitksingh has quit [Ping timeout: 260 seconds]
Jybz has quit [Quit: Konversation terminated!]
rohitksingh has joined #yosys
fsasm has quit [Ping timeout: 265 seconds]
rohitksingh has quit [Ping timeout: 265 seconds]
X-Scale has quit [Ping timeout: 240 seconds]
X-Scale has joined #yosys
cr1901_modern has joined #yosys
X-Scale has quit [Quit: HydraIRC -> http://www.hydrairc.com <- Like it? Visit #hydrairc on EFNet]
dh73 has quit [Quit: Leaving.]
bitmapper has quit [Read error: Connection reset by peer]
bitmapper has joined #yosys
bitmapper has quit [Remote host closed the connection]
rohitksingh has joined #yosys
klotz has joined #yosys
rohitksingh has quit [Ping timeout: 260 seconds]
tpb has quit [Remote host closed the connection]
tpb has joined #yosys