pico-examples

I really love the SSD1306 for its educational value. If you've bought a sensor kit for Arduino or ESP32 or Pico or whatever, chances are decent that you already have an SSD1306 lying around. There's so much example code for it. And the datasheet was pretty easy to grok IMO. My first exposure to it was in the pico-examples repo: https://github.com/raspberrypi/pico-examples/tree/master/i2c... There's a few Rust libraries for it, too. And it's supported in Wokwi! https://wokwi.com/projects/425067706980448257

Pico W uses this, right? https://github.com/raspberrypi/pico-examples/blob/master/pic...

Unfortunately the starter example [1] hasn't made it into the public tree (yet ?) [1] https://github.com/raspberrypi/pico-examples/blob/master/dvi...

> My hope is that they'll eventually provide a library of ready-made "soft peripherals" Perhaps they could be more ready-made, but there are loads of official PIO examples that are easy to get started with. https://github.com/raspberrypi/pico-examples/tree/master/pio

The Pico SDK has a plugin based stdio, they give you two implementations: UART and USB CDC, but you can add new ones by implementing a few callback functions. The UART plugin provided with the SDK can be disabled and replaced, the default implementation is very simplistic and will block. The USB CDC version is much faster but may not always be appropriate for your project. I implemented one that uses a buffer and an interrupt to feed the UART in the background, and then I disabled the plugin the Pico SDK provided. I'm not using an RTOS. The SDK example [uart_advanced](https://github.com/raspberrypi/pico-examples/blob/master/uar...) [github.com/raspberrypi] shows how to set up UART interrupts using the Pico SDK

> probably impossible https://github.com/raspberrypi/pico-sdk/ links to a PDF about connecting to the interwebs with a pi pico: "Connecting to the Internet with Raspberry Pi Pico W" https://rptl.io/picow-connect micropython/micropython//ports/rp2/boards/RPI_PICO_W: https://github.com/micropython/micropython/tree/master/ports... micropython/micropython//lib: https://github.com/micropython/micropython/blob/master/lib micropython/micropython//examples/network/http_server_simplistic.py: https://github.com/micropython/micropython/blob/master/examp... micropython/micropython//examples/network/http_server_ssl.py: https://github.com/micropython/micropython/blob/master/examp... raspberrypi/pico-sdk//lib: btstack, cyw43-driver, lwip, mbedtls, tinyusb https://github.com/raspberrypi/pico-sdk/tree/master/lib raspberrypi/pico-examples//pico_w/wif

I don’t know of an off-the-shelf way to implement what you want. There’s a usb-usb converter in QMK which allows you to add QMK features to any keyboard, but QMK does not have Bluetooth support. ZMK is designed for Bluetooth but doesn’t seem to have anything like QMK’s protocol converters (tho I might have looked in the wrong place). You might be able to DIY it with a Raspberry Pi Pico W, by gluing together the picow_bt_example_hid_host_demo and tinyusb_dev_hid_multiple_interface examples from https://github.com/raspberrypi/pico-examples

Chapter 3 of the RP2040 datasheet is all about PIO, but it may not be the best wy to learn: https://datasheets.raspberrypi.com/rp2040/rp2040-datasheet.p... I find the Pico SDK examples useful to learn, but it requires that you already have a good understanding of the instructions and the protocol that it implements. Here's the I2C PIO program, for example: https://github.com/raspberrypi/pico-examples/blob/master/pio....

Oh yes, the PIO is very cool and somewhat unique. The list of examples of things that can be implemented with such a tiny "computer" (9 instructions assembly language, program size maximum of 32 instructions) is quite impressive: https://github.com/raspberrypi/pico-examples/tree/master/pio In fact, the rp2040 examples and SDK docs are very, very good compared to most traditional manufacturer's documentation and by itself makes it a very good value proposition for hobbyists.

Don't forget software costs. Raspberry Pi foundation is known for excellent software and Pico seems to be intended that way too. And that's money well spent, I think. If I'm a hobbyist and am planning on using a grand total of three microcontroller boards, than paying $2 x 3 for "blue pill boards", and then spending hours and hours debugging some obscure problem... that doesn't look like all that great of a deal, compared to paying $5 x 3 and making some use of polished examples and a nice build system: https://github.com/raspberrypi/pico-examples

PIO is definetly interesting stuff. This has its own assembly language (.pio) to program. Custom peripherals can be implemented by using this assembly. Raspberry Pi already provides example programs such as custom I2C, SPI, UART (they are different from the hardware peripherals in the chip), logic analyser, LED controller, and etc[1]. [1]: https://github.com/raspberrypi/pico-examples/tree/master/pio