Flashing an RP2040 board (tested with a Waveshare RP2040-Zero) from a Raspberry Pi over SSH using arduino-cli. Written for a first-time setup. Notes from actual trial and error.
Things that will differ on your machine are marked like <this>. Pay attention to usernames, serial ports, and file paths: do not copy-paste those blindly.
curl -fsSL https://raw.githubusercontent.com/arduino/arduino-cli/master/install.sh | sh
Imagine you have an embedded-system prototype running on a Pi 5 SBC, but you need a lightweight OS—for example, to boot faster. Typically, if you don’t need a GUI, you might use something like DietPi or the Raspberry Pi OS CLI (non-GUI) version. But what if you do need a GUI? Preferably a web app? Here’s a helpful nugget if you’re facing that scenario …
I didn’t realize that these days we can display a Chromium frontend on this minimal OS without installing a heavy, full-blown desktop environment. Since the Pi 5 (our target) defaults to modern Wayland graphics, we can use a “kiosk” approach. This runs a lightweight Wayland compositor whose sole job is to draw the Chromium browser directly to the assigned external display, saving RAM and CPU for other processes.
Clone a running Raspberry Pi OS install from the microSD card to an M.2 NVMe SSD (via the Pi M.2 HAT+) and boot fully from the SSD. No desktop, all over SSH.
Tested on: Raspberry Pi 5, Debian 13 (trixie), Pi OS Lite 64-bit, 256 GB NVMe.
Tip
Why not SD Card Copier?
That is a desktop GUI tool. On a Lite/headless image, it does not exist. This guide uses rpi-clone instead.
What it took to get visualbruno/ComfyUI-Hunyuan3d-2-1 running reliably on Linux with PyTorch nightly + Blackwell
Auto-launch a tmux monitoring dashboard on Raspberry Pi boot (headless/CLI). Press any key within 10 seconds to skip and drop to shell.
Note
I use this for a pi that I carry on-site, either when I'm teaching or on a client side, where I need a MQTT broker and also where wifi setup shoudl be easy (So, my pi is running: headless pi wifi configurator)
To make the main branch exactly like the dev branch by ignoring the changes in the main branch and overwriting it with dev:
git fetch originCheck out to the main branch:
git checkout main
Imagine you are making small webapp to control a hardware protoytpe.
It is part of a set of internal tools and utilities that you are building for a bigger project, to aid you in testing or something else.
This repo, since it is a client project, is private.
Now, let's say the private git repo, you are maintaining those utilities is hosted in github as: github.com/user/utility_repo
At some point you want to make the web-app go live, you don't want to bother working on a bare-metal VPS, you want to just simply use gh-pages because it provides ssl support out of the box, it's simple, lean and gets the job done, while your repo still remains private.