Using Raspberry Pi's Built‑in Hardware Watchdog for Automatic Recovery
Enable the Raspberry Pi’s built‑in bcm2835‑watchdog driver and a small userspace daemon to get automatic recovery from software hangs without extra hardware.
Loading…
ReadMeFeed / Community knowledge
Raspberrypi
Real questions. Useful conversations. Find the people who know your stack.
Raspberrypi
Developer tools · #raspberrypi
Architecting a Headless Raspberry Pi IoT Gateway for Sensor Aggregation
Learn how to build a stable, headless Raspberry Pi IoT gateway using read-only filesystems, hardware watchdogs, and strict logic-level boundaries to prevent SD corruption and downtime.
Managing Raspberry Pi GPIO: BCM vs. BOARD Numbering and Voltage Safety
Learn the critical differences between BCM and BOARD numbering in Raspberry Pi GPIO, how to prevent SoC damage via voltage management, and how to implement stable inputs using pull-up resistors.
pythonFull Disk Imaging vs. Partition-Level Backups for OS Recovery
System State Recovery Strategy When managing Raspberry Pi OS upgrades, ensuring a reliable recovery path is critical if a package update leads to a corrupted root filesystem or a broken dpkg state. There are two primary documented approaches for capturing the system state: full disk imaging and partition-level backups. Recovery Trade-offs Full disk imaging c
vcgencmd get_throttled returns 0x50005 only in production: under-voltage on a bench-tested Raspberry Pi power supply
A Raspberry Pi 4 deployment runs cleanly on the bench with a 5.1 V / 2.5 A adapter, but once installed on site it intermittently shows the lightning-bolt icon. Reading vcgencmd get_throttled returns 0x50005 , which the documentation maps to under-voltage and throttling having occurred since boot. The production setup differs from the bench in three ways: a l
"Hash Sum mismatch" during apt install on Raspberry Pi OS: stale index or out-of-sync mirror?
On Raspberry Pi OS (Debian-based, bookworm assumed), an apt install or full-upgrade can fail with a Hash Sum mismatch error when the local package index under /var/lib/apt/lists no longer matches the repository's current Release and Packages metadata. The apt toolchain only refreshes this index when apt update runs; it does not check freshness automatically