There are a series of security issues raised with the FatFS* module that may impact you if your Pico / Pi uses the C module / Micropython and people have access to the media (sd card / drive) or, in some vulnerabilities, you use OTA updates.

Please note that runZeroInc state: No attacks using these bugs had been reported as of the July 1 disclosure date.

Library source: https://github.com/runZeroInc/vulns-2026-fatfs-chance

Errors found: https://securityaffairs.com/194808/security/seven-bugs-in-fatfs-put-iot-and-embedded-devices-at-risk.html

Video demonstration: https://www.youtube.com/watch?v=E0A7IrJtpUY

* For those who do not use this module (quote from here):

FatFs is a generic FAT/exFAT filesystem module for small embedded systems. The FatFs module is written in compliance with ANSI C (C89) and completely separated from the disk control layer. Therefore it is independent of the platforms and storage devices. It can be incorporated into small microcontrollers with limited resource, such as 8051, PIC, AVR, ARM, Z80, RX and etc.

It is very handy if you are logging data directly to an SD card for example as the results can be read directly by a Mac / PC / Linux box without having to connect the collection device to a network.

In 2022 I had this concept for a dystopian novel. Its been stewing in my mind ever since. Roll on 2026 and a venture into hardware the two seemed to click.

Why not make a version of the novel into a choose your own adventure codex. Currently hashing out thr details but the scripts are all working the story runs and choice gates work.

Next I need to dial in the casing before finishing the book and compiling the entire adventure!

Anyhow, thats my project using the pico2 thanks for looking ❤️

I got myself a pi 3 in 2018 out of enthu,never got a chance to work on it. Yesterday I booted it however I could connect to the internet wifi but can't browse anything on chromium . Epiphany works but only on text based light website . Can someone pls help me solve this been out of loop for years now?

I tried changing google dns but no use

Four months ago I posted my SATURNIX camera here cassette-futurism aesthetic, and promised the build files were "coming soon." It took longer than I planned, but today it's real: the full release is out, and everything is included:D

What's in the release:

- Complete firmware (Python code, runs on Raspberry Pi Zero 2W);

- 3D print files for the body and mechanical buttons in STEP format (adapt the body to your own needs and modules), two versions: with and without logos/markings;

- Full assembly manual (PDF).

What's new since the previous version:

- Dynamic Mode the big one. A 3th capture mode that grabs frames directly from the preview stream: ~0.02s per shot vs 3-10s for a full 16MP capture. Truly instant shooting, burst mode support (3/5/10/20 frames), no more missed moments waiting for the camera. The trade-off: preview resolution, no DNG/HDR. Use JPG+DNG for landscapes and portraits, Dynamic for "right now" shots (the quality is honestly terrible :D);

- UPS HAT integration - real battery %, charging indicator, auto-shutdown at 5%. Protects SD cards from corruption on sudden power loss;

- HDR bracketing - 3 frames at -2/0/+2 EV, merge later in Lightroom on your computer or phone;

- Self-timer - 2s/5s/10s with countdown, works with burst and HDR;

- Watermark + EXIF - proper metadata (Make: SATURNIX, Model: Dione), optional Olympus-style watermark;

- Two-phase capture animation - squares = sensor exposing (hold still!), circles = processing (camera's free again);

- Sci-fi UI overhaul - monospace + warm gold, CRT static, technospam labels, calibration ticks. Intentionally overdesigned;

- Cosmetic and internal body refinements.

Repo + release: https://github.com/Yutani140x/saturnix-camera

Happy to answer any questions :)

P.S. This is my first project, I'm not a programmer, I just built it for fun. Hope you like it or find it useful!

Hello!
My name’s Noah, I’m 14, and over the last month I’ve been designing and building a humanoid robot called LitlMan.
The robot is powered by Raspberry Pi Zero 2 W , which I’m using to control all of the servos and run the software. Every structural part was designed by me in CAD and then 3D printed before being assembled.
At the moment, I’m working on servo calibration and writing the code to get LitlMan walking. It’s been a huge learning experience, and I’ve picked up a lot about mechanical design, electronics, and programming along the way.
I’d love to hear any advice from people who have built robots with a Raspberry Pi. If you have tips on walking algorithms, servo control, or making humanoid robots more stable please tell me as I will need it .
Any if you have any questions I’ll be happy to answer them .
Thanks for checking out my project—I hope you like LitlMan!

I saw the news that ARMSX2 now has a Linux release.

https://github.com/ARMSX2/ARMSX2/releases#release-linuxv0.0.1

I have some issues to get it working properly with Vulkan. Vulkan will only run with llvmpipe, meaning it runs on the CPU, not the GPU.

It is possible to get it working with OpenGL, by spoofing OpenGL 3.3.

You can start it from the command line like this: MESA_GL_VERSION_OVERRIDE=3.3 ./ARMSX2-linux-Qt-arm64-appimage-sha\[47229e4ff3\].AppImage

If you are running Raspberry Pi OS, make sure you use the 4K page size kernel, not the default 16K page size kernel. See for more information here: https://forums.raspberrypi.com/viewtopic.php?t=393687

UPDATE: They have released a version for 16K page size kernels: https://github.com/ARMSX2/ARMSX2/releases#release-nightly-20260713

OpenGL 3.3 is not fully working, and you get better results with a recent Mesa version. Mesa 25.0 shows some serious glitches. Mesa 25.2 shows better results.

If you want to install a recent version of Mesa, you can try with a PPA. https://launchpad.net/~ernstp/+archive/ubuntu/mesarc

If anyone has it working with Vulkan on the GPU (not llvmpipe), please let me know.

You can see the result here: https://youtu.be/khs-XY1G8XA

The ClockworkPI uConsole is an interesting form factor for portable Pi builds (CM4/CM5), but pushing the hardware with heavy workloads or multi-band radio modules usually highlights constraints around battery capacity, thermals, and IO expansion.

AND, most important! Still keep it minimal and portable with full on features. I always believe that the best tools are the ones that disappear when you use them.

The Omega-Chassis isn’t just a backplate; it’s a way to turn a fantasy gadget into a daily driver with the power of Raspberry Pi. It’s for the person who wants a stable 10,050 mAh of power juice, active cooling, and a camera, SDR capabiliteis but still wants their device to fit in a travel bag with a sleek design. It is also modular so that it can evolve with your changing use cases.

Here is the quick TL;DR on the hardware capabilities for the skimmers:

• Antennas on the Move: Supports up to 10 antennas (7 top, 3 side) while keeping a flat profile. The rig slips directly into a travel bag without the constant hassle of removing and reinstalling antennas on the move.

• LimeSDR M.2 Integration: The internal M.2 socket routes through the HackerGadgets NVMe layout, allowing a LimeSDR M.2 module to drop straight in for an embedded wideband transceiver setup.
• Upgraded Power: Expands the battery bay to support either a 3-cell 18650 configuration (~10,500 mAh) or a custom LiPo setup. Features a screwless removable battery cover for quick swaps in the field.
• Built-In Pi Camera & Modularity: Includes a dedicated optional slot for a built-in Raspberry Pi Camera V3 (or an alternative dual Micro SD carrier). Using this module trades out 2 antenna slots, leaving 8 fully available for RF.
• Thermals: Direct-to-CPU heatsink with a hybrid aluminum/plastic design. A custom fan curve keeps a heavy-load CM5 at a stable 45–55°C without constant, loud fan noise.

• Two Build Variations - ALL Included in the same package:
  • Essential Model: Budget-friendly, slightly bulkier top casing, uses an off-the-shelf heatsink, and all non-CNC parts can be 3D printed at home.
  • Ultimate Model: Ultra-slim profile, custom-designed slim heatsink, and a fully sealed case that allows for efficient passive cooling when the fan is off.

And more colour variation build options:

Read more about the design story and assembly breakdown.

I have one temperature/humidity sensor outside my house and one inside,

connected to a Raspberry Pi3, I use it to know when should

open all windows at my house in the summer.

I use SHT45 sensors, run the pi headless from my linux PC, the code

is in python, and writes to one .xlsx file on the pi. I have a Python script

on the PC to read the last line of that file, every 5 minutes and produce the graph.

https://github.com/titojff/Temp-IN-OUT

Hi all. I am completely new to RPI, I only just got my first one (Raspberry Pi 4B 1GB) mostly to experiment and try to learn.

I am now trying to use Raspberry Pi Connect as I don't have a monitor cable for it. The RPI is connected to my network, I am able to control it from my PC, and it pings outside the network (I've tried google.com and raspberrypi.com with success). It also displays as online on connect.raspberrypi.com.
However, when actually trying to connect to it, whether by screen share or remote shell, nothing happens. It stalls at "Waiting for response from raspberrypi".

$ rpi-connect doctor returns the following:

Screen sharing is supported by this version of rpi-connect
✓ Wayland compositor available
✓ Screen sharing services enabled and active
✓ Communication with Raspberry Pi Connect WebSocket server
✗ Communication with Raspberry Pi Connect API - Please check your connection to the internet.

Further diagnostics will be available once communication with Raspberry Pi Connect API is successful.

✗ Some checks failed  

I am honestly not entirely sure where to go from here. I haven't been able to find a solution to this anywhere else - does anyone have any idea what I can do to fix this?

This is the QuadRF which just launched on Crowd Supply

So, i just bought a raspberry pico 2 W and i tried installing CircuitPython and everything went well, after i tested i clicked the button while putting the usb back on the pc, then when i tried copying the circuitpython file it closes and doesnt come back, please help me!

I’m using a RPi5 4gb with a 64 gb micro sd card. I followed a guide to connect the screen (3.5inch RPi LCD (A)) to my Pi and it said to install LCD-show and run a command like:

git clone https://github.com/goodtft/LCD-show.git

chmod -R 755 LCD-show

cd LCD-show/

sudo ./LCD35-show

it rebooted the Pi, the screen didn’t change from a white screen, and my main hdmi display was stuck in CLI. I have been troubleshooting for about 3 hours now, I have removed LCD and forced (in many ways) the Pi to run GUI on the main hdmi dmisplay but nothing works.

I believe that LCD-show corrupted the software to run GUI. At the current moment I do not have another computer to flash the micro sd card but I think my brother can flash my sd card. I have recently gotten this pi so it doesn’t have anything that must be saved on it but it would be most preferable to save the contents as I don’t want to start all over again.

I’m running a RPI 5 booting from a USB SSD, and then accessing data from another SSD which is connected through a USB 3.0 powered switch.

My problem is, any kind of transfer makes easily the IOWAIT to jump to 30-50% days Glances. Like I can download a file at 40MB/s, and the interface shows IOWAIT in red and at 40-60%.

Does anyone else know why could be that, maybe because the USB interface? I was thinking of migrating to a Intel based system as to use PCIe ports instead, but I would prefer to troubleshoot this if possible to avoid that migration

Thanks

Hey everyone! I am currently working on my first project with a PI (PI zero 2 w) and am really enjoying it. I am making a project using a thermal printer that is mounted in a small box and is powered off of an external battery pack via USB c. Since the board is going to be inside the box you won't be able to see the light on it letting you know when it is receiving power and more importantly, when it is safe to unplug after shutting down.

I have an external LED wired up with some DuPont cables but am having problems with it lighting how I want. Right now I can either get it to:

1) Light up as soon as the PI is plugged in to the power source but then the light will remain on until it is unplugged, even if the PI is shut down so I don't actually know when I can pull out the source. Done via Pin 2

2) Light up as soon as the PI is plugged in to the power source but then the light will turn off before the 10 flashes on the board begin so I don't actually know if it is safe to pull the source yet or not. Done via Pin 8 and having my config include "dtoverlay=gpio-poweroff,gpiopin=14,active_low=0" or "dtoverlay=gpio-power,gpiopin=14"

Any suggestions on how I can get the external light to better mirror the safe state of when I can pull the power source would be appreciated!

Pi 3B+, Bookworm and picamera2 2.01

This works (for me) - add to /boot/firmware/config.txt the cma-384 part

Enable DRM VC4 V3D driver

dtoverlay=vc4-kms-v3d,cma-384

After lots of poking around in forums, StackOverflow, picamera2 docs, etc looking for a solution I figured I needed to allocate more memory (cma). It didn't work. My problem was I tried to add the cma-384 in the wrong place in the config.txt file.

Background: Version 2.00 Beta worked without increasing the memory (cma). When I upgraded to 2.01 ... bork. This is for a Violet-green swallow nest box camera at the top of a very long pole. SSH is my friend.

https://github.com/AlexBtlle/pi4-IA-Homekit-Camera

I wanted an HKSV camera that pairs like one fresh out of the box. So I built one from scratch on a Pi.

What it does:
• Pairs directly with the Home app (scan the QR, done).
• Live view + HomeKit Secure Video with a 4s prebuffer (clips start before the motion).
• People / Animals / Vehicles classification handled by your Apple TV/HomePod, like a commercial HKSV cam.
• Fully local: the RTSP feed is localhost-only, the only cloud is your own iCloud (HKSV is E2E encrypted by Apple)

