M5Stack Cardputer Zero Volume 1 — Overview, Family Lineage, and Decision Tree — M5Stack Cardputer Zero · Hacking

What it is (hypothesized), where it sits in the Cardputer family, vs-ADV buy-or-skip decision tree, the research-baseline framing for the whole series

Section	Topic
1	About this volume
2	Research-baseline disclosure
3	What the Cardputer Zero (presumably) is
4	The Cardputer family — lineage diagram
5	Hypothesis matrix — full hardware speculation
6	Hardware-decision consequences (the load-bearing speculation)
7	Decision tree — buy Zero, buy ADV, or wait
8	Capability matrix — Zero (presumed) vs siblings
9	Use cases that would justify a Zero
10	Comparison to sibling tools in the lineup
11	What to confirm before purchase
12	Depth indices into Vols 2-12
13	Resources

1. About this volume

This is the overview volume of a twelve-volume research-baseline deep dive into the M5Stack Cardputer Zero — the hypothesized budget / education / entry-level variant of M5Stack’s Cardputer family. The series is built on the assumption that the Zero exists or will exist, but explicitly does not assume any specific hardware spec until vendor confirmation lands.

This volume’s job is to:

Anchor the family lineage — show where Zero fits between the original Cardputer (K132) and the Cardputer ADV (K132-Adv) (§ 4)
Make every hardware hypothesis explicit — every claim about Zero’s hardware in this entire series has a confidence rating; see § 5 for the master hypothesis table
Frame the buy-vs-skip decision — § 7 has the decision tree; mostly a function of (a) does Zero even exist, (b) does it have features Zero-tier buyers actually need
Cross-reference Cardputer ADV throughout — most operational content in subsequent volumes carries forward unchanged from the ADV deep dive

Cross-reference discipline: this series leans heavily on ../../../M5Stack Cardputer ADV/03-outputs/Cardputer_ADV_Complete.html. For anything that’s “same as Cardputer ADV”, the volume cites the cross-reference rather than re-authoring. The Zero-specific content focuses on the deltas — what the Zero subtracts from the ADV, what budget/education use cases gain from those subtractions, and how the firmware ecosystem adapts.

2. Research-baseline disclosure

This is the single most important section of the deep dive. Read it before treating anything else as authoritative.

As of 2026-05-13:

No authoritative source confirms the Cardputer Zero is a shipping M5Stack product
No vendor product page has been verified on shop.m5stack.com for a SKU named “Cardputer Zero”
No M5Stack documentation entry has been verified on docs.m5stack.com
The “Zero” name itself could be:
- A real but unreleased SKU (M5Stack’s typical naming pattern; possible but unconfirmed)
- A community nickname for an existing or planned product
- A speculative name (tjscientist’s working assumption)
- A misnomer for something with a different official name

What we are reasonably confident about:

M5Stack ships budget variants of many product lines using the “Zero” or “Lite” naming conventions (e.g., ATOM Zero / Lite siblings to ATOM Matrix)
The Cardputer family currently consists of the original (K132, 2024) and the ADV (K132-Adv, 2025/2026)
A budget variant of the Cardputer would have plausible commercial reasons (education market, fleet ops, geographic pricing)
If a Cardputer Zero exists, it would almost certainly be ESP32-S3 family with a QWERTY keyboard — the defining Cardputer feature

What we are explicitly NOT claiming:

That the Zero has any specific battery capacity, display size, expansion connector, or audio subsystem
That the Zero is priced at any specific point
That the Zero is currently available for purchase
That any specific firmware build targets the Zero

Reader discipline: every spec table in this deep dive has a “Confidence” column. Low confidence means “the inference is plausible but not verified”; Medium means “vendor pattern strongly suggests this but verification is needed”; High means “this follows from being any Cardputer-family member” or “this is logically necessary for the SKU to be useful”. There are no specs marked Confirmed in this series until the product is verified.

