Add an embedded dev-env for ESP32 and Arduino boards - #9723
Open
HugoluizMTB wants to merge 2 commits into
Open
Conversation
`omarchy install dev-env embedded` installs arduino-cli, platformio-core, esptool, avrdude, and picocom, then clears the two things that otherwise stand between a freshly plugged board and a working upload: - Serial devices belong to `uucp` on Arch, so without group membership every upload and every serial monitor needs sudo. Most advice found online names `dialout`, which does not exist here. - ModemManager probes new serial devices on plug-in and holds them open long enough to break the first upload. A udev rule marks the common development board vendors so they are left alone: CH340/CH341 (low-cost ESP32 and Arduino clones), CP210x (ESP32 DevKit), FTDI (official Arduino and debug probes), and the Espressif and Arduino native-USB IDs. Both are the kind of first-hour papercut the other dev-envs already absorb. Every package comes from the official repositories.
HugoluizMTB
force-pushed
the
dev-env-embedded
branch
from
September 2, 2026 02:08
f0ef68b to
62dd10f
Compare
The command alone is unreachable: Install > Development is built from `omarchy-menu.jsonc`, so without an entry there the environment exists but nobody finds it. The menu item is disabled once `arduino-cli` is present, matching how the other environments detect themselves. The manual lists the available environments by hand, so it gets the new one too.
Author
|
Pushed two follow-ups after re-reading
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
omarchy install dev-env embeddedinstallsarduino-cli,platformio-core,esptool,avrdude, andpicocom, then clears the two things that otherwise stand between a freshly plugged board and a working upload.Why
The 18 existing dev-envs each absorb their own environment papercuts — Composer on PATH, PHP extensions enabled, opam initialised. Hardware has none, and it has two that bite everyone on the first board:
Serial devices belong to
uucpon Arch. Without group membership, every upload and every serial monitor needs sudo. Almost all advice online namesdialout, which does not exist on Arch, so the search usually costs more time than the fix.ModemManager probes new serial devices on plug-in and holds them open long enough to break the first upload. The symptom is a failed flash that succeeds on the second try, which reads as flaky hardware rather than a fixable cause.
A udev rule marks the common development-board vendors so ModemManager leaves them alone and the node lands in
uucp:1a8610c40403303a2341Notes
omarchy-install-gaming-xbox-controllers.test/clipasses (116 tests).Tested on Arch with the toolchain install and udev reload; I did not have a board on hand to confirm the end-to-end upload, so a second pair of eyes on the vendor list would be welcome.