On RP2040/latest firmware:
1-Wire makes a signal, but doesn’t detect the attached sensor. This could be a bug I introduced earlier, could be easy fix.
I2C is messed up. Not in the same way as RP2350, but that defo isn’t 0xff
WOW! look at that. ~38khz clock signals coming out of the data pin in 2WIRE mode. Similar to I2C on RP2350. I’m pretty sure I didn’t cause that.
LED mode similarly messed up to RP2350.
Hum…
We can probably conclude that there is a bug in at least the SDK effecting both rp2040 and rp2350, along with some rp2350 specific bugs as well. Strongly feel is it related to the new PIO assignment function not placing code correctly/blowing out PIO code. It could also be something stupid I did while moving everything to that new function and a standardized pio_config struct for settings.
Next step is to disable everything that uses PIO, and manually assign resources one at a time. Also wonder if this might be useful.
Bus Pirate 5
Strongly recommend the last pre-SDK 2.0 firmware build for Bus Pirate 5.
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.