Skip to content

Recognize CoreS3-SE FT6336U touch identity - #277

Open
marosell wants to merge 1 commit into
m5stack:masterfrom
marosell:fix/cores3se-ft6336u-identity
Open

Recognize CoreS3-SE FT6336U touch identity#277
marosell wants to merge 1 commit into
m5stack:masterfrom
marosell:fix/cores3se-ft6336u-identity

Conversation

@marosell

@marosell marosell commented Sep 2, 2026

Copy link
Copy Markdown

Fixes #276.

A physical CoreS3-SE reports the FT6336U identity tuple CIPHER 0x64, FIRMID 0x03, VENDID 0x20. The current whitelist rejects it, logs a misleading read-failure warning, and falls back to ILI9342C even though all three reads succeeded.

M5Stack documents CoreS3-SE as FT6336U plus ILI9342C, so this change accepts the complete tuple as the ILI9342C variant. Existing 0x11 vendor handling and ILI9342E selection remain unchanged. It also requires the cipher register read to succeed before accepting any identity.

Hardware verification:

  • CoreS3-SE autodetection succeeds
  • display operates with the existing ILI9342C fallback
  • capacitive touch navigation operates normally
  • tested with M5GFX 0.2.27, M5Unified 0.2.20, ESP-IDF 5.5.4

Hardware reference: https://docs.m5stack.com/en/core/M5CoreS3%20SE

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.

CoreS3-SE FT6336U identity 64/03/20 triggers misleading version-read warning

1 participant