-
Notifications
You must be signed in to change notification settings - Fork 7.6k
west.yaml: update hal_rpi_pico to be based on Pico SDK 2.1.0 #84204
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
Conversation
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
@ajf58 |
@ajf58 thanks for the note, but FYI this is handled automatically by the Manifest GitHub action, which will add a DNM label until the PR points to a SHA (which implies that the module PR has been merged). |
e5254b5
to
2be2514
Compare
This version of the HAL is based on the 2.1.0 release of the Raspberry Pi Pico SDK. Update `modules/hal_rpi_pico/CMakeLists.txt` to add the new include directories to the build. See https://github.com/raspberrypi/pico-sdk/releases/tag/2.1.0 for more information. Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com> Signed-off-by: Andrew Featherstone <andrew.featherstone@gmail.com>
Changes introduced in 293b9a1 didn't verify correct behaviour when running `TIMER1` with `TIMER0` is paused, and was reporting the wrong tick counter being incremented. Correct this and extend the testing to verify correct behaviour. Signed-off-by: Andrew Featherstone <andrew.featherstone@gmail.com>
2be2514
to
7a89fd7
Compare
Latest push is a rebase off an updated |
This should not be merged until zephyrproject-rtos/hal_rpi_pico#8 has been approved .
Summary
hal_rpi_pico
to the 2.1.0 release. This brings in a number of bugfixes and improvements.rpi_pico_timer
. Updating the HAL to use a newer version of the SDK brings in a bugfix in the SDK, which in turn exposes a bug in therpi_pico_timer
. Fix the bug and extend the test coverage to confirm and verify this.This PR supersedes #82680
Testing
Locally tested against the Raspberry Pico 2, with no regressions identified. Build-only testing for a couple of RP2040-based boards with no issues found.
Fixes #82452