Draft
Conversation
Owner
Author
|
Tested on staging from PIO local build |
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.
This adds the C5 devkit, with 2.4GHz and 5GHz WiFi 6 support.
The C5 flashed fine with platformio but had a similar issue flashing CI assets to the C6 when esptool wasn't pinned. Also now that we aren't pinned for lvgl, it felt like a good time to revisit using the latest BSP and ESPtool, previously held up by the flash args issue for the C6.
Our merged bin was suggested as having the wrong flash args causing the ets loader issue, and looking at the arduino-IDE output for the C5 it uses "keep" as the args after the initial setup of the bootloader (elf2image from a qio_80m.elf bootloader but using DIO flash arg to generate bootloader even though flash mode was QIO from the FQBN string) and app partition.