Recognize CoreS3-SE FT6336U touch identity - #277
Open
marosell wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
Hardware reference: https://docs.m5stack.com/en/core/M5CoreS3%20SE