zephyr: Track mainline zephyr - #15891
#15891Closed
Ayush1325 wants to merge 8 commits into
Closed
zephyr: Track mainline zephyr#15891Ayush1325 wants to merge 8 commits into
Ayush1325 wants to merge 8 commits into
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #15891 +/- ##
=======================================
Coverage 98.54% 98.54%
=======================================
Files 169 169
Lines 21855 21855
=======================================
Hits 21536 21536
Misses 319 319 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Code size report: |
Ayush1325
force-pushed
the
upstream
branch
3 times, most recently
from
October 19, 2024 07:44
80aec05 to
de9989f
Compare
- Seems upstream zephyr broke this API after 3.7.0. Since for bcf, some stuff is not present in 3.7.0, it is important to build against latest. Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- Not using latest container images or sdk since they generally work fine across zephyr versions. And is better for caching. Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- Enable Analog inputs - Requires Zephyr v3.8.0 Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- Implement PWM support using standard zephyr APIs Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- Enable PWM config for bcf. - Needs Zephyr 3.8.0 Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- Add docs for PWM support Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- Enable support for FLASH and IEEE802154 subg radio - Requires Zephyr v3.8.0 Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Member
|
See related #16770. |
The (deprecated) kconfig option NET_SOCKETS_POSIX_NAMES was removed in commit abad505bdeed6102061767f45acd63323973f564 so remove it from our configuration. As the option has been deprecated longer, this also works for v3.7 and v4.0 the other still supported versions. Signed-off-by: Detlev Zundel <dzu@member.fsf.org>
Member
|
Zephyr 4.0.0 is now supported, see #16879. |
Contributor
Author
Great. I am closing this PR now. Will create PRs for all boards that are supported by zephyr 4.0.0 separately. |
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
3 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.
Summary
The purpose of this PR is to track mainline zephyr for micropython zephyr port. It provides a base for upcoming Zephyr boards that are not supported in a stable Zephyr version yet.
The reason for creating this is because in the past, BeagleBoard.org has maintained different forks for upcoming boards, which ended up becoming unmaintained with time due to having low manpower. So this PR also is sort of testing ground and staging for upcoming (and existing) boards from BeagleBoard.org, which already do have some random fork.
It can also help with supporting the latest version of Zephyr in the future.
This is built on top of the amazing work #9335
Plans
The boards that are planned to be used for testing are the following:
Currently, the plan is to keep this as a Draft and create new PRs to move the board support to upstream once we support some future v3.8.0 of Zephyr or something.