ESP-Mosaico#
The ESP-Mosaico build is OpenCarMind EdgeOS 2.1.0. It comes from the same source tree as the S3 build and keeps what mossREV 1.2.0 had: both models, the touch apps, Wi-Fi for the clock and the desktop app over USB. Version 2.1.0 adds the Health app and the AI services behind it.
What you need#
Part |
On the ESP-Mosaico V1.2 |
|---|---|
Chip |
ESP32-S31 (ESP32-S31NRV16), dual core, run at 320 MHz |
PSRAM |
32 MB in the package. The board’s user guide says 16 MB. The chip reports 33,554,432 bytes ( |
Flash |
16 MB NOR (GD25Q128): two 6 MB app slots, and 3.75 MB of FAT for the state files |
Drive-log store |
128 MB SPI NAND (GD5F1GM7UEYIGR) on its own SPI bus, see The 128 MB NAND |
Screen |
2.16 inch CO5300 AMOLED, 480 x 480, over QSPI |
Touch |
CST9220 on I2C |
Battery |
a small cell with a BQ27220 fuel gauge |
Radio |
Wi-Fi and Bluetooth. OpenCarMind uses Bluetooth LE for the OBD adapter, as on the S3 |
USB |
one Type-C port, the S31’s USB OTG port: console, the desktop app’s USB door, and flashing |
There is no SD card slot. The drive logs live on the NAND, and the learned model state, the clock, the settings files and the Wi-Fi list live in the flash FAT.
Unused pins. At boot every GPIO the firmware does not use is put in a safe state: input and output off and no pull resistor, held (the strapping pins 37 to 40 are not held), and the speaker amplifier’s enable (GPIO45) is driven low, so the amplifier stays off. The flash, USB, UART0 console and BOOT pins are never touched. This gives the same pin state at every boot. Its power saving is not measured.
You also need a Bluetooth LE OBD-II adapter, a USB-C cable, Python with pyserial and esptool 5.6.0 or later. The board needs no SD card: the drives go to its NAND.
Flash the firmware#
You need the merged image OpenCarMind-EdgeOS-2.1.0-ESP-Mosaico-ESP32-S31-merged.bin from the EdgeOS 2.1.0 release (check it against SHA256SUMS there), a USB-C cable, Python with pyserial (pip install pyserial), and esptool 5.6.0 or later (pip install "esptool>=5.6.0"), the version this release was tested with.
Before you flash, copy your drives off the board and expect to pair again. The merged image starts at address 0x0 and covers the NVS partition (0x9000 to 0xF000). Flashing it erases the pairing with the desktop app, the saved Wi-Fi networks, the settings, the Smart swipe and Smart UI verdicts, the model choice and the session counter. The flash FAT (0xC40000) and the NAND are not written, and the next session number continues after the highest one found on the storage, so old drives are not overwritten. Import your drives first anyway. A flash that stops halfway is not covered by that.
Plug the board into the computer. It shows up as a USB serial port (
/dev/cu.usbmodem...on macOS,/dev/ttyACM...on Linux,COMxon Windows).Put it into download mode without pressing a button: open that port at 1200 baud and close it again. The board waits until its storage has started, flushes the logs, holds the file systems and restarts into the chip’s ROM download mode.
python -c "import serial; serial.Serial('/dev/cu.usbmodemXXXX', 1200).close()"
A new port appears, the ROM’s. Write the image to it:
esptool --chip esp32s31 --port <ROM port> --before no-reset --after hard-reset \ write-flash --flash-mode dio --flash-freq 80m --flash-size 16MB 0x0 OpenCarMind-EdgeOS-2.1.0-ESP-Mosaico-ESP32-S31-merged.bin
The board restarts into OpenCarMind EdgeOS. The console (115200 baud on the same port) prints
OpenCarMind EdgeOS 2.1.0 running. Pair it again from the desktop app.
Measured on the board, OpenCarMind EdgeOS 2.0.0 4aeff43: the image EdgeOS-2.0.0-esp32s31-merged.bin (SHA-256 a225125d27f3906c...) printed OpenCarMind EdgeOS 2.0.0 running at 4.3 s and boot health good at 68.0 s. That 2.0.0 image was never published. The released 2.1.0 image is built from main at 1053f9d; its board checks are in the release notes and the README.
To go back to mossREV 1.2.0, flash mossREV-1.2.0-esp32s31-merged.bin with the same steps. It erases the NVS again, so pair again after it. Going back is not yet verified on the board.
To build it yourself, use ESP-IDF 6.1. The S31 is a preview target there, hence --preview:
. $IDF_PATH/export.sh
idf.py --preview set-target esp32s31
idf.py build
The board’s settings are in sdkconfig.defaults.esp32s31 and its partition table in partitions_mosaico.csv.
Release image and going back#
Flashing needs no buttons. Open the board’s USB port at 1200 baud, then write the merged image with esptool 5.6.0 or later. docs/MOSAICO.md has the commands. The merged image erases the NVS partition, so the pairing with the desktop app, the saved Wi-Fi networks and the settings go, and you pair again. The drive logs on the NAND and the flash FAT’s state files are not written.
The released image is OpenCarMind-EdgeOS-2.1.0-ESP-Mosaico-ESP32-S31-merged.bin on the EdgeOS 2.1.0 release, with an app-only image and SHA256SUMS beside it. To keep the pairing and settings, write only the app parts, as the release notes say. The 2.0.0 board check ran on EdgeOS-2.0.0-esp32s31-merged.bin, built from 4aeff43 (SHA-256 starts a225125d27f3906c), which was never published.
To go back, flash the mossREV 1.2.0 merged image the same way. Going back is not yet verified on the board.
Pair the adapter#
With no saved adapter, the board offers a new adapter only at -70 dBm or better and saves nothing until you say yes. The screen shows “OBD adapter found: <name>, signal strong. Use this adapter?” with “Not this one” and “Use this adapter”, and counts down 30 s. The pairing chapter of the manual has every question the board can ask, and Pairing safety explains the rules behind them.
First drive#
About 65 s after a start the board rates its own health. The Board page then says “Parked, health good” in green. Start the engine and drive: the board turns to Driving once the car’s computer answers and rows are logged. See First drive and the user manual.