Upgrade mcu dependencies - #12647
Merged
Merged
Conversation
tronical
approved these changes
Jul 26, 2026
ogoffart
force-pushed
the
olivier/mcu-esp-hal-1.1
branch
2 times, most recently
from
July 28, 2026 12:22
dba4957 to
4d18982
Compare
Bump esp-hal to 1.1.1 and the related esp crates, and migrate the esope board off the deprecated esp-hal-embassy onto esp-rtos. esp-hal-embassy only works with esp-hal 1.0.0-rc.0, so keeping it pinned the whole crate. esp-rtos is its maintained replacement and needs embassy-executor 0.10, which cascades into bumping the whole embassy ecosystem (executor, time, sync, embassy-rp, embassy-stm32) with the matching source changes for pico2-touch and stm32u5. esp-hal 1.1 pulls riscv-rt 0.16, which conflicts with rp235x-hal's riscv-rt 0.12 in a shared lock file. Move mcu-board-support to its own workspace (excluded from the examples workspace) so each board resolves on its own via the demos workspace. PSRAM mode moves from the removed ESP_HAL_CONFIG_PSRAM_MODE env var into the PsramConfig passed to psram_allocator!. The display and touch drivers are built in init() and stored in the backend rather than stashing the whole Peripherals struct; esp-hal 1.1's Psram::new takes the PSRAM peripheral by value, so keeping the constructed drivers avoids a partial move and the unsafe PSRAM::steal workaround. The esope esp-rtos port compiles but still needs on-hardware testing.
Neither bump needs source changes: mipidsi's builder API and the models in use are unchanged, and the pico2-st7789 board keeps compiling against rp235x-hal 0.4. Verified by building the pico, pico2-st7789, esp32-s3-box-3 and m5stack-cores3 boards.
Match the versions used by mcu-board-support for the freestanding ESP-IDF C++ integration. The panic-handler/println and log-04 features and the esp_println::println! macro are unchanged; verified with a freestanding esp32s3 build of slint-cpp.
The board's panel is an ILI9342C, not an ILI9486. mipidsi 0.10 validates the interface kind per model and rejects ILI9486Rgb565 over SPI (the real ILI9486 does not support RGB565 on a serial interface), so the display init panicked with InvalidConfiguration(UnsupportedInterface). The ILI9342C supports RGB565 over SPI and has the panel's native 320x240 framebuffer size. Verified on hardware, including touch.
ogoffart
force-pushed
the
olivier/mcu-esp-hal-1.1
branch
from
July 28, 2026 13:12
963f57a to
4f52b79
Compare
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
2 participants
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.
No description provided.