3. What the Cardputer Zero (presumably) is

The M5Stack Cardputer Zero is hypothesized to be a budget-tier handheld in the Cardputer family. Plausible role positions:

Education tier: lower-cost device for school kits, embedded-systems classrooms, hackathon giveaways
Fleet-ops tier: cheaper deployable units for engagements that lose / damage / consume devices
Geographic / regional pricing tier: a SKU available in markets where the ADV is unaffordable
Feature-subset tier: when EXT-bus expansion isn’t needed, a stripped variant at lower cost

Sold as (hypothesis): a single-board credit-card-sized handheld with at minimum:

ESP32-S3 family MCU
56-key QWERTY membrane keyboard (the defining Cardputer feature; presumed retained)
Small color IPS display (probably 1.14” 240×135 if matching family pattern)
USB-C charging + data
microSD slot (presumed; critical for firmware ecosystem)
Grove HY2.0-4P expansion (presumed; M5Stack-universal)
Smaller LiPo battery than the ADV’s 1750 mAh (likely 500-1000 mAh)
Speaker (presumed; cheap to include)

Hypothesized to omit (vs the ADV):

14-pin EXT expansion bus (the ADV’s defining feature)
Cap LoRa-1262 compatibility (consequence of no EXT bus)
ES8311 audio codec (might be replaced by simple GPIO PWM speaker + no jack)
3.5 mm audio jack
MEMS microphone
IR LED transmit (cheap but maybe cut)
BMI270 6-axis IMU
Magnetic LEGO-Technic base (less consequential)

The single most consequential subtraction: the EXT bus. Vol 4 § 2 covers the cascading consequences of this in detail.

[FIGURE SLOT — Vol 1, § 3] Vendor hero photo of Cardputer Zero front view (showing QWERTY + display + general form factor). Source: Photo Helper search “M5Stack Cardputer” or vendor product page on shop.m5stack.com once confirmed. Caption when filled: “Figure 1.1 — M5Stack Cardputer Zero front view. Photo: [source].“

4. The Cardputer family — lineage diagram

Where Zero (presumably) sits relative to its siblings:

   M5Stack Cardputer family — lineage as of 2026-05-13
   ═══════════════════════════════════════════════════

                  ┌─────────────────────────┐
                  │   ESP32-S3 family       │
                  │   QWERTY + IPS display  │
                  │   handheld credit-card  │
                  └────────────┬────────────┘
                               │
                  ┌────────────┴────────────┐
                  │                         │
                  │                         │
            ┌─────▼──────┐         ┌────────▼────────┐
            │ Cardputer  │         │ Cardputer ADV   │
            │ (K132)     │         │ (K132-Adv)      │
            │ 2024       │         │ 2025-2026       │
            │            │         │                 │
            │ ESP32-S3   │         │ ESP32-S3FN8     │
            │ PICO       │         │ Stamp-S3A       │
            │ 1.14" LCD  │         │ 1.14" LCD       │
            │ Grove      │         │ Grove + 14-pin  │
            │ 1500 mAh   │         │   EXT bus       │
            │ ~$45       │         │ 1750 mAh        │
            │            │         │ ES8311 codec    │
            │            │         │ MEMS mic        │
            │            │         │ BMI270 IMU      │
            │            │         │ IR TX           │
            │            │         │ ~$60            │
            └────────────┘         └─────────────────┘
                                            │
                                            │
                                    ┌───────▼─────────┐
                                    │ Cardputer Zero  │
                                    │ (hypothesized)  │
                                    │ "K132-Zero"?    │
                                    │                 │
                                    │ ESP32-S3 family │
                                    │ ? display       │
                                    │ Grove only      │
                                    │ ~500-1000 mAh   │
                                    │ Speaker only?   │
                                    │ ? IR / ? IMU    │
                                    │ ~$30-40?        │
                                    └─────────────────┘
                                       UNCONFIRMED

