#rpipico — Public Fediverse posts

Mantendo suas placas IoT vivas mesmo quando travam (#dev #devlog #iot #micropython #raspberrypipico #pipico #rpipico)
https://raccoon.ninja/pt/post/dev/keeping-iot-boards-alive-even-when-they-freeze/

Mantendo suas placas IoT vivas mesmo quando travam (#dev #devlog #iot #micropython #raspberrypipico #pipico #rpipico)
https://raccoon.ninja/pt/post/dev/keeping-iot-boards-alive-even-when-they-freeze/

Mantendo suas placas IoT vivas mesmo quando travam (#dev #devlog #iot #micropython #raspberrypipico #pipico #rpipico)
https://raccoon.ninja/pt/post/dev/keeping-iot-boards-alive-even-when-they-freeze/

Keeping your IoT boards alive even when they freeze (#dev #devlog #iot #micropython #raspberrypipico #pipico #rpipico)
https://raccoon.ninja/post/dev/keeping-iot-boards-alive-even-when-they-freeze/

Keeping your IoT boards alive even when they freeze (#dev #devlog #iot #micropython #raspberrypipico #pipico #rpipico)
https://raccoon.ninja/post/dev/keeping-iot-boards-alive-even-when-they-freeze/

Keeping your IoT boards alive even when they freeze (#dev #devlog #iot #micropython #raspberrypipico #pipico #rpipico)
https://raccoon.ninja/post/dev/keeping-iot-boards-alive-even-when-they-freeze/

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

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

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

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

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

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

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

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

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

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

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 https://codeberg.org/sjlongland/modbus-ina219-bridge -- 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

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 https://codeberg.org/sjlongland/modbus-ina219-bridge -- 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

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 https://codeberg.org/sjlongland/modbus-ina219-bridge -- 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

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 https://codeberg.org/sjlongland/modbus-ina219-bridge -- 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

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 https://codeberg.org/sjlongland/modbus-ina219-bridge -- 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

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.

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.

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.

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.

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 #rpipico
This along with the touch screen C++ driver I converted from lvgl to the pimoroni-pico graphics will be published in my #presto examples once I have fully implemented the driver and written some simple boilerplate examples.
#pimoroni #pico #RaspberryPi

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 #rpipico
This along with the touch screen C++ driver I converted from lvgl to the pimoroni-pico graphics will be published in my #presto examples once I have fully implemented the driver and written some simple boilerplate examples.
#pimoroni #pico #RaspberryPi

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 #rpipico
This along with the touch screen C++ driver I converted from lvgl to the pimoroni-pico graphics will be published in my #presto examples once I have fully implemented the driver and written some simple boilerplate examples.
#pimoroni #pico #RaspberryPi

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 #rpipico
This along with the touch screen C++ driver I converted from lvgl to the pimoroni-pico graphics will be published in my #presto examples once I have fully implemented the driver and written some simple boilerplate examples.
#pimoroni #pico #RaspberryPi

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 #rpipico
This along with the touch screen C++ driver I converted from lvgl to the pimoroni-pico graphics will be published in my #presto examples once I have fully implemented the driver and written some simple boilerplate examples.
#pimoroni #pico #RaspberryPi

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.

http://www.ulisp.com/show?56ZO

#ulisp #lisp #rpi #rpipico #rp2040

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.

http://www.ulisp.com/show?56ZO

#ulisp #lisp #rpi #rpipico #rp2040

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.

http://www.ulisp.com/show?56ZO

#ulisp #lisp #rpi #rpipico #rp2040

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.

http://www.ulisp.com/show?56ZO

#ulisp #lisp #rpi #rpipico #rp2040

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.

http://www.ulisp.com/show?56ZO

#ulisp #lisp #rpi #rpipico #rp2040

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

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

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

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

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

the Raspberry Pi Pico 2 W is available now.
just rare on stock.

https://www.raspberrypi.com/news/raspberry-pi-pico-2-w-on-sale-now/

#rp2350 #rpipico #pico2w

the Raspberry Pi Pico 2 W is available now.
just rare on stock.

https://www.raspberrypi.com/news/raspberry-pi-pico-2-w-on-sale-now/

#rp2350 #rpipico #pico2w

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.

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.

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.

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.

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.

Oh, RPI Pico 2! #rpipico
https://www.raspberrypi.com/news/raspberry-pi-pico-2-our-new-5-microcontroller-board-on-sale-now/

Oh, RPI Pico 2! #rpipico
https://www.raspberrypi.com/news/raspberry-pi-pico-2-our-new-5-microcontroller-board-on-sale-now/

Oh, RPI Pico 2! #rpipico
https://www.raspberrypi.com/news/raspberry-pi-pico-2-our-new-5-microcontroller-board-on-sale-now/

Oh, RPI Pico 2! #rpipico
https://www.raspberrypi.com/news/raspberry-pi-pico-2-our-new-5-microcontroller-board-on-sale-now/

Oh, RPI Pico 2! #rpipico
https://www.raspberrypi.com/news/raspberry-pi-pico-2-our-new-5-microcontroller-board-on-sale-now/

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.

https://youtu.be/HOcjp2-kDjY

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

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.

https://youtu.be/HOcjp2-kDjY

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

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.

https://youtu.be/HOcjp2-kDjY

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

Got an ISO mounted in NEXTSTEP on the NeXTstation with my new BlueSCSI v2 device. Awesome addition to the system.

#NeXT #NEXTSTEP #vintagecomputing #retrocomputing #SCSI #storage #vintagetech #tech #NEXTTIME #SteveJobs #video #UNIX #BlueSCSI #RPi #RPIPico

Got an ISO mounted in NEXTSTEP on the NeXTstation with my new BlueSCSI v2 device. Awesome addition to the system.

#NeXT #NEXTSTEP #vintagecomputing #retrocomputing #SCSI #storage #vintagetech #tech #NEXTTIME #SteveJobs #video #UNIX #BlueSCSI #RPi #RPIPico

Got an ISO mounted in NEXTSTEP on the NeXTstation with my new BlueSCSI v2 device. Awesome addition to the system.

#NeXT #NEXTSTEP #vintagecomputing #retrocomputing #SCSI #storage #vintagetech #tech #NEXTTIME #SteveJobs #video #UNIX #BlueSCSI #RPi #RPIPico

Got an ISO mounted in NEXTSTEP on the NeXTstation with my new BlueSCSI v2 device. Awesome addition to the system.

#NeXT #NEXTSTEP #vintagecomputing #retrocomputing #SCSI #storage #vintagetech #tech #NEXTTIME #SteveJobs #video #UNIX #BlueSCSI #RPi #RPIPico

Got an ISO mounted in NEXTSTEP on the NeXTstation with my new BlueSCSI v2 device. Awesome addition to the system.

#NeXT #NEXTSTEP #vintagecomputing #retrocomputing #SCSI #storage #vintagetech #tech #NEXTTIME #SteveJobs #video #UNIX #BlueSCSI #RPi #RPIPico