Writing · Checklist
From a Spectra 6 dev kit to a product: the checklist
An ESP32 + Spectra 6 development board proves that the panel can show your content. It does not prove that a hundred of them will keep doing it on a shelf, on battery, with nobody watching. These are the twelve things we check before a design leaves the bench — most of them learned the hard way on our own product.
Published 2026-11-09. Every item here comes from the firmware and hardware we ship in 8frames and adapt for customer products. For the panel-level details — SPI modes, power budget, LUTs, dithering — read the companion ESP32-S3 + Spectra 6 field guide first.
The dev kits people start on
There is now a healthy range of ESP32-S3 boards with Spectra 6 panels attached. We build on Good Display’s ESP32E6-E01 (7.3″ GDEP073E01, 800×480) and ESP32-133C02 (13.3″ GDEP133C02, 1200×1600), both on ESP32-S3-WROOM-1-N16R8 modules. Smaller and maker-oriented options exist too — M5Stack’s PaperColor pairs a 4-inch Spectra 6 panel with an ESP32-S3 and a 1,250 mAh battery, and Good Display positions its ESP32-133C02 board for prototype development.
What a dev kit is for: Proving the panel, the color, and your content pipeline. Not proving battery life, field recovery, provisioning, or manufacturability — the board was designed for a bench, with a USB cable attached.
The checklist
| # | Check | Why it bites | What production needs |
|---|---|---|---|
| 01 | Final flash partition table | OTA updates the app, not the partition table. Ship the wrong layout and every field unit is stuck with it. | Freeze partitions (OTA slots + storage) before the first unit leaves the bench. |
| 02 | Wake source on an RTC-capable pin | Only RTC GPIOs can wake an ESP32-S3 from deep sleep. On the ESP32E6-E01 that is one button. | Route the wake button to an RTC pin on your PCB. |
| 03 | PMIC configured, not defaulted | Power-bank chips can cut output at light load — i.e. when your device sleeps. | Configure at every boot, read registers back, log the result. |
| 04 | Black-box log | A battery device has no serial cable in the field. | Persist boot stage, reset reason, battery mV; upload with each sync. |
| 05 | Provisioning without an app | Store staff will not install your app to join Wi-Fi. | Captive portal on a per-device SSID; test odd SSIDs. |
| 06 | Factory reset gesture | Lost Wi-Fi credentials otherwise mean a USB cable and an engineer. | Defined button gestures (e.g. long hold) that a non-engineer can do. |
| 07 | Offline content buffer | Wi-Fi drops; the sign should still do its job. | Cache several frames in flash and replay them. |
| 08 | Change detection on sync | Re-downloading unchanged images burns radio time. | Send content tags (etags); only fetch what changed. |
| 09 | One codebase, several panels | 7.3″ and 13.3″ have different frame sizes and drivers. | Panel behind an interface; panel chosen at compile time. |
| 10 | Ghosting policy | Pre-clearing removes ghosting but doubles refresh time. | Decide per product; make it a setting. |
| 11 | Waveform tuning per panel lot | Stock waveforms drift reds and yellows across lots. | Tune on a first-off unit per lot; bake into firmware. |
| 12 | Certification path | A custom radio design means a full intentional-radiator filing. | Use a pre-certified module so you file a lighter package. |
The ones that deserve more than a table row:
1. Freeze the partition table before the first field unit
Our 16 MB layout is two 3 MB OTA app slots plus roughly 9.9 MB of LittleFS for cached images. Over-the-air updates rewrite the app slot; they do not rewrite the partition table. We learned what that means: a device that was first flashed with an older, smaller layout gets new firmware that expects more storage, and file writes can fail without the library reporting it. Our firmware now checks at boot whether storage can hold even one frame and refuses to pretend otherwise — but the only cure is a USB reflash. Decide the final layout while the units are still on your bench.
2. Put the wake button on an RTC-capable pin
An ESP32-S3 in deep sleep can only be woken by its RTC-domain GPIOs. On the ESP32E6-E01, four user buttons are wired, and only one of them (IO9) is RTC-capable — so only one can wake the board. On your own PCB, choose the pin on purpose. It also matters which level the button drives: the 13.3″ board’s buttons pull high where most pull low, and our firmware has to know which.
3. Configure the power-management chip yourself
The 13.3″ board carries an IP5306 power-bank PMIC. Our early firmware never configured it, so it ran on power-on defaults — and a chip in that family can switch its boost output off when the load gets light, which is exactly what a sleeping e-paper device looks like. A frame went dark overnight. We now write the control registers at every boot, read them back, and log the result. If your design has any charger or boost IC, test it at sleep current, not just at refresh current. Our battery-life write-up covers the rest of the power budget.
4. Build a black box before you need one
On battery, a panic, brownout or mid-refresh power loss leaves no trace except “the picture stopped changing”. Our firmware keeps the boot stage, battery voltage at boot and its minimum during the panel refresh, and a BUSY-timeout count in RTC memory that survives deep sleep and resets, writes a one-line summary of each boot to flash, and sends the last few lines with every cloud sync. Repeated identical brownout boots collapse into one line so the log does not fill. This is what turns field returns into fixes.
5. Provisioning that works for any SSID
First boot brings up a per-device access point, a DNS catch-all so phones open the captive portal automatically, and a small page with a network list and password field. We hand-rolled it after a popular provisioning library mangled saved network names containing an apostrophe — a network called “Jung’s Home” was truncated on the next portal visit — and the rewrite also saved about 60 KB of flash. Test the network names your customers actually use.
6. A factory reset a store manager can do
Our wake button classifies a press as a single tap, a double tap or a six-second hold, and the firmware maps those to actions: advance the content, reboot, or factory reset. No laptop, no cable, no engineer on site.
7. Keep content on the device
Each image slot is about 384 KB on the 7.3″ and 960 KB on the 13.3″. With the 16 MB layout that is up to 24 cached slots on the 7.3″ and around ten on the 13.3″, so the device keeps rotating through scheduled content when Wi-Fi is down, and resyncs with content tags when it comes back so unchanged images are not downloaded again.
8. Decide your ghosting policy
A white pre-clear before each new image removes the faint bleed of the previous one, at the cost of roughly doubling the update — about 30 seconds becomes about 60 — and an obvious white flash. For a gallery-style product, that may be right. For a shelf sign that updates while shoppers watch, maybe not. Make it a setting rather than a hard-coded choice.
What comes after the checklist
With those settled, the remaining work is the product itself: your enclosure and mounting, your content system, and your certification and manufacturing path. Our standard process runs a reference-derived PCB spin, a firmware and cloud fork into your GitHub org, and a working unit on your desk in six weeks, followed by small-batch runs or a DFM package for your contract manufacturer. What the product is for shapes most of the remaining decisions — see how this plays out for retail shelves, workplace signage and industrial labels. If you are still weighing panel technology, start with Spectra 6 vs the alternatives.
FAQ
Which ESP32 Spectra 6 development board should we start with?
Start with the board that matches your target panel size. We build on Good Display’s ESP32E6-E01 for the 7.3-inch GDEP073E01 and the ESP32-133C02 board for the 13.3-inch GDEP133C02, both on ESP32-S3-WROOM-1-N16R8 modules. Smaller kits like M5Stack’s 4-inch PaperColor are fine for proving the panel, but plan to change boards for production.
Can we ship the dev board in a custom enclosure?
For a 10–50 unit proof of concept, often yes — that is how our smallest engagements start. For volume, you want your own PCB: dev boards carry connectors, buttons and bridges you do not need, and you cannot choose which pins wake the device or how the power path behaves.
What is the most common mistake moving from dev kit to field units?
Shipping before freezing the flash partition table. Over-the-air updates replace the app image, not the partition layout, so a device shipped with too little storage stays that way until someone reflashes it over USB.
How long does it take to go from a Spectra 6 prototype to production?
Our process puts a working custom prototype — PCB spin, firmware and cloud fork — on your desk six weeks from kickoff, because we adapt a stack that already ships rather than designing one. Manufacturing hand-off follows from there, either as small-batch runs by us or a DFM package for your contract manufacturer.
Do we need FCC and CE certification for an ESP32 e-paper product?
Yes, for sale in those markets. Building on an ESP32-S3 module that already carries FCC and CE modular certification avoids a full intentional-radiator filing and turns it into a much lighter compliance package.