Skip to content

riotbuild: Upgrade ESP32 toolchain to GCC 14.2.0 #255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Apr 7, 2025
Merged

riotbuild: Upgrade ESP32 toolchain to GCC 14.2.0 #255

merged 2 commits into from
Apr 7, 2025

Conversation

gschorcht
Copy link
Contributor

@gschorcht gschorcht commented Feb 18, 2025 •
edited
Loading

This PR is required for the upgrade of the ESP-IDF SDK from version 4.4 to version 5.4. It provides the following changes:

  • upgrades ESP32 toolchain to GCC v14.2.0
  • upgrades GDB to v14.2
  • upgrades QEMU for ESP32 Xtensa based SoCs to version 9.0.0
  • adds QEMU for ESP32 RISC-V based SoCs
  • removes picolibc compilation for ESP32

The picolibc compilation for ESP32 had to be removed since it produces error on buildung the docker image.

The toolchain should work with current master.

Depends on #257

@gschorcht gschorcht requested a review from kaspar030 February 18, 2025 15:45
@gschorcht
Copy link
Contributor Author

I don't understand why the compile test for esp32-wroom-32 failed in CI. I built the riotbuild container and it works with the current master and the 2025-01 release as well.

@gschorcht
Copy link
Contributor Author

Ah, the compilation test uses the 2024.01 release branch which can't work with this release of the ESP32 toolchain. It requires at least the 2025.01 release branch.

Obviously, it seems to be related to PR #257

@gschorcht gschorcht mentioned this pull request Mar 2, 2025
Merged
7 tasks
@benpicco benpicco requested a review from mguetschow March 3, 2025 10:29
mguetschow
mguetschow reviewed Mar 3, 2025
View reviewed changes
Copy link
Contributor

@mguetschow mguetschow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll probably need to rebase on current master for the changes from #257 to be included.

@gschorcht gschorcht force-pushed the riotbuild_esp32_espressif_gcc_14.2.0 branch from 3d3b622 to f49002d Compare March 8, 2025 12:24
@mguetschow
Copy link
Contributor

Oh

Update manifest digest to 0993a39a90e0b573637ea488d51fb33ba1cbeacbfbae4a27cca2091d0873d383:
		makefiles/docker.inc.mk:8:DOCKER_TESTED_IMAGE_REPO_DIGEST := 045fd7eb54ccba2d5f4c06e8619bb1d5cd20ef96da8c6d4b7c1f9127e70adfff

looks like the build system sanity check complains about the RIOT version tagged with 2025.01 not using the latest docker image :/ @maribu

@maribu
Copy link
Member

maribu commented Mar 27, 2025

It is actually using the release branch. So just bumping the tagging in the release branch will fix the issue.

I guess we should make sure to always backport the tagging of the new docker image once it is deployed to the latest release branch.

See RIOT-OS/RIOT#21329

@maribu
Copy link
Member

maribu commented Apr 5, 2025

Btw: This should pass the CI now.

@gschorcht gschorcht force-pushed the riotbuild_esp32_espressif_gcc_14.2.0 branch from f49002d to 108123e Compare April 7, 2025 10:53
@gschorcht
Copy link
Contributor Author

@benpicco Don't we have to wait until 2025.04 is released? There was still a small compilation problem that was fixed by RIOT-OS/RIOT#21245 which is not part of the 2025.01 release.

@maribu
Copy link
Member

maribu commented Apr 7, 2025

It would be beneficial for the 2025.04 release if it would already use the new docker container.

As of now, Murdock will use the latest version for building both master as well as backports. A CI upgrade after the release has a risk to block backports. Updating now has a chance to break backports to 2025.01, but will make life easier for backports to the 2025.04 branch (including backports before the release is made due to bugs uncovered by the release tests on release candidates).

Either way, it is not optimal and the real fix would be to somehow use the tagged version of riotbuild in the CI for the release branch.

@benpicco
Copy link
Contributor

benpicco commented Apr 7, 2025

There was still a small compilation problem that was fixed by RIOT-OS/RIOT#21245 which is not part of the 2025.01 release.

That can be fixed easiely

@benpicco benpicco added this pull request to the merge queue Apr 7, 2025
@gschorcht
Copy link
Contributor Author

BTW, I have working ESP32-H2 locally with this toolchain version, but BLE is a nightmare for this variant. As usual with Espressif, they integrate external packages into their closed low-level binary libraries. For ESP32-H2 they have integrated Nimble into the BLE low-level libraries, which leads to major conflicts with the Nimble package as provided by RIOT 🙈

Merged via the queue into RIOT-OS:master with commit af25ec8 Apr 7, 2025
1 check passed
maribu added a commit to maribu/RIOT that referenced this pull request Apr 7, 2025
@maribu
makefiles/docker.inc.mk: bump tagged container
18b1aba 
This updates the tagged container due to the merge of
RIOT-OS/riotdocker#255
@maribu maribu mentioned this pull request Apr 7, 2025
Merged
maribu added a commit to maribu/RIOT that referenced this pull request Apr 8, 2025
@maribu
makefiles/docker.inc.mk: bump tagged container
5e03b99 
This updates the tagged container due to the merge of
RIOT-OS/riotdocker#255

(cherry picked from commit 18b1aba)
@maribu maribu mentioned this pull request Apr 8, 2025
Merged
Lukas-Luger pushed a commit to Lukas-Luger/RIOT that referenced this pull request Apr 14, 2025
@maribu @Lukas-Luger
makefiles/docker.inc.mk: bump tagged container
048e837 
This updates the tagged container due to the merge of
RIOT-OS/riotdocker#255
@gschorcht gschorcht deleted the riotbuild_esp32_espressif_gcc_14.2.0 branch July 30, 2025 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@maribu maribu maribu left review comments

@mguetschow mguetschow mguetschow left review comments

@benpicco benpicco benpicco approved these changes

@kaspar030 kaspar030 Awaiting requested review from kaspar030

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@gschorcht @mguetschow @maribu @benpicco