-
Notifications
You must be signed in to change notification settings - Fork 7.9k
SDK_VERSION: Use Zephyr SDK 0.17.4 #95344
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
SDK_VERSION: Use Zephyr SDK 0.17.4 #95344
Conversation
This commit updates the CI workflows to use the CI image v0.28.4, which includes Zephyr SDK 0.17.4. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
This commit updates ZEPHYR_SDK to point to the Zephyr SDK 0.17.4 release. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will also help with the SDK 1.0 work as Zephyr SDK 0.17.4 can be used to build
stand-alone binaries (like bootloaders) with picolibc and the picolibc startup code.
Just curious, why 0.17.3 was never integrated? |
It was using an incorrect version of picolibc. This version is sync'd with the Zephyr module. |
This series updates
SDK_VERSION
to point to the Zephyr SDK 0.17.4 release and updates the CI workflows to use the CI Docker image v0.28.4.The main purpose of this is to ensure that the SDK Picolibc version is synced with the Picolibc module version for Zephyr 4.2 release, which missed doing this -- once merged, this is to be backported to the
v4.2-branch
so that the upcoming Zephyr 4.2.1 release will have the same Picolibc version as the SDK 0.17.4 (i.e. ca8b6ebba5226a75545e57a140443168a26ba664).Note that, for the upcoming Zephyr 4.3 release, the next SDK release (1.0.0) will ensure that Zephyr and SDK Picolibc versions synced.