home.social

#rpipico — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rpipico, aggregated by home.social.

fetched live
  1. Happy scenes in the #doghouse working on the next #CNC machine project. Having to use windows which feels weird, but whatever the OS its good to get this BTT SKR #Pico board moving motors correctly. #rpipico #grbl #grblHAL

  2. Question for electronics folks: if I make a cheat sheet for the pinouts or popular dev boards, do you prefer separate figures for the Raspberr Pi Pico, Pico W, Pico 2, and Pico 2 W, or one generic one is enough, knowing that the pins are the same on all of them?

    #Electronics #DIY #RaspberryPi #RpiPico

  3. Yesterday, I was battling kernel issues, and thought I had solved them… but 'lo and behold, they're back.

    ```
    [ 501.876271] usb 3-6: new full-speed USB device number 12 using xhci_hcd
    [ 502.009828] usb 3-6: New USB device found, idVendor=1234, idProduct=5678, bcdDevice= 4.03
    [ 502.009836] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 502.009839] usb 3-6: Product: WideSky Hub Test Rig
    [ 502.009841] usb 3-6: Manufacturer: WideSky.Cloud Pty Ltd
    [ 502.009843] usb 3-6: SerialNumber: E663AC91D3A25F30
    [ 502.017519] input: WideSky.Cloud Pty Ltd WideSky Hub Test Rig as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/input/input34
    [ 502.017882] input: WideSky.Cloud Pty Ltd WideSky Hub Test Rig as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.1/input/input35
    [ 502.018877] input: WideSky.Cloud Pty Ltd WideSky Hub Test Rig as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.2/input/input36
    [ 502.019157] input: WideSky.Cloud Pty Ltd WideSky Hub Test Rig as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.3/input/input37
    [ 523.473860] usb 3-6: USB disconnect, device number 12
    [ 523.474020] usbtouchscreen 3-6:1.1: usbtouch_irq - usb_submit_urb failed with result: -19
    [ 523.474033] usbtouchscreen 3-6:1.3: usbtouch_irq - usb_submit_urb failed with result: -19
    [ 523.509076] usbtouchscreen 3-6:1.2: usbtouch_irq - usb_submit_urb failed with result: -19
    ```

    The device is a Raspberry Pi Pico RP2040 and the firmware is based on codeberg.org/sjlongland/modbus -- it works fine on other machines, just not the Ubuntu laptop at work.

    The `usbtouchscreen` messages are a clue… it seems it's interacting and fouling up `cdc-acm`, if I remove it and re-plug, I get this:

    ```
    [ 559.382809] usbcore: deregistering interface driver usbtouchscreen
    [ 563.370959] usb 3-6: USB disconnect, device number 13
    [ 564.699077] usb 3-6: new full-speed USB device number 14 using xhci_hcd
    [ 564.831198] usb 3-6: New USB device found, idVendor=1234, idProduct=5678, bcdDevice= 4.03
    [ 564.831203] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 564.831205] usb 3-6: Product: WideSky Hub Test Rig
    [ 564.831206] usb 3-6: Manufacturer: WideSky.Cloud Pty Ltd
    [ 564.831207] usb 3-6: SerialNumber: E663AC91D3A25F30
    [ 564.839153] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
    [ 564.840965] cdc_acm 3-6:1.2: ttyACM1: USB ACM device
    [ 564.868428] usbcore: registered new interface driver usbtouchscreen
    ```

    So looks like I need to blacklist `usbtouchscreen`. No idea why this is even being loaded, there are 0 touchscreens on this machine, USB or otherwise.

    #Zephyr #Ubuntu #RPIPico #RP2040

  4. Took all of 5 minutes to “clean up” my #SBC set-up. I have downsized the SBC that I currently use. Now I am down to the following:

    1) @PINE64 Rockpro64 which is my mini #Debian file server (black box with stickers)

    2) #MangoPi Pro a D1 #riscv sbc for tinkering (small black box)

    3) #RPipico emulating a 128K Macintosh (grey box)

    4) #OrangePiRV2 (clear box) an 8core K1 riscv sbc also for tinkering.

    All my other sbc are collecting dust in a box until I find a use or they end up in the e-recycling bin.

  5. Not content with this success, I went on to write a pico C++ driver for the lsm6ds3 accelerometer using the pimoroni-i2c library as there did not appear to be any C++ drivers in the wild for this on
    This along with the touch screen C++ driver I converted from lvgl to the pimoroni-pico graphics will be published in my examples once I have fully implemented the driver and written some simple boilerplate examples.

  6. The PicoCalc uLisp Machine is a Clockwork Pi PicoCalc handheld computer that runs uLisp, a Lisp implementation for microcontrollers.

    The Clockwork Pi PicoCalc features an RP2040/2350-based Raspberry Pi Pico or Pi Pico 2 board, and has a nice 320x320 4" colour IPS display and keyboard. uLisp provides a rich environment and tools.

    ulisp.com/show?56ZO

    #ulisp #lisp #rpi #rpipico #rp2040

  7. The moment when the chinese clone is better than original, waveshare RP2040-Zero, it might have less GPIO, but USB-C port is the winner. I have no ideas what was RPI foundation thinking about using micro-usb port in theirs RPI Pico #rpipico #waveshare this will be brain of my next #handwired #keyboard

  8. Well this was fun.

    #rpipico #zxspectrum #breadboard #gamepad #gnu #linux #unix #bash

    Also, never ever send keycode for Enter on no event. Hihihi. Took me while to figure casting sleep on cp code revision.

  9. Unbrick Raspberry pi pico micropython - Restaurar firmware cuando falla código en main

    A veces en nuestro código se provoca una excepción o realizamos alguna acción que rompe la ejecución demasiado pronto para que nos de tiempo a parar e insertar una corrección.

    Os dejo una solución para reflashear por completo y dejar la pico como recién llegada para continuar el desarrollo.

    youtu.be/HOcjp2-kDjY

    #micropython #rpi #pico #rpipico #raspberry #unbrick

  10. Right angle vs vertical connectors! Which is more popular?

    KF141 quick connectors: the right angle version is ahead by 3:1 after a week.

    Pico silkscreen headers: right angle was a last minute decision. First instincts were right: vertical is ahead by a whopping 10:1..

    #buspirate #openhardware #rpipico

  11. RPi Pico is great, but the tiny misaligned pin labels are not. We asked Uncle to silkscreen the Pico pinout on 20p headers when we sent KF141s. We picked the best header out of 10 manufacturers and used a two-part silkscreen process that's extra sharp.

    dirtypcbs.com/store/designer/d

    #rpi #rpipico

  12. When you know what the problem with your hacked up driver (bits of Arduino and espruino code in the mix) is but… #sh1107 on #rpipico

  13. #Preisindex #RPiPico Evalboard (inkl AliExpress Versand):
    4MB 3.03EUR
    16MB 3.37EUR

  14. #Preisindex #RPiPico Evalboard (inkl AliExpress Versand):
    4MB 3.07EUR
    16MB 3.39EUR

  15. my new keyboard emits an “a” character every second - it’ll be a big timesaver! 🤣 #hardware #rpipico and #rust

  16. Hab mir nun n Nullmodem-Kabel mit einem #RPiPico und #TinyUSB gebaut:
    #Arduino Example github.com/adafruit/Adafruit_T leicht modifiziert (Debugmeldungen, tolower/toupper entfernt)

    Warum einfach, wenn's auch kompliziert geht?

  17. Maker community should be excited with this one. No audio support over Bluetooth as per the reporting though (actually had a project in mind for that, ah well, welcome all the same)

    The Raspberry Pi Pico Software Developer Kit version 1.5.0 released with Bluetooth support #RaspberryPiPico « Adafruit Industries – Makers, hackers, artists, designers and engineers!
    blog.adafruit.com/2023/02/14/t

    Github release notes for anyone interested github.com/raspberrypi/pico-sd

    #rpi #raspberryPi #pico #rpipico ico

  18. Modules arrived today. Various resolutions and bit depths. Plan to make the graphics lib code device agnostic. #rpipico #spi #tft

  19. Needed a cross section of display modules to test my RPI PICO GFX LIB against. Cant make it hardware agnostic without some kit. Ordered a variety of interface tech (i2c, spi) bit depth (1bit to 65k) and sizes including a huge 2 inch display!

    github.com/seanbutler/rpi_pico

    #RPIPICO #OLED #microcontroller
    #opensource

  20. Hey @yezzer -- don't forget to try to program the . Lots of easy-to-load libraries supporting sensors, actuators, sophisticated add-on hw, and some fun kits, such as PicoBricks. Unlike other blocks languages, MicroBlocks is LIVE. Blocks in the IDE are kept in sync with blocks on the board. Click any block(s) to immediately activate! ⚡