Mark R. Rubin

Trigger commands must be written one per line. Your second example, if entered correctly, should trigger on a falling edge on input PB11. $1.50: trigger 0=1xxxxxxx-1-0 st1 $1.50: trigger 1=0xxxxxxx-0-1...

The `monitor` command is intended as a live display of the digital/analog/serial inputs or for slow-speed data logging. 50kHz is pushing it. You should probably be using the `logic` (analyzer)...

Thanks for the clarification. I'll need to test further, but `monitor` should only miss reporting data changes if the data rate is too fast, not stop completely. You can also...

Feel free to do so.

buck50 does not connect directly to pulseview, so no drivers, baudrate, etc. Instead it saves a VCD file to disk which is then loaded into pulseview. Depending on how buck50.py...

Thanks, @nerdralph . Interesting idea. Let me "meditate" on it. My intended use-case was always multiple channels (thus the "gang" feature), but I can certainly imagine 2 channels at higher...

I come from a software background, so I'll yield to your experience and experiment for myself when I get a chance. I've always read that anything above 1 MHz was...

Thanks, @nerdralph. I'll be interested in hearing what you find out when you get around to it.

How did you choose the value for`nss-time=100μs`? In the`mode=master nss=active` SPI configuration, buck50 lowers PA4/NSS1 at the beginning of a byte transfer, waits `nss-time` to allow the data to be...

You're welcome. Glad you've found it useful. Reviewing the code, it looks like I should remove the `nss-time` parameter and instead check `Spi::Sr::BUSY`. I seem to recall trying something like...