EnvOpenPico VS mechware

I do like the pico and I actually like it enough to design my own mimick https://github.com/Envious-Data/EnvOpenPico which I intend to have a JST connector or a type-c connector instead of type-b so it can be used more easily within keyboards.

I do it for my keyboard firmware project, it's designed to compile up for Arduino (well, not their IDE, but VS with PlatformIO but it's much of a muchness) https://github.com/dairequinlan/mechware

code here https://github.com/dairequinlan/mechware/blob/main/src/input/MatrixInput.cpp That's dual use code, few #define chunks there for Ardiuno (Teensy) and Pico, but basically (using the more common Arduino syntax) ...

Plan is to add the BLE functionality as another pluggable module to my own firmware https://github.com/dairequinlan/mechware

Indeed. It makes for a neat µC for a keyboard, all that GPIO :-D OP are you planning a complete build ? This might be useful it's a complete pluggable and configurable firmware for PICO based keyboards. Dual compiles to Teensy/Arduino so there are a bunch of conditional blocks but it's fairly straightforward otherwise.

it's not an actual pro micro though, right ? It's a RP2040 board like the Pi Pico. I didn't know that that was even supported by QMK yet (if that's what you're trying to use). Coincidentally I just started using as a daily driver a custom split board I put together, which has a Pi PICO in either half, talking I2C to one another. Completely custom firmware though, source is here: https://github.com/dairequinlan/mechware/tree/pico