Skip to content

Enable ModuleDisplay on CoreP4X - #440

Merged
lovyan03 merged 1 commit into
m5stack:developfrom
ainyan03:moduledisplay_write_only
Nov 7, 2026
Merged

lovyan03 merged 1 commit into
m5stack:developfrom
ainyan03:moduledisplay_write_only

Conversation

@ainyan03

@ainyan03 ainyan03 commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Enables ModuleDisplay on CoreP4X in M5.begin().

  • Adds board_M5CoreP4X to the ESP32-P4 boards that set up ModuleDisplay.
  • Passes the board M5Unified adopted (detected, fixed or fallback) to M5ModuleDisplay::config_t::board unless the user set it. M5GFX selects the wiring and the write-only transmitter path from that board.

Requires m5stack/M5GFX#407 (adds config_t::board and the write-only transmitter path). The ModuleDisplay block is only compiled when M5ModuleDisplay.h is included, so the CI examples build without it; the combination was verified with the full build matrix locally.

Verified

  • CoreP4X + ModuleDisplay: M5.begin() adds the display; output from a cold start, from a reset, and after sleep/wakeup. Without the module M5.begin() returns with one display.
  • Tab5X + ModuleDisplay: unchanged.

Add CoreP4X to the ESP32-P4 boards that set up ModuleDisplay in M5.begin(), and pass the board M5Unified adopted (detected, fixed or fallback) to M5ModuleDisplay::config_t::board unless the user set it. M5GFX selects the wiring and the write-only transmitter path from that board.
@lovyan03
lovyan03 merged commit 5bbfe89 into m5stack:develop Nov 7, 2026
31 checks passed
@ainyan03
ainyan03 deleted the moduledisplay_write_only branch November 7, 2026 19:47
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