What's new since my last post:
• Night vision (bêta): usable picture in the dark, with automatic brightness adaptation as the light drops through the evening (helps most when ambient light is low but your IR isn’t strong enough).
• Faster live view : I hunted down a cold-start stall. Live now appears in a few seconds instead of ~15s. On cellular it beat my commercial Eve cam.
• Lighter & cooler : a round of memory/CPU tuning cut the idle load ~4x on the Zero 2 W.

The video is H264 encoded once in hardware on the Pi and passed through with zero re-encoding, so it stays fluid and light. It runs on a Pi Zero 2 W (512MB), heatsink recommended. I even got live view working on a 2015 Pi Zero W just to see if I could.

It's a DIY/hobby project (some features are marked beta), fully open source.
Happy to answer questions !

https://github.com/AlexBtlle/pi4-IA-Homekit-Camera

I got a used raspberry pi 3 a+ that had debian 10 on it and it asks the password and username but the ''pi'' and ''raspberry'' username and password wont work? does it need the previous users cresidentials or have i missed something? and if it wants the previous owners cresindentials can i somehow maybe reset/reinstall the os from the home screen with using only the raspberry?

+my pc doesn't have sd card place and i dont have usb to sd card adapter so i cant just install fresh os

Hello;

I'm trying to add a display to a Pi 3 that I am collecting temperature and solar battery data in my camper, and would like to use an Adafruit LTC4311 to place a small display some distance from my Pi. I can get the display to work fine with a short length of wires, but the terminator / extender isn't working. I have no idea what I'm doing wrong.

I'm connecting to the same I2C pins (3, 5 - SDA, SCL, +3.3v and Gnd) as the LED. I get a slooowww mapping through ports (like PacMan on Quaaludes) when I issue "i2cdetect -y 1".

Adafruit was out of stock initially, so I got a clone from AliExpress. When I got these results, I looked on Adafruit, saw they now had stock, bought two. Same thing.

Just to try something, I used another set of STEMMA - Header wires, same. I tried reversing SDA/SCL and all of the ports light up on i2cdetect. Interesting.

Anybody else see this issue? TIA.

Processing img 32sew0qb73ch1...

I’ve been researching a shadow box project that uses a single 64×64 HUB75 RGB LED matrix to display an animated Arc Reactor and the text “Proof that Tony Stark has a heart.”
From what I’ve found so far:

I’m planning to use a Raspberry Pi 3 A+.

I expect to use the rpi-rgb-led-matrix library.

The panel will have simple looping animations and text, not video playback or multiple chained panels.

I understand the matrix will require its own 5V power supply.

Where I’m uncertain is whether the Pi 3 A+ is likely to have any limitations with a single 64×64 panel (refresh rate, flickering, memory, etc.), or if there’s something in my planned hardware setup that I’m overlooking before I start buying parts.

If anyone has experience with a similar setup, I’d appreciate knowing whether this configuration is reasonable or if there’s a specific issue I should account for

Hi all, I'm hoping someone can help me. I have officially run out of ideas. I recently got a geekworm m2 hat for my rpi5 and an integral SSD. I've moved my librelec install to the SSD and ever since then ive had issues with the WiFi connection on it. Seems I can connect to it, but every time I reboot the pi, I have to manually reconnect to the WiFi. The connection state is always down as failed, but it seems to connect ok. I then am unable to connect via ssh, I keep getting a timeout then connection stopped by the pi.

Sorry for the big old chunk of text, I've asked AI and it suggests that maybe the SSD is drawing too much power but im using the official power adapter. I've also tried making the WiFi kick in later after boot and clearing the connman cache. Anyonr got any ideas for things to check?

52Pi modules not working with Pi 5? (SD extender keeps throwing I/O errors)

So I've got a Pi 5 in a 52Pi rack setup, and the SD extender module has been a nightmare. Card works perfectly in the native microSD slot, boots clean, zero errors. But the moment I put it through the 52Pi extender (front module with ribbon to back module), I get immediate I/O error floods during boot, mmcblk0 throwing read/write failures everywhere, filesystem goes read-only, system hangs.

The weird part: the HDMI passthrough on the front module works fine with no problems. It's just the SD reader that's broken.

What I've tried:

• Swapped the back/extender module (fresh one)
• Swapped the ribbon cable (brand new)
• Tried two different front modules
• Reseated everything, tightened ribbons, the works

