Philip Howard

Using pins >31 requires the new `PIO.gpio_base(N)` method, where valid values are either GPIO0 (for 0-31) or GPIO16 (for 16-47). `sm_config_set_in_pins()` *should* accept >31, as long as the build specifies...

*snip* ``` hardware_pio Added pio_sm_set_pins64(), pio_sm_set_pins_with_mask64() and pio_sm_set_pindirs_with_mask64() to allow setting of >32 pins. Much improved documentation of how GPIO numbers > 32 are handled. Fixed a bug in the...

Most of the PIO I work with is in C and handily avoids the quirks but there are a couple of related issues- setting up PIO pins on RP2350 is...

It would be better to lean into using a virtualenv and install the packages directly with pip rather than using the installer. I wrote some possibly useful virtualenv stuff here:...

Not totally sure there's a way to handle this without hardware support for a slow soft-start ramp up on the DAC. I believe the issue is the amp turning on...

I think the tool silently ignores a lot of things, all errors are trapped and... discarded :grimacing: That needs some... fixing.

I've managed to trap the no-valid-files case early and explode in a somewhat more helpful manner. However this doesn't solve the mixed case- I think the warning output about missing...

Right, disregard the above... I think I've got it bailing sensibly now.

Woof, I guess we can close this now?

🥳