The Zero (if it exists) is positioned as a subset of the ADV, not a sibling of equal capability — that’s the hypothesis. The original Cardputer K132 is the closer-feature peer for the Zero, but the Zero (presumed) would aim for an even tighter cost target.

5. Hypothesis matrix — full hardware speculation

Every hardware claim in this series traces back to this table. Confidence ratings: High (logically follows from being a Cardputer); Medium (vendor pattern strongly suggests); Low (plausible but unverified).

Aspect	Hypothesis	Confidence	Rationale / what to verify
Existence	Product exists or will exist	Low	”Zero” naming convention used elsewhere in M5Stack portfolio; no vendor confirmation
SKU	K132-Zero	Low	Family naming pattern; not verified
MCU	ESP32-S3 family	Medium	All Cardputer family members are ESP32-S3; Zero unlikely to break this
Specific MCU package	ESP32-S3FN8 (8 MB flash) or PICO-1-N8R2	Low	Budget variants often drop PSRAM; could be either
Flash size	8 MB	Medium	Cardputer family standard
PSRAM	None or 2 MB	Medium	ADV omits PSRAM; Zero almost certainly also omits
Display	1.14” 240×135 IPS (ST7789-class)	Medium	Matches family; budget variant could downgrade to OLED or smaller
Display controller	ST7789V2	Medium	Family pattern
Keyboard	56-key membrane QWERTY	High	Defining Cardputer feature; impossible to call it a Cardputer without
Keyboard scanner	TCA8418 or GPIO scanning	Medium	ADV uses TCA8418; budget variant could go GPIO direct
Battery	500-1000 mAh LiPo	Medium	Budget variants reduce battery; smaller cell is cost win
Charge controller	TP4056-class	High	Standard handheld topology
USB	USB-C	High	Industry standard; M5Stack convention
Storage	microSD (Class 10 / U1+)	Medium	Critical for firmware ecosystem; presumed retained
Grove HY2.0-4P	Yes	High	M5Stack universal; cost-trivial to include
14-pin EXT bus	No	Medium	The single defining ADV feature; budget variant most likely cuts it
IR LED transmit	No or Yes	Low	Cheap to include; could go either way
BMI270 IMU	No	Medium	Budget variant likely cuts
ES8311 audio codec	No	Medium	Cost cut; replaced by simple speaker
MEMS microphone	No	Medium	Cost + privacy posture; likely cut
3.5 mm audio jack	No	Medium	Audio chain reduced
Speaker	Yes (passive or class-D)	High	Useful + cheap
LED indicators	Yes (LiPo charge LED)	High	Standard
Magnetic LEGO base	Maybe	Low	Cute feature; could go either way
Antenna	PCB integrated (ESP32-S3 module-style)	High	Standard
Estimated price	$30-40 USD	Low	”Zero” positioning suggests budget tier
Estimated weight	35-45 g	Low	Slightly less than ADV’s ~50 g due to smaller battery
Estimated thickness	12-15 mm	Low	Similar form factor
Release date	Unknown	—	TBD entirely

Cross-checking the hypothesis: any cell marked Low confidence should be verified before purchase. The full pre-purchase verification checklist is in Vol 12.

6. Hardware-decision consequences (the load-bearing speculation)

The hypothesis matrix above is the input; this section is the output — what those hypotheses imply for the Zero’s value proposition.

6.1 If EXT bus is omitted (presumed)

Cascading consequences:

No Cap LoRa-1262 compatibility → no Meshtastic, no LoRa, no GNSS via the M5Stack Cap module ecosystem
No M5MonsterC5 attachment for 5 GHz Wi-Fi work
No future Cap module compatibility
Reduces value proposition vs ADV significantly for RF / mesh use cases

Mitigations (if Zero acquired):

Grove Unit C6L (ESP32-C6 + SX1262, standalone) for LoRa via UART
Grove + external module for whatever Cap was supposed to do
Higher BoM cost for the workarounds than Cap modules would have been

