Raspberry Pi Pico W plant/flower watering system is coming out nicely. Those Wago connectors are awesome.
🔥 Top 6 Raspberry Pi eBooks for $20
https://ebokify.com/top-6-Raspberry-pi-ebooks
#raspberrypi4 #RaspberryPi #raspberrypipc #picow #Raspberrypipico
Raspberry Pi Pico W - Wie installier ich einen Webserver mit Webseite?
Wie steuere ich ein Neopixel Rundlicht mit Raspberry Pico (w)?
Wie messe ich die Temperatur mit einem Pico (W) ? (Raspberry Pi)
Finished building my new hardwired split mechanical keyboard this weekend! #3dprinted based on my own design, spray painted and powered by a pair of Raspberry Pi Pico W’s. Of course, it’s running my fave #keyboard firmware #KMK! Sadly #CircuitPython doesn’t yet support BLE on the PicoW so it’s not wireless yet, but I’m just counting down the days!
(more details in the image alt text!)
#olkb #splitkeyboard #ergokeyboard #mechanicalkeyboard #pipico #picow #raspberrypi #handwiredkeyboard
#RunCPM v6.7
with #RP2040 / #RP2350 Core v4.5.4
for #Pico / #PicoW and #Pico2
as Source and .#UF2 Binary at https://github.com/guidol70/RunCPM_RPi_Pico/raw/refs/heads/main/v6_7/GL20250601_Binary_Source_RunCPM_v6_7.zip
テスト用のコードでBLEキーボードから文字を拾うことができるようになった!!
#picow
#picow にBLEキーボードがあとちょっとでつながるんだけれど、セキュア接続の壁に阻まれている。色々やっているが sm_require_paring()がどのパラメータの組み合わせでもstatus=8で失敗してしまう＿ﾉ乙(､ﾝ､)_
Right, current status with all my mucking about with #Rust on #RaspberryPi #PicoW: https://yvan.seth.id.au/rusty-pico-w-co2-ppm-sensor.html
With all the hard work done by embassy, picoserve, and libscd — I can display some sensor data on a web page served by the PicoW... this has taken me at least 5 days. 😅
It's a steeper learning curve than I expected!
A bunch more work to do, but right now I really need refresh my Python knowledge. As ever it's hard to know what things to focus on in my limited time... I've got it boiled down at present to refreshing myself on Python and C++ whilst learning some Rust... with the goal of hopefully being able to prove my employability.
Hurrah... my #Rust based #PicoW SCD40 CO2 sensor thing is working. Had a few gnarly problems, have some definite concurrency issues going on I think, I need to dig deeper into how the whole async/mutex situation in Rust/embassy works. But we were also self-DoS-ing as the sample HTTP code I started with had keepalives on, which just doesn't make any sense for this use-case. The moment I added the JS stuff it broke, turn off the keepalives: no problems!
So now I have a page served by the Pico which has the CO2 PPM, temp, and humidity being updated every couple of seconds.
This forms a base for adding further/different sensors and expanding on that, learning as I go, as always. Want to get the built in RTC working, and timestamp results, and store in flash with a bulk-get capability.
And on the topic of flash, need to work out persistent configuration too.
Fairly happy with that at day ~5 of using Rust for the first time.
FUCKING A!
I have a #Rust programme on my #RaspberryPi #PicoW that reads data (an u16) from a sensor and you can then get that data from a web request. HUGE ACHIEVEMENT.
It has taken me like… a large chunk of three days… To get to this point from having code that reads the sensor and serves web requests. 😂 I feel like a moron. But hey, I've only been coding Rust for ~5 days. Probably taking the hard path by going straight into embedded with no::std…
It has taken so many attempts to get to grips with scopes, mutables, Rust's bloody intense syntax, etc, etc… but in the end I've worked out a way to pass a u16 to both spawned workers via some sort of a Mutex. I think I might have an extra level of indirection I don't need… but fuck it, I'll take that I can do this at all as a win.
Now I can take it outside (i.e. not USB-tethered) and see what it reads as an outdoor CO2 PPM measurement.
(I could have had this working in C++ in… minutes, but no, I'm a masochist.)
RIGHT. Fucksake! Arghhh...
I have a solution to this, I do not like my solution to this, but it is a solution...
I reverted my project to use embassy from GitHub again.
I have then grabbed picoserve from GitHub and I have edited the relevant Cargo.toml to use the embassy packages from GitHub.
An in my project Cargo.toml I have referenced my downloaded and modified picoserve instead of using Crates.io... because no matter what I try I cannot make this work using Crates.io packages.
I have now successfully compiled the project modified to use picoserve, loaded it onto the #PicoW, and it runs and serves a "Hello World" via HTTP.
So, another #Rust #embassy #PicoW question.
I started out with embassy examples and had a working thing that compiled and ran on a Pico W.
But then I wanted to use picoserve and this ran me into some dumb looking dependency problems.
I fixed that by following advice to remove the git entries from my Cargo.toml.
However I then have a linker error, one that can be fixed by removing build.rs - but then I get a binary that doesn't work on the Pico W: "entry point is not in mapped part of file"
I think that this is because build.rs was adding these linker arguments: -C link-arg=--nmagic -C link-arg=-Tlink.x -C link-arg=-Tlink-rp.x.
Any one of these being there causes the linker error. I assume something is missing from what needs to be linked in, thus the "undefined symbol" errors. But WHY is this different with the only difference being getting the same versions of packages from git vs crates?!
Edit: hacked a solution, see down-thread
Today I successfully got #Rust code working for a #RaspberryPi #PicoW board! Not bad. All credit goes to the toolchains and projects... my efforts here are purely exploratory / discovery. My current status is I got some Pico / Pico W sample code working and then merged some samples together to form a foundation I'll build more code on top of. The merged code achieves:
The real TL;DR is: The embassy project seems to be the best starting point for Rust on a Pico W. (Not a Pico 2, this is an older RP2040 board.)
The long version is: https://yvan.seth.id.au/rusty-pico-w.html
IoT Pico W TLS Client based on the pico_examples tls_client example by the Raspberry PI foundation. #picow #raspberrypi #iot #cybersecurity #tls #embedded https://github.com/mytechnotalent/iptc
Video of the Badger up and running showing multiple sensors and controlling smart home devices via its buttons!
https://www.youtube.com/watch?v=r-DjXnoWFrA
#esphome #homeassistant #badger #pimoroni #pipico #picow #raspberrypi #maker #homeautomation
Exciting! I have my Pimoroni Badger 2040W working in ESPHome including the buttons and display! You can see the code here:
#esphome #homeassistant #badger #pimoroni #pipico #picow #raspberrypi #maker #homeautomation
I've hacked together a CircuitPython library to UART boot the RP2350. The two bin files it's uploading just cycle through the LEDs in different directions.
I still have no RUN pin so I'm using one of my USB Power Switches to power cycle the board.
#CircuitPython #RP2350 #RP2350A #PicoW #UARTboot #Electronics
I kinda wish that #nabucasa / #homeassistant would officially adopt #wled like they did with #esphome so the project can get more dev resources (and finally bring Wled to the #raspberrypi #picoW )
I think I've confused my poor #PicoW running #CircuitPython. It thinks I've pressed a reset button the board doesn't have 😆 (I shorted another USB port on the HUB).
You are in safe mode because:
You pressed the reset button during boot.
Press reset to exit safe mode.
