Skip to content

Add support for Adafruit Metro ESP32-S3 + 2.8" TFT shield#78

Open
ladyada wants to merge 1 commit into
espressif:masterfrom
ladyada:add-metro-esp32s3-tft-shield
Open

Add support for Adafruit Metro ESP32-S3 + 2.8" TFT shield#78
ladyada wants to merge 1 commit into
espressif:masterfrom
ladyada:add-metro-esp32s3-tft-shield

Conversation

@ladyada

@ladyada ladyada commented May 14, 2026

Copy link
Copy Markdown

Description

Adds support for the Adafruit Metro ESP32-S3 paired with the 2.8" TFT FeatherWing shield — board info, devices, peripherals, sdkconfig defaults, setup_device, and a firmware-manifest entry for the web flasher.

This re-opens @FoamyGuy's original work from #44 (which was closed pending CLA). I'm submitting it under my own CLA so it can land.

Testing

Per the original PR: tested by building and flashing onto Metro S3 + 2.8" TFT Shield. Also tested web flasher via GH Pages in a fork.

Adds board definition files (info, devices, peripherals, sdkconfig
defaults, setup_device) for the Adafruit Metro ESP32-S3 paired with
the 2.8" TFT FeatherWing shield, and registers the board in the
web flash tool firmware manifest.
@CLAassistant

CLAassistant commented May 14, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@laride

laride commented May 15, 2026

Copy link
Copy Markdown
Collaborator

Thanks for the PR and for adding support for this new development board!

Could you please revert the changes to docs/src/flash-tool/firmware.json and rebase this PR onto the latest master branch?

Also, if the USB interface on this board is used as Serial JTAG, please add the following configuration to sdkconfig.defaults.board:

# USB: Serial JTAG
CONFIG_ESP_CONSOLE_USB_SERIAL_JTAG=y
CONFIG_ESP_CONSOLE_SECONDARY_NONE=y

If the USB interface is connected through a USB-to-UART bridge instead, then no modification is needed — please just help confirm which configuration this board is using.

Thanks!

@FoamyGuy

Copy link
Copy Markdown

@laride If the board is removed from docs/src/flash-tool/firmware.json does that mean that it won't be listed on the web flasher for being able to install to this device? Adding an entry for the board in that file caused it to appear in the flasher in our testing. Is there some automated process that populates that file instead of manual editing?

We'll work on the serial config change. The USB is direct, no bridge chip.

@laride

laride commented May 21, 2026

Copy link
Copy Markdown
Collaborator

docs/src/flash-tool/firmware.json is just a placeholder used so the docs build tests can still pass when firmware.json has not been generated yet. The actual firmware.json is generated by our CI pipeline.

For online flashing support, the board needs to be added to our CI build process. We’ll update the configuration when the PR adding the new board is merged, so there’s nothing you need to do on your side.

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.

4 participants