claireare there like. no good solutions for viewing logic analyser dumps on macOS? Both pulseview and GTKWave don't seem to run under modern macOS...
✧✦Catherine✦✧@protosphere pulseview isn't really "good" in first place; I'd convert it to a VCD and use Surfer
@whitequark Ohhh that is what I’m looking for. I’ll be getting VCD files anyway since I (will be) using the glasgow analyzer applet for this
@whitequark If you don't mind me asking, how does one actually use the glasgow analyzer applet? The docs state that it's removed, yet it still seems to be there. But I can't get it to produce anything except a 0-byte VCD file
@protosphere the removed thing is the "applet analyzer", a distinct entity from "analyzer applet" (internal vs external logic analyzer)
glasgow run analyzer foo.vcd should do something, if not run with glasgow -vvv and upload log
@whitequark Seems to do nothing (I'm terminating it with Ctrl-C). Log has one error, E: g.hardware.assembly: cannot configure pulls for port A: Vio is off. There's no activity after starting the applet.
@whitequark Yeah ok that makes sense. It was an optional parameter so I imagine it maybe detected automatically voltage if left out (imo this is not clear in the documentation for someone more less technical in electronics like myself)
@protosphere it's also using the legacy applet infrastructure which is slowly falling apart concurrently with us porting applets to V2 infrastructure (which has actual design and is the only one I'm comfortable documenting)
@protosphere (once it's ported to the V2 infrastructure, there will be an error message for this case, I just don't care to spend any more time supporting the legacy infra)
@whitequark That's totally fair
Thanks for all the help! So far the experience of using glasgow has been great overall. It's made this task much less daunting to work on
Thanks for all the help! So far the experience of using glasgow has been great overall. It's made this task much less daunting to work on
@protosphere nice, i'm very happy to hear that!
the underlying core of the analyzer applet is a bit weird (it is one of my first RTL designs dating back to like 2018, i was inexperienced then) so it might have some issues; if you hit overflows quickly, add --pull-ups or --pull-downs
(it compresses the capture data under the hood, which is good for long captures, except if the data is not very compressible like voltage around Vcc/2, it quickly overruns the buffers...)