Repository navigation
Conversation
This branch has not been deployed
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.
Adds the ESP32-C5-Touch-LCD-1.9 board profile for esp_board_manager discovery without a product-local -c directory. Custom devices retain init_skip: true; applications own initialization, shared-SPI policy, panel sequencing and gauge handling.
Updated against upstream main (including v0.1.3) and resolved both generated catalog conflicts, retaining the upstream LR1121 ePaper board. Seven profiles / fourteen builds per resolved Board Manager version are documented. The three C5 YAML files still match the product definition.
Validation:
Keep this PR draft while upstream CI and hardware-document review remain outstanding. The schematic PDF still contains Chinese notes, a resistor-reference inconsistency and crowded labels; no PCB placement/designator drawing was supplied. The product retains its local board YAML until this PR is merged, the registry publishes the profile and consuming-application verification succeeds. Flash/PSRAM configuration remains application-owned.