Expand description
M5Stack PPS module (SKU U136) driver, I2C address 0x35.
The module serves one RAM register bank; reads auto-increment through it and
writes land in it. The full map, who writes what, and the bus timing it was
measured with are in docs/pps-register-map.md. This driver touches only
0x00..=0x1F:
| Addr | Bytes | Register | Writer |
|---|---|---|---|
| 0x00 | 2 | module ID, always 0x1041 | module |
| 0x04 | 1 | ENABLE, 0 = output off | host |
| 0x05 | 1 | running mode 0 off / 1 CV / 2 CC | module, after it switched the output |
| 0x07 | 1 | FLAG, +1 per measurement refresh (~16 Hz), wraps | module |
| 0x08..=0x17 | 4 × f32 | output V, output A, °C, input V | module |
| 0x18..=0x1F | 2 × f32 | voltage set, current set | host |
The module applies the setpoints whether or not the output is enabled, and does NOT reject out-of-range ones: the caller clamps.
Two bus properties shape every caller (measured, 2026-10-17): the module
holds SCL for 100-200 us while it copies the bank for a read, and it NACKs a
transaction addressed right after another one ended. See crate::io::pps.
Structs§
Enums§
Constants§
- ADDRESS
- The module’s I2C address as shipped.
- MODULE_
ID - Module ID at registers 0x00/0x01, hardcoded by the module’s own firmware
(https://github.com/m5stack/M5Module-PPS-Internal-FW
Core/Src/i2c_comm.c).