Strongly recommend the last PICO SDK 1.5 firmware build for Bus Pirate 5. SDK 2.0 has caused all kinds of weird issues in the modes using the PIO hardware.
I plan to spend a couple more days messing with SDK 2.0, but next week I’ll have to roll back to SDK 1.5 so we can keep pushing forward on the firmware for 5.
how painful is it to downgrade from 2.0 to 1.5? Can they both coexist?
The main thing is I will probably need to deploy a second build server if I don’t want to spend a day mucking about in the Linux environmental variable and SDK path swamp. I assume it can all work together on one given enough time, but I also know that I can setup a new one in about an hour.
The actual change shouldn’t be painful. I already rolled back any SDK2.0 specific functions because every one I’ve used is super super buggy and caused crashes that were painful to debug. However, the Rp2350 chips are stuck with SDK2.0 because they aren’t supported in SDK1.5.
This should be fixed now, and you can resume using the latest auto builds.