Decision marker: if your use case is mesh networking, LoRa, or GNSS-on-handheld, the Zero is the wrong tool (unless its EXT bus is later confirmed to exist).

6.2 If audio chain is reduced (presumed)

Cascading consequences:

No ES8311 codec → no high-quality audio I/O
No 3.5 mm jack → no discreet listening, no recording chain
No MEMS mic → no voice recording, no wake-word, no walkie-talkie firmware
Speaker only — fine for beeps and basic playback, not productive for audio work

Mitigations:

External USB audio interfaces possible but adds cost + bulk
Most pentest workflows don’t need audio anyway

Decision marker: if your use case is audio analysis, voice recording, or Meshtastic-with-voice, the Zero is the wrong tool.

6.3 If battery is smaller (presumed)

Cascading consequences:

Runtime per charge ~50-70% of ADV
More frequent charging in field use
Heavier dependence on USB-C battery packs

Mitigations:

USB-C battery pack for extended sessions
Plan engagements to charge windows
Acceptable for short-form / education / fleet-ops scenarios

6.4 If IR is omitted

Cascading consequences:

No universal-remote firmware
No IR-based ISM band research

Mitigations:

Add a Grove IR Unit if needed ($5-10)
Most pentest use doesn’t require IR

6.5 What’s preserved (presumed)

ESP32-S3 silicon — full programmability
QWERTY keyboard — defining feature retained
Display — visual feedback retained
microSD — firmware ecosystem retained
Grove expansion — basic peripheral path retained

The preserved feature set is enough for: general-purpose ESP32-S3 development, basic pentest workflows (Wi-Fi scanning / BLE / Marauder-class work), retro gaming, MicroHydra-based scripting, ESPHome integration, education, hackathon use.

7. Decision tree — buy Zero, buy ADV, or wait

   Are you considering an M5Stack handheld?
                    │
                    │
   ┌────────────────┴────────────────┐
   │                                 │
   │                                 │
   │                                 │
   │ Is the Zero confirmed shipping? │
   │                                 │
   └──────────────┬──────────────────┘
                  │
        ┌─────────┴─────────┐
        │                   │
       NO                  YES
        │                   │
        ▼                   ▼
  ┌──────────┐      ┌──────────────────────┐
  │ Wait for │      │ Do you need LoRa,    │
  │ vendor   │      │ Meshtastic, audio,   │
  │ confirma-│      │ or EXT-bus modules?  │
  │ tion;    │      └──────────┬───────────┘
  │ consider │                 │
  │ ADV in   │         ┌───────┴────────┐
  │ meantime │         │                │
  └──────────┘        YES              NO
                       │                │
                       ▼                ▼
                  ┌─────────┐     ┌──────────────┐
                  │ Buy ADV │     │ Is budget    │
                  │ — Zero  │     │ a major      │
                  │ lacks   │     │ constraint   │
                  │ EXT     │     │ ($30 vs $60)?│
                  │ (pre-   │     └──────┬───────┘
                  │ sumed)  │            │
                  └─────────┘    ┌───────┴───────┐
                                YES             NO
                                 │               │
                                 ▼               ▼
                          ┌─────────┐      ┌──────────┐
                          │ Buy Zero│      │ Buy ADV  │
                          │ — fits  │      │ — futre  │
                          │ budget  │      │ EXT bus  │
                          │ tier    │      │ optional │
                          │ use case│      │          │
                          └─────────┘      └──────────┘

   Other purchase triggers:
   - Fleet ops (10+ units, expected loss) → Zero makes economic sense
   - Education (classroom kit, 30 units) → Zero is the right SKU
   - Single-unit "should I have a Cardputer at all" → ADV is the safer
     answer (more features, future-proof, more firmware support today)

