Skip to content

board_spec: correct StopWatch / Dial / StickCPlus storage and fix the host test - #323

Merged
lovyan03 merged 2 commits into
m5stack:developfrom
ainyan03:board_spec_storage
Sep 30, 2026
Merged

lovyan03 merged 2 commits into
m5stack:developfrom
ainyan03:board_spec_storage

Conversation

@ainyan03

Copy link
Copy Markdown
Contributor

Two small fixes to the board specification catalog.

Storage entries

Board Before After
StopWatch PSRAM 0 MB PSRAM 8 MB (octal), flash 16 MB, PSRAM pins 26–37
Dial (ESP32-S3FN8) no storage entry no PSRAM, flash 8 MB
StickCPlus (ESP32-PICO-D4) no storage entry no PSRAM, flash 4 MB

Values were read from the hardware: the ESP32 Arduino core's chip report (flash chip size, PSRAM size). On StopWatch the quad PSRAM driver fails to start ("PSRAM chip is not connected, or wrong PSRAM line mode") and the octal one brings up 8 MB. The PSRAM pin roles follow the other ESP32-S3 octal PSRAM boards (e.g. AtomS3R). generated/resolved and the editor bundle are regenerated.

Host test

power2101 now starts by disabling the AXP2101 DCDC protections (REG 0x23), but the legacy sequence in test/ops_host.cpp still had 5 steps, so the C++ host suite no longer compiled (static_assert 5 vs 6). The legacy sequence gets the same first step.

Checks

  • npm test: 160 tests, 160 pass (before: the C++ host suite fails)
  • node cli/spec.js check: OK

StopWatch carries 8 MB of octal PSRAM and 16 MB of flash (the quad PSRAM
driver fails to start on it); it was listed without PSRAM. Dial (ESP32-S3FN8)
and StickCPlus (ESP32-PICO-D4) had no storage entry; record that they have no
PSRAM and 8 MB / 4 MB of flash.
power2101 now starts by disabling the DCDC protections (REG 0x23), so the
legacy sequence the host test compares against needs the same first step;
the C++ host suite no longer compiled (operation count 5 vs 6).
@lovyan03
lovyan03 merged commit 9e38bac into m5stack:develop Sep 30, 2026
29 checks passed
@ainyan03
ainyan03 deleted the board_spec_storage branch October 1, 2026 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants