-
Notifications
You must be signed in to change notification settings - Fork 24
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
Zephyr make kernel clock default + improvements #400
Conversation
Also does following improvements: - Use timed wait on semaphore instead of a busy-wait for sleeping - Use Zephyr API for getting a monotonically increasing time.
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.
LGTM!
Oh, looks like macOS is failing 😞 |
But I see now that |
Yes, this should not affect macOS as we only build and test Zephyr with a Linux host |
Dont know what to make of it. No useful output from the CI and it passed when I re-ran it.. |
FYI: I added the |
The macOS test failures can not come from any changes introduced here, so there is a problem already in |
Seems to be: |
Could you mark it as failing and create an issue? |
We have had some issues with using the Zephyr Counter API as the timing service, it is implemented differently for different boards and did not work for a STM32 board which was reported by a user on Zulip. I had other similar reports also earlier. Therefore, I want to make the Zephyr Kernel time API the default, it gives less precise timing, but it is simple and supported by all boards with Zephyr.
The Counter API can still be used, if the board supports it, but it is not the default.
Docs: lf-lang/lf-lang.github.io#247
Lingua-franca: lf-lang/lingua-franca#2248