Fosstodon

YvanRight, current status with all my mucking about with <a href="https://toot.ale.gd/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> on <a href="https://toot.ale.gd/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPi</a> <a href="https://toot.ale.gd/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a>: <a href="https://yvan.seth.id.au/rusty-pico-w-co2-ppm-sensor.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yvan.seth.id.au/rusty-pico-w-co2-ppm-sensor.html</a>With all the hard work done by <code>embassy</code>, <code>picoserve</code>, and <code>libscd</code> — 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.

YvanHurrah... my <a href="https://toot.ale.gd/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> based <a href="https://toot.ale.gd/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> 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.

YvanFUCKING A!I have a <a href="https://toot.ale.gd/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> programme on my <a href="https://toot.ale.gd/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPi</a> <a href="https://toot.ale.gd/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> 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.)<a href="https://toot.ale.gd/tags/embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embedded</a> <a href="https://toot.ale.gd/tags/embassy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embassy</a>

YvanRIGHT. 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 <code>embassy</code> from GitHub again.I have then grabbed <code>picoserve</code> from GitHub and I have edited the relevant <code>Cargo.toml</code> to use the <code>embassy</code> packages from GitHub.An in my project <code>Cargo.toml</code> I have referenced my downloaded and modified <code>picoserve</code> 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 <code>picoserve</code>, loaded it onto the <a href="https://toot.ale.gd/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a>, and it runs and serves a "Hello World" via HTTP.<a href="https://toot.ale.gd/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> <a href="https://toot.ale.gd/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPi</a> <a href="https://toot.ale.gd/tags/Pico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pico</a> <a href="https://toot.ale.gd/tags/Embassy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Embassy</a>

YvanSo, another <a href="https://toot.ale.gd/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> <a href="https://toot.ale.gd/tags/embassy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embassy</a> <a href="https://toot.ale.gd/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> question. I started out with <code>embassy</code> examples and had a working thing that compiled and ran on a Pico W.But then I wanted to use <code>picoserve</code> and this ran me into some dumb looking dependency problems.I fixed that by following advice to remove the <code>git</code> entries from my <code>Cargo.toml</code>.However I then have a linker error, one that can be fixed by removing <code>build.rs</code> - 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 <code>build.rs</code> was adding these linker arguments: <code>-C link-arg=--nmagic -C link-arg=-Tlink.x -C link-arg=-Tlink-rp.x</code>.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

YvanToday I successfully got <a href="https://toot.ale.gd/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> code working for a <a href="https://toot.ale.gd/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPi</a> <a href="https://toot.ale.gd/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> 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:<ol><li>DHCP to local network</li><li>Listen and respond to TCP</li><li>Poke a GPIO (blink)</li><li>Logging to USB-TTY</li></ol>The real TL;DR is: The <code>embassy</code> 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: <a href="https://yvan.seth.id.au/rusty-pico-w.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yvan.seth.id.au/rusty-pico-w.html</a><a href="https://toot.ale.gd/tags/microcontrollers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#microcontrollers</a> <a href="https://toot.ale.gd/tags/pico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pico</a>

Andy Warburton ❌❌❌Video of the Badger up and running showing multiple sensors and controlling smart home devices via its buttons! <a href="https://www.youtube.com/watch?v=r-DjXnoWFrA" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=r-DjXnoWFrA</a> <a href="https://mastodon.social/tags/esphome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#esphome</a> <a href="https://mastodon.social/tags/homeassistant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homeassistant</a> <a href="https://mastodon.social/tags/badger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#badger</a> <a href="https://mastodon.social/tags/pimoroni" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pimoroni</a> <a href="https://mastodon.social/tags/pipico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pipico</a> <a href="https://mastodon.social/tags/picow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#picow</a> <a href="https://mastodon.social/tags/raspberrypi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#raspberrypi</a> <a href="https://mastodon.social/tags/maker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#maker</a> <a href="https://mastodon.social/tags/homeautomation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homeautomation</a>