For tjscientist’s current situation (2026-05-13): Cardputer ADV is the safer single-unit choice. Zero becomes interesting if (a) it’s confirmed to exist, (b) a specific fleet / education / budget use case lands, or (c) tjscientist wants a deliberately reduced-feature ESP32-S3 platform for a specific project.

8. Capability matrix — Zero (presumed) vs siblings

Capability	Cardputer K132	Cardputer ADV K132-Adv	Cardputer Zero (presumed)
ESP32-S3 silicon	✓	✓	✓
QWERTY keyboard	✓ (56-key)	✓ (56-key)	✓ (presumed 56-key)
Color display	✓ (1.14”)	✓ (1.14”)	✓ (presumed 1.14”)
microSD	✓	✓	✓ (presumed)
Grove HY2.0-4P	✓	✓	✓ (presumed)
14-pin EXT bus	✗	✓	✗ (presumed)
Cap LoRa-1262	✗	✓	✗ (presumed)
IR transmit	✓	✓	? (presumed reduced)
Audio in (MEMS mic)	✗	✓	✗ (presumed)
Audio out (3.5 mm jack)	✗	✓	✗ (presumed)
ES8311 audio codec	✗	✓	✗ (presumed)
6-axis IMU (BMI270)	✗	✓	✗ (presumed reduced)
Magnetic LEGO base	✗	✓	? (presumed reduced)
Speaker	✓	✓	✓ (presumed)
LiPo battery	1500 mAh	1750 mAh	500-1000 mAh (presumed)
USB-C	✓	✓	✓
Approximate price	~$45	~$60	$30-40 (presumed)
Approximate weight	~50 g	~50 g	35-45 g (presumed)
Pentest firmware support	Mature	Excellent	Likely (Marauder, Bruce port-dependent)
Meshtastic	No (no LoRa)	Yes (via Cap LoRa-1262)	No (presumed; no Cap path)
Retro gaming	Yes (MicroHydra)	Yes (MicroHydra)	Yes (presumed)
Audio recording / FFT	No (no mic)	Yes	No (presumed)
Voice walkie-talkie firmware	No	Yes	No (presumed)
Fleet-ops cost-effectiveness	OK	Good for single unit	Best (presumed, if Zero exists)

The cells marked “presumed” are the highest-uncertainty rows in the matrix; verify on receipt.

9. Use cases that would justify a Zero

Where a Zero-class SKU specifically wins over the ADV:

9.1 Education / classroom kit

A classroom of 30 students each getting a Cardputer: ADV costs $1800; Zero presumably costs ~$900-1200. The cost delta funds:

Replacement units for breakage
More accessory parts (cases, antenna, etc.)
Add-on modules for advanced exercises
Bigger budget for instructor / TA time

Verdict: if you’re teaching ESP32-S3 + embedded I/O + microcontroller programming to a class, Zero is the right SKU. The ADV’s audio + Cap features are mostly irrelevant for intro courses.

9.2 Fleet operations

Engagements that deploy 10-20 units and expect to lose / damage / consume some:

Capture units placed in field for monitoring
Conference / venue deployment (loss expected)
Hackathon participant giveaways
Sacrificial units for explosive / mechanical / chemical tests

Verdict: lower per-unit cost matters more than per-unit capability. Zero wins.

9.3 Specific feature subset deliberate choice

If you specifically don’t want / need:

LoRa (you have a dedicated LoRa device elsewhere)
Audio recording (privacy / regulatory)
IMU (not relevant to your use case)

Buying the Zero is “feature pruning” rather than “downgrading”. Saves $20+ and removes attack-surface / regulatory complexity.

9.4 Geographic / regional pricing

In markets where the ADV is unaffordable due to import costs, taxes, or local pricing: Zero might land at a price point that’s accessible.

9.5 Secondary / spare unit

If you already own the ADV: a Zero as a secondary unit (different SD card, different firmware, parallel development) at lower cost than a second ADV.

10. Comparison to sibling tools in the lineup