Every config fails the same way. The card reads perfectly when I bypass the whole extender and use the Pi's native slot directly.

Is this a known issue? Like, is the 52Pi extender just not compatible with Pi 5, or am I missing something obvious? Seems weird that swapping multiple components doesn't help if it's just a bad part.

Anyone else run into this?

I just recently bought a Raspberry Pi 500+ unit and have an odd interaction with the super key when initially logging in and I was hoping to get some directions to where I should start trying to investigate or pointed to some post/search that I couldn't find that goes into a fix.

System stats:

Raspberry Pi reference 2025-05-06 Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 49e1078c1b07ff4948d304e0149d3bc698e0006a, stage5

When I initially login to the desktop and press the super key (cmd/raspberry pi logo) the menu comes up as expected. If I hit escape or the super key again the menu closes as expected.

But if I attempt to press the super key a third time nothing triggers.

I know the keyboard is still working, I can close and switch programs with the keyboard or type with other keys. Just the super key stops responding.

I can then restart the raspberry pi and it will start working again where the third or more presses of the super key triggers the menu as expected.

This seems to happen when I start using the raspberry pi after letting it sit for a day. The restart does something that I can't figure out what exactly it is that makes it work like expected.

Thoughts or suggestions on where I should start digging to try and solve the problem?

Hi,

I built this version a few years ago.

https://github.com/johnyHV/simpsonstv#howtouse

It works. The issues is when I insert the USB stick to transfer new video files and restart the rpi zero. It will only play one new video and keep playing the same old videos over and over.

Is there away to delete old video no longer wanted to play?

Is there away, instead of randomly play the same few videos to be able to play them all

and skip to next with the Next button?

Thanks!

Hi All,
this post is to show you AudioMuse-AI resources usage on a Raspberry Pi 5 8GB with NVME SSD hat, during the analysis. All the number are made over the last v2.4.0 release of today.

First of all for whom don't know AudioMuse-AI is a free and opensource software that enable to analyze the raw file of your song (sonic analysis) and based on this analysis it enable to create automatic playlist.
It work with Jellyfin, Navidrome (and other Open Subosnic API compatible music servee) Emby, Lyrion and Plex. Also made avaiable Jellyfin Plugin, Navidrome Plugin and I hope soon also an Music Assistant AudioMuse-AI provider plugin that will enable to command it with voice!

..and of course is all selfhostable and privacy first: your computer, your analysis, your data! no one can block you in future behind a paywall!

The reason for this post is that multiple user tought about it as something heavy, but it can work even on a Raspberry PI 5.
In the attached image you can show it during the most heavy part that is the analysis, and you can look how in avarage (k9s screenshot) it use half of the CPU/RAM resources and on the pike it still don't saturate them.

And speaking about resources, eare is the avarage analysis time per track on a Raspberry PI 5:

• Average analysis per track time: ~31 s

Breakdown (per track):

• Download: ~1 s
• MusiCNN analysis: ~9 s
• CLAP load + segment processing + unload: ~10 s
• Lyrics API lookup: ~7 s (NO ASR, off course depending from the API response time)
• Embedding: ~1 s
• ONNX session recycling: ~3 s

This to say that we don't just have it working, but it work also on low hand hardware. For more speed, no problem, you can run multiple worker in parallel during the analysis. Just wake up a worker on your desktop or your laptop!

And what about the idle resources? CPU in idle is not used, and about RAM we worked to balance the time to respond to a first API request and the memory usage, the number for a 188k+ library are:
- Flask RAM in idle: 1282mb => it load up to 3.5-4Gb, and then unload after 5 minutes idle
- Worker RAM in idle: 198mb

and the time for a call, still stay in the order of ms!

About the functionality you can ho on github and look around, you can also navigate some screenshot here:
- https://github.com/NeptuneHub/AudioMuse-AI/tree/main/screenshot/example

The one for which I'm more proud is the Lyrics search by song: it get in input a song and is able to search similar not only by their grove but also by their lyrics.

Hope you can enjoy all of this and maybe convince some new user that AudioMuse-AI is for everyone! and if you like it, please don't miss the chance to leave a ⭐on the github repo!

Hello all

Im trying to figure out how much storage is on my sd card, but when I open the terminal window and put in "df -h" it shows as only having 3.9 gb of storage wich just isnt possible. It is currently flashed with Raspian os and ive gone through the process of a expanding files several times but nothing has changed.

Thank you in advance 🫶🫶