Open ajf58 opened 1 day ago
@soburi I notice that the bot has auto-assigned this to you, but I'm conscious you may be unwilling/unable to take this work on due to other commitments. Are you happy to look at this, or can this be assigned to one of a few people who've expressed an interest in contributing to Raspberry Pi support within Zephyr?
@soburi I notice that the bot has auto-assigned this to you, but I'm conscious you may be unwilling/unable to take this work on due to other commitments. Are you happy to look at this, or can this be assigned to one of a few people who've expressed an interest in contributing to Raspberry Pi support within Zephyr?
No problem.
Is your enhancement proposal related to a problem? Please describe.
Raspberry Pi Pico SDK v2.1.0 has now been released, and includes bugfixes and enhancement that are required by both in-tree and future additions to the project. See https://github.com/raspberrypi/pico-sdk/releases/tag/2.1.0
I think this would be a good first issue. The scope is well defined and local regression testing with an in-tree board (e.g. the Pico 1) would give a good level of confidence.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
N/A.