Sibling tool	Overlap with Zero (presumed)	Zero wins when	Sibling wins when
Cardputer ADV (K132-Adv)	Direct overlap minus EXT bus	Budget / fleet / education	Any feature in the EXT-bus path (LoRa, audio, IMU)
Cardputer original (K132)	Closest peer	Lower cost	Mature firmware support today
M5StickS3	Different form factor (stick vs card)	QWERTY workflows	Wearable + audio
Flipper Zero	Different niche entirely	ESP32-S3 + keyboard	RFID/NFC/Sub-GHz integrated
AWOK Dual Touch V3	Different role (Flipper module)	Standalone ESP32-S3 work	Wi-Fi audit firmware
Wired Hatters Banshee	Different scale	Budget tier	Multi-modal RF + dual MCU
Bus Pirate 6	Zero protocol-bring-up scope	Field portable	Bench bring-up

Zero’s niche: budget ESP32-S3 handheld with keyboard, no EXT bus, simplified audio. If that niche is what you need, it’s the right tool; if you need anything beyond it, look elsewhere.

11. What to confirm before purchase

This is the pre-purchase checklist. Do not skip these.

Verify the product exists on shop.m5stack.com or docs.m5stack.com — search “Cardputer Zero” or browse the Cardputer family page
Note the SKU (likely K132-Zero pattern; verify)
Check the spec sheet for:
- Exact MCU package (ESP32-S3FN8 vs PICO-1-N8R2 etc.)
- Flash size (4 MB? 8 MB?)
- PSRAM (none? 2 MB? 8 MB?)
- Display dimensions + controller
- Keyboard count + technology (membrane vs other)
- Battery capacity in mAh
- Expansion connectors (Grove? EXT?)
- Audio subsystem
- Sensors (IMU? IR?)
- Charging spec (USB-C with PD? simple 5 V?)
Check pricing — both vendor listing and resellers (DigiKey, Mouser, Aliexpress)
Check community discussion — r/CardPuter, M5Stack forum, cardputer.wiki — for any teardowns / reviews
Check firmware support — does M5Launcher (bmorcelli.github.io/Launcher) list a Zero target? Does Bruce? Marauder?
Check Awesome M5Stack Cardputer list — github.com/terremoth/awesome-m5stack-cardputer for any Zero-specific entries

If any of the above can’t be confirmed → don’t purchase yet. The Zero is a moving target; lock in the specs before spending.

12. Depth indices into Vols 2-12

Hardware

Hypothesized silicon block diagram → Vol 2 § 2-3
Display + keyboard subsystem → Vol 2 § 4-5
Battery + power topology → Vol 2 § 6 + Vol 5
Sensors (if any) → Vol 2 § 7
Photo Helper FIGURE SLOTS for board photos → Vol 2 throughout

External interfaces

USB-C → Vol 3 § 2
microSD → Vol 3 § 3
Grove HY2.0-4P → Vol 3 § 4
Audio (if present) → Vol 3 § 5
Antenna integration → Vol 3 § 6

Modules + expansion

Why no EXT bus matters → Vol 4 § 2
Grove Units catalog for Zero use → Vol 4 § 3
Cap module incompatibility consequences → Vol 4 § 4
Workarounds for missing Cap features → Vol 4 § 5

Power

Battery realism → Vol 5 § 2
Charging behavior → Vol 5 § 3
Per-mode current → Vol 5 § 4
Field-deployment power discipline → Vol 5 § 5

Firmware

M5Launcher on Zero → Vol 6 § 2
Pentest fork compatibility → Vol 6 § 3
MicroHydra / UiFlow / Bruce / Marauder ports → Vol 6 § 4
Education-friendly firmwares → Vol 6 § 5

Programming

Arduino + M5Cardputer library → Vol 7 § 2
PlatformIO with Zero-specific env → Vol 7 § 3
MicroPython → Vol 7 § 4
UiFlow visual programming → Vol 7 § 5

