M5Stack Cardputer Zero Volume 3 — External Interfaces — M5Stack Cardputer Zero · Hacking

USB-C, microSD, Grove HY2.0-4P, what's NOT externally accessible, comparison vs ADV's expansion surface

Section	Topic
1	About this volume
2	USB-C — charge + data
3	microSD card slot
4	Grove HY2.0-4P port
5	What is NOT externally exposed
6	Comparison vs sibling Cardputers’ interfaces
7	Resources

1. About this volume

Vol 3 covers Cardputer Zero’s external interfaces — what you can connect to it from outside the enclosure. Far less than the ADV is the operational summary: the Zero (presumed) is USB-C + microSD + Grove only, with the EXT bus / audio jack / extras of the ADV deliberately omitted to hit the budget price point.

Cross-reference: ../../../M5Stack Cardputer ADV/03-outputs/Cardputer_ADV_Complete.html Vol 3 covers the ADV’s interfaces in detail. This volume focuses on the Zero’s interface subset + the cascading consequences of the omissions.

2. USB-C — charge + data

2.1 Physical + electrical

Aspect	Hypothesis	Confidence	Notes
Connector	USB-C female	High	Industry standard; M5Stack convention
USB version	USB 2.0 high-speed (480 Mbps)	High	ESP32-S3 native USB-CDC; sufficient for the silicon
Data role	USB-CDC (device) + USB OTG (host capable)	High	ESP32-S3 silicon
Charge input	5V / ~1 A	Medium	Standard handheld budget topology
USB-PD support	No (likely)	Medium	Budget design; PD adds cost
Cable type	USB-C to USB-A or USB-C to USB-C, data + power	High	Standard

2.2 What USB-C gives the Zero

   USB-C Functions
   ───────────────
   1. Charge battery (5V / ~1A input → TP4056 → cell)
   2. Power the device while running (no battery drain)
   3. Serial console (USB-CDC) for development + logging
   4. esptool.py firmware flash
   5. USB OTG host mode (BadUSB HID emulation)
   6. USB Mass Storage (with right firmware)
   7. M5Burner / web-flasher tool connection

USB-C is fully reversible and modern. Compare to older M5Stack products with mini-USB (legacy): the Zero (presumed USB-C) is future-proof.

2.3 USB-PD considerations

Standard 5V USB-C works regardless of PD. PD-only chargers (some MacBook 96W or USB-PD-only travel chargers) may or may not fall back to 5V — test before relying on a specific charger.

3. microSD card slot

3.1 Likely specs

Aspect	Hypothesis	Confidence	Notes
Slot type	microSD push-push or friction	Medium	Push-push more common; verify
Format	FAT32 (primary)	High	M5Stack firmware ecosystem standard
Max capacity	Up to 128 GB practical (FAT32 limit)	High	Standard
Class minimum	Class 10 / U1	Medium	Firmware ecosystem expects this
Bus	SPI (most likely) or SDIO	Medium	SPI is cost-cheaper
Power	3.3V from system bus	High	Standard

3.2 What microSD enables

Firmware updates — M5Launcher self-flash workflow uses SD
Pentest captures — captured Wi-Fi probes, BLE adverts, etc.
Bruce / NEMO / Marauder data storage — built-in firmware ecosystem
MicroHydra apps + scripts — user-installable Python scripts
UiFlow projects — visual programming project storage
General data storage — config files, logs, etc.

Without microSD: the Zero loses ~70% of its firmware ecosystem value. The slot is essentially mandatory for any serious use; it’s hard to imagine M5Stack cutting it.

4. Grove HY2.0-4P port

4.1 Likely pin assignment

Standard M5Stack Grove port — 4-pin HY2.0 connector with:

   Pin 1: GND
   Pin 2: VCC (3.3V or 5V — verify; M5Stack varies)
   Pin 3: SDA / RX / GPIO
   Pin 4: SCL / TX / GPIO

The two signal pins are dual-purpose I²C / UART / GPIO depending on configuration.

4.2 Grove Unit catalog (relevant for Zero)

Vol 4 covers the Grove Unit catalog in depth. Highlights for Zero use:

Grove Unit C6L — ESP32-C6 + SX1262 (LoRa over UART) → the Cap LoRa-1262 workaround
Grove IR Unit — adds IR TX/RX if Zero omits internal IR
Grove GPS Unit — adds GNSS over UART
Grove Environment Unit — temperature / humidity / pressure
Grove BLE Module — secondary BLE radio
Grove I²C peripherals — many

Grove is the primary expansion path; without EXT bus, Grove is the only path for adding hardware features.

4.3 Limitations vs ADV’s combined Grove + EXT path

Only one Grove port — can’t stack multiple peripherals without I²C addressing
Lower current available — 3.3V Grove typically tops out at ~200-300 mA shared
Bandwidth-limited — UART/I²C only; no SPI-speed peripherals via Grove
No direct memory expansion — can’t add storage / RAM via Grove

5. What is NOT externally exposed

This is where Zero differs from ADV most:

Interface	ADV has?	Zero has? (hypothesis)	Workaround for Zero
14-pin EXT bus	Yes	No	None — major capability gap
3.5 mm audio jack	Yes	No (likely)	External USB-C audio interface (adds bulk)
MEMS microphone	Yes (mic on EXT path)	No	Grove mic unit (limited) or external
IR LED	Yes	Maybe	Grove IR Unit
Hat (16-pin) connector	No	No	(Cardputer family doesn’t have Hat)
External antenna SMA	No (PCB integrated)	No (PCB integrated)	None on either
6-axis IMU (BMI270)	Yes	No (likely)	Grove IMU Unit

The cascading impact of “no EXT bus” is the dominant factor. Vol 4 § 4 covers this.

6. Comparison vs sibling Cardputers’ interfaces

Interface	Original K132	ADV K132-Adv	Zero (presumed)
USB-C	✓	✓	✓
microSD	✓	✓	✓
Grove HY2.0-4P	✓	✓	✓
EXT 14-pin bus	✗	✓	✗
3.5 mm audio jack	✗	✓	✗
IR TX LED	✓	✓	?
MEMS mic	✗	✓	✗
6-axis IMU	✗	✓	✗
Speaker	✓	✓	✓

The Zero (presumed) is essentially the original K132 with USB-C — minus IR (maybe) and IMU (which the K132 also didn’t have). The ADV’s value-adds (audio + EXT bus + sensors) are precisely what’s hypothesized to be cut.

7. Resources

Cardputer ADV Vol 3 (interfaces canonical): ../../../M5Stack Cardputer ADV/03-outputs/Cardputer_ADV_Complete.html
M5Stack Grove ecosystem: https://docs.m5stack.com/en/category/Unit
HY2.0-4P connector spec: M5Stack docs

End of Vol 3. Next: Vol 4 walks the module ecosystem — the cascading consequences of no EXT bus, the Grove Units catalog as the only expansion path, and the Cap module incompatibility.

M5Stack Cardputer Zero Volume 3 — External Interfaces

Contents