Andy Warburton ❌❌❌Exciting! I have my Pimoroni Badger 2040W working in ESPHome including the buttons and display! You can see the code here:<a href="https://community.home-assistant.io/t/anyone-successfully-used-pimoroni-badger-with-esphome/741067/10?u=hellweaver666" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://community.home-assistant.io/t/anyone-successfully-used-pimoroni-badger-with-esphome/741067/10?u=hellweaver666</a><a href="https://mastodon.social/tags/esphome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#esphome</a> <a href="https://mastodon.social/tags/homeassistant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homeassistant</a> <a href="https://mastodon.social/tags/badger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#badger</a> <a href="https://mastodon.social/tags/pimoroni" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pimoroni</a> <a href="https://mastodon.social/tags/pipico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pipico</a> <a href="https://mastodon.social/tags/picow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#picow</a> <a href="https://mastodon.social/tags/raspberrypi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#raspberrypi</a> <a href="https://mastodon.social/tags/maker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#maker</a> <a href="https://mastodon.social/tags/homeautomation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homeautomation</a>

Chris BurtonI'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.<a href="https://widget.uk/tags/CircuitPython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CircuitPython</a> <a href="https://widget.uk/tags/RP2350" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RP2350</a> <a href="https://widget.uk/tags/RP2350A" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RP2350A</a> <a href="https://widget.uk/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> <a href="https://widget.uk/tags/UARTboot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UARTboot</a> <a href="https://widget.uk/tags/Electronics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Electronics</a>

Andy Warburton ❌❌❌I kinda wish that <a href="https://mastodon.social/tags/nabucasa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nabucasa</a> / <a href="https://mastodon.social/tags/homeassistant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homeassistant</a> would officially adopt <a href="https://mastodon.social/tags/wled" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wled</a> like they did with <a href="https://mastodon.social/tags/esphome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#esphome</a> so the project can get more dev resources (and finally bring Wled to the <a href="https://mastodon.social/tags/raspberrypi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#raspberrypi</a> <a href="https://mastodon.social/tags/picoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#picoW</a> )

Chris BurtonI think I've confused my poor <a href="https://widget.uk/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> running <a href="https://widget.uk/tags/CircuitPython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CircuitPython</a>. 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.

wook :fedora:<a href="https://mastodon.cloud/@adafruit" class="u-url mention">@adafruit</a> .. (in poor timing) i bought my first stand-alone <a href="https://fosstodon.org/tags/PicoW" class="mention hashtag" rel="tag">#PicoW</a> last week from microcenter, but now that I started using it and learned about the extensive CircuitPython/library support from <a href="https://fosstodon.org/tags/AdaFruit" class="mention hashtag" rel="tag">#AdaFruit</a>, I’ll make sure to buy the <a href="https://fosstodon.org/tags/Pico2W" class="mention hashtag" rel="tag">#Pico2W</a> from them!

wook :fedora:Is there an existing library or method to re-program a <a href="https://fosstodon.org/tags/PicoW" class="mention hashtag" rel="tag">#PicoW</a> via WiFi OTA ? The only suggestions I’ve seen are to write your own http server that browses the file system and accepts uploads to replace existing scrips then reboots. I’m too lazy and want to focus on building other stuff, not tooling.

j4n3zKamarád mě poprosil o PWM kontroler na ventilátory do racku, který bude schopný se připojit k <a href="https://mastodon.social/tags/HomeAssistant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HomeAssistant</a>. Koncept by byl. Otestoval jsem připojení k HA a základní výstup ovládání. Ještě mi zbývá vyzkoušet zapojení na nepájivém poli a pokud to bude fungovat, tak objednat tišťák. Samozřejmě k tomu ve finále přibude i nějaká krabička 🙂<a href="https://mastodon.social/tags/KiCad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KiCad</a> <a href="https://mastodon.social/tags/Raspberry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Raspberry</a> <a href="https://mastodon.social/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> <a href="https://mastodon.social/tags/tinkering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tinkering</a>

Guido Lehwalder<a href="https://mastodon.online/tags/RunCPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunCPM</a> v6.7 for <a href="https://mastodon.online/tags/Pico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pico</a> & <a href="https://mastodon.online/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> This time with CCP-Internal-64K available at <a href="https://github.com/guidol70/RunCPM_RPi_Pico/raw/refs/heads/main/v6_7/GL20241105_Binary_Source_RunCPM_v6_7_Pico_W_260_270Mhz_CCP-Internal_64K.zip" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/guidol70/RunCPM_RPi_Pico/raw/refs/heads/main/v6_7/GL20241105_Binary_Source_RunCPM_v6_7_Pico_W_260_270Mhz_CCP-Internal_64K.zip</a>

Guido LehwalderHere comes the <a href="https://mastodon.online/tags/RunCPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunCPM</a> v6.7 <a href="https://mastodon.online/tags/Update" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Update</a> for RPi <a href="https://mastodon.online/tags/Pico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pico</a> & <a href="https://mastodon.online/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> with the ABDOS.SYS and CCP-DR.64K ATTENTION: be arware of the REAME.TXT ;) Get it at <a href="https://github.com/guidol70/RunCPM_RPi_Pico/raw/refs/heads/main/v6_7/GL20241103_Binary_Source_RunCPM_v6_7_Pico_W_260_270Mhz.zip" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/guidol70/RunCPM_RPi_Pico/raw/refs/heads/main/v6_7/GL20241103_Binary_Source_RunCPM_v6_7_Pico_W_260_270Mhz.zip</a>

SidecarTridgeThis is a story about how a flaw in PCB design can severely impact network performance, especially with the <a href="https://oldbytes.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaspberryPi</a> <a href="https://oldbytes.space/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a>.Below are some pictures (apologies for the quality) showing two versions: the production revisions (in white) of the <a href="https://oldbytes.space/@sidecartridge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sidecartridge</a> and a new prototype in development (in black).The production versions adhere to the Raspberry Pi engineers’ PCB design guidelines for optimizing network performance using the Infineon CYW43 WiFi and Bluetooth chip on the <a href="https://oldbytes.space/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a>. These devices are able to detect several WiFi networks in my area, including my own—CHISMEROUTER_RPT, 4 meters away, and CHISMEROUTER, 20 meters away behind walls.In contrast, the prototype deviates from the recommended design and includes two copper layers directly under the <a href="https://oldbytes.space/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a>, which is a significant error. As a result, the device’s performance drops dramatically, barely detecting any of the nearby WiFi networks.Is this prototype viable? Clearly not. However, despite the poor network performance, it’s a valuable part of the learning process. It’s helping me redesign the <a href="https://oldbytes.space/@sidecartridge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sidecartridge</a> Multi-device network stack to handle low-quality connections better. As expected, some users blame the device when they experience weak WiFi signals. The <a href="https://oldbytes.space/@sidecartridge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sidecartridge</a> aims to address this, and I’m working on it.BTW, the pictures are from the forthcoming firmware release v1.0.0

MikeredPimoroni just released a WiFi enabled pico2 plus, beating raspberry pi to wireless rp2350 <a href="https://shop.pimoroni.com/products/pimoroni-pico-plus-2-w" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://shop.pimoroni.com/products/pimoroni-pico-plus-2-w</a>A touch expensive at £16.80, but ordered one !<a href="https://fosstodon.org/tags/raspberrypi" class="mention hashtag" rel="tag">#raspberrypi</a> <a href="https://fosstodon.org/tags/rp2350" class="mention hashtag" rel="tag">#rp2350</a> <a href="https://fosstodon.org/tags/pico2" class="mention hashtag" rel="tag">#pico2</a> <a href="https://fosstodon.org/tags/PicoW" class="mention hashtag" rel="tag">#PicoW</a>

Guido Lehwalder<a href="https://mastodon.online/tags/RunCPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunCPM</a> v6.6 is downloadable for RPi <a href="https://mastodon.online/tags/Pico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pico</a> and <a href="https://mastodon.online/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> <a href="https://mastodon.online/tags/TTGO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TTGO</a> <a href="https://mastodon.online/tags/VGA32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VGA32</a> and Windows 32bit & 64bit at my github-page <a href="https://github.com/guidol70" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/guidol70</a>

Guido LehwalderThe next days I will upload: <a href="https://mastodon.online/tags/RunCPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunCPM</a> Update v6.6 for RPi <a href="https://mastodon.online/tags/Pico" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pico</a> & <a href="https://mastodon.online/tags/PicoW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PicoW</a> <a href="https://mastodon.online/tags/TTGO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TTGO</a> <a href="https://mastodon.online/tags/VGA32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VGA32</a> Windows 32bit & 64bit

Recent searches

Search options

Administered by:

Server stats:

#PicoW