Flashing

M5Burner workflow → Vol 8 § 2
Web flashers → Vol 8 § 3
esptool.py manual flash → Vol 8 § 4
Factory backup before customization → Vol 8 § 5

Use cases + recipes

Education classroom recipes → Vol 9 § 2
Fleet-ops deployment patterns → Vol 9 § 3
Budget pentest workflows → Vol 9 § 4
Retro gaming + utility → Vol 9 § 5

Custom firmware

Mostly cross-ref to Cardputer ADV Vol 10 → Vol 10 § 2-3
Zero-specific custom hardware considerations → Vol 10 § 4

Operational posture

Regional rules → Vol 11 § 2 (inherits family)
LiPo small-cell discipline → Vol 11 § 3
Education / classroom posture → Vol 11 § 4
Legal / ethics → Vol 11 § 5

Cheatsheet

Quick-facts (hypothesized) → Vol 12 § 2
What to verify on receipt (the critical Zero-specific checklist) → Vol 12 § 3
Troubleshooting flow → Vol 12 § 9

13. Resources

Vendor

M5Stack shop: https://shop.m5stack.com/ (search “Cardputer Zero” — may not exist yet)
M5Stack docs: https://docs.m5stack.com/ (Zero-specific page TBD)
M5Stack community forum: https://community.m5stack.com/

Community

Cardputer Wiki: https://cardputer.wiki/ (likely first to add Zero entry)
r/CardPuter (Reddit): https://reddit.com/r/CardPuter/
Awesome M5Stack Cardputer: https://github.com/terremoth/awesome-m5stack-cardputer

Sibling project deep dives (the canonical references)

Cardputer ADV deep dive (the superset reference):
Cardputer ADV CLAUDE.md: ../../../M5Stack Cardputer ADV/CLAUDE.md
M5StickS3 deep dive: ../../../M5Stick S3/03-outputs/M5StickS3_Complete.html

Firmware ecosystem (inherited from Cardputer family)

M5Launcher web flasher: https://bmorcelli.github.io/Launcher/
M5Cardputer Arduino library: https://github.com/m5stack/M5Cardputer
M5Unified library: https://github.com/m5stack/M5Unified
Bruce firmware: https://github.com/pr3y/Bruce
NEMO: https://github.com/n0xa/m5stack-nemo
MicroHydra: https://github.com/echo-lalia/MicroHydra

Cross-tool references

Hack Tools comparison: ../../../_shared/comparison.md
Capability matrix: ../../../_shared/capability_matrix.html
Legal / ethics: ../../../_shared/legal_ethics.md

This is Volume 1 of a twelve-volume research-baseline series. Next: Vol 2 walks the hypothesized hardware in schematic-style detail — ESP32-S3 silicon, display, keyboard scanner, audio (if any), power tree — with explicit FIGURE SLOTS for board photos to be filled once hardware is acquired.

M5Stack Cardputer Zero Volume 1 — Overview, Family Lineage, and Decision Tree

Contents

1. About this volume

2. Research-baseline disclosure

3. What the Cardputer Zero (presumably) is

4. The Cardputer family — lineage diagram

5. Hypothesis matrix — full hardware speculation

6. Hardware-decision consequences (the load-bearing speculation)

6.1 If EXT bus is omitted (presumed)

6.2 If audio chain is reduced (presumed)

6.3 If battery is smaller (presumed)

6.4 If IR is omitted

6.5 What’s preserved (presumed)

7. Decision tree — buy Zero, buy ADV, or wait

8. Capability matrix — Zero (presumed) vs siblings

9. Use cases that would justify a Zero

9.1 Education / classroom kit

9.2 Fleet operations

9.3 Specific feature subset deliberate choice

9.4 Geographic / regional pricing

9.5 Secondary / spare unit

10. Comparison to sibling tools in the lineup

11. What to confirm before purchase

12. Depth indices into Vols 2-12

13. Resources