Skip to content

docs(vital100s): the MCU UART is on TP57/TP64, not the debug header #87

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
benedikt-bartscher wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

docs(vital100s): the MCU UART is on TP57/TP64, not the debug header #87

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
df20256
docs(vital100s): the MCU UART is on TP57/TP64, not the debug header
benedikt-bartscher Nov 1, 2026
9419e1f
docs(vital100s): identify the UART pads by stock module pin
benedikt-bartscher Nov 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 16 additions & 5 deletions devices/levoit-vital100s/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,14 +138,25 @@ Four wires, plus one to silence the stock module:
| Connection | Where |
|-----------|-------|
| `3.3V`, `GND` | Debug header pins 3 and 2 |
| ESP `RX` ← MCU `TX` | Debug header pin 4 |
| ESP `TX` → MCU `RX` | Debug header pin 5 |
| ESP `RX` ← MCU `TX` | Test pad beside R92, at the stock module's corner — **TP64** in the pinout photo, **TP54** on other boards. Same net as module pin 27 (`IO18`) |
| ESP `TX` → MCU `RX` | Test pad **TP57**, next to header pin 6 (`IO0`). Same net as module pin 28 (`IO19`) |
| Stock ESP32 `EN` → `GND` | Debug header **pin 1**, tied to pin 2 |

The MCU link is **not** on the debug header. Header pins 4 and 5 are the stock
module's flashing UART — labelled *UART - Flash FW* in the
[pinout photo](#debug-header-pinout) — while the ESP ↔ MCU UART runs over the
two test pads labelled *UART ESP <> MCU* there (on the stock ESP32-C3 that is
GPIO18/19, see `levoit-vital100s.yaml`). With the stock module held in reset,
the header's TX/RX lead nowhere useful.

If a pad label doesn't match, go by the module: the ESP32-C3-SOLO-1 pinout is in
its FCC user manual (FCC ID 2AC7Z-ESPC3SOLO). With the module text readable,
pins 25-28 are the bottom four on the right side, counted upwards: `IO9`, `IO10`,
`IO18`, `IO19`. A beep test from each pad to pins 27 and 28 confirms the pair.

The debug header carries `EN` on pin 1, so the stock module can be held in reset
straight from the header — no probing needed. See
[Debug Header Pinout](#debug-header-pinout) above. Until it is held low, keep
your ESP's TX disconnected: both modules would otherwise drive the same line.
straight from the header — no probing needed. Until it is held low, keep your
ESP's TX disconnected: both modules would otherwise drive the same line.

> **Use an external antenna.** The board sits low in a plastic housing beside a
> metal fan assembly. The XIAO's onboard antenna works, but the FPC antenna in
Expand Down