Thanks to visit codestin.com
Credit goes to github.com

Skip to content

zephyr: Upgrade to Zephyr v4.0.0. #16207

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.

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

Closed
wants to merge 4 commits into from

Conversation

MaureenHelm
Copy link
Contributor

@MaureenHelm MaureenHelm commented Nov 10, 2024

Summary

Updates the Zephyr port to the latest Zephyr release tag. It's currently a release candidate, not a final release, therefore this PR is in draft status until the Zephyr release is finalized. Zephyr v4.0.0 was released on 15 Nov 2024.

Testing

Tested on max32690fthr and frdm_k64f boards.

Zephyr v4.0.0 changed thread analyzer functions to pass a cpu argument
and allow thread analysis on each cpu separately. Promote this change to
the MicroPython zephyr module.

Signed-off-by: Maureen Helm <[email protected]>
Copy link

codecov bot commented Nov 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.57%. Comparing base (5dfbd43) to head (470dcb3).
Report is 562 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #16207   +/-   ##
=======================================
  Coverage   98.57%   98.57%           
=======================================
  Files         164      164           
  Lines       21345    21345           
=======================================
  Hits        21041    21041           
  Misses        304      304           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

@dpgeorge
Copy link
Member

The CI is failing with:

/micropython/ports/zephyr/main.c:100:50: error: 'CONFIG_SDMMC_VOLUME_NAME' undeclared

Zephyr v4.0.0 removed CONFIG_SDMMC_VOLUME_NAME and set the disk name
based on a devicetree property to allow multiple instances of the
sdmmc_subsys disk driver to be registered. All in-tree zephyr
definitions of the devicetree property are set to "SD", therefore we use
this constant string when initializing the MicroPython VFS.

Unfortunately I don't have hardware to verify that this change works
correctly at runtime; I can only verify that it resolves a build error
found when upgrading to MicroPython to Zephyr v4.0.0.

Signed-off-by: Maureen Helm <[email protected]>
Upgrades CI to use the latest versions of the Zephyr docker image and
Zephyr SDK.

Signed-off-by: Maureen Helm <[email protected]>
Updates the Zephyr port build instructions and CI to use the latest
Zephyr release tag.

Tested on max32690fthr and frdm_k64f.

Signed-off-by: Maureen Helm <[email protected]>
@MaureenHelm MaureenHelm marked this pull request as ready for review November 16, 2024 17:11
@MaureenHelm
Copy link
Contributor Author

@dpgeorge not sure what's wrong with the windows builds or why this PR would cause them to fail. can you take a look?

@MaureenHelm MaureenHelm changed the title zephyr: Upgrade to Zephyr v4.0.0-rc3. zephyr: Upgrade to Zephyr v4.0.0. Nov 23, 2024
@dpgeorge
Copy link
Member

Merged as part of #16879 in commit 3c8d1b1

@dpgeorge dpgeorge closed this Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants