Repository navigation
sdkconfig.esp32p4: the OV5647 driver settings, carried by the module - #9
Merged
Merged
Conversation
…instead of a board
Contributor
Author
|
Proven after merge, 2026-10-05: with the camera on the Touch-LCD-4B, the generic-P4 image built with this fragment detects |
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
1 participant
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.
The two settings the OV5647 needs (the driver, and its MIPI auto-detect so
--gc-sectionsdoesn't drop the probe) lived in micropython-pydevices' Touch-LCD-4B board dir, which is being retired (step 5 of its build plan). They move here verbatim assdkconfig.esp32p4, whichbuild_mp.pyappends to any P4 build that selects cameraif.Proven 2026-10-05: both P4s (DEV-KIT and Touch-LCD-4B) built on upstream's
ESP32_GENERIC_P4with--modules allpicked this fragment up, booted, and importedcameraif. A camera capture wasn't run.