Home >

Zephyr: A Vendor Neutral Secure RTOS Option

Kate Stewart - Watch Now - Duration: 45:05

5 years ago the Zephyr project was launched at Embedded World, with the vision to deliver the best-in-class RTOS for connected resource-constrained devices, built to be secure and safe. Since then, many companies have collaborated together to create a vendor neutral solution to achieve these goals. The project has actively worked to adopt open source best practices, as well as best security practices. This talk will go into details about the practices Zephyr has adopted, and that other open source projects should consider, as we work to make the endpoints devices of the IoT ecosystem secure.
M↓ MARKDOWN HELP
italicssurround text with
*asterisks*
boldsurround text with
**two asterisks**
hyperlink
[hyperlink](https://example.com)
or just a bare URL
code
surround text with
`backticks`
strikethroughsurround text with
~~two tilde characters~~
quote
prefix with
>

DaveN
Score: 0 | 7 months ago | 1 reply

Thanks for a great OS and great talk! A few questions:

Does Zephyr provide C++ support, especially C++11 concurrency and threading support?

Can you speak to Zephyr testing on different hardware platforms?

While delivering numerous products using FreeRTOS, the bane of our development is horrific vendor-provided drivers (especially USB and Ethernet). I understand Zephyr has the protocol stacks, but what about hardware-specific drivers?

Kate StewartSpeaker
Score: 0 | 6 months ago | no reply

Sorry for the delay in response.
For C++ thread support, there is the recently merged support for https://github.com/zephyrproject-rtos/zephyr/issues/21519

For different hardware platform testing - there is a testing working group, and they focus on a core set of platforms in addition to the general testing in simulation that happens on every commit. In terms of the boards (https://github.com/zephyrproject-rtos/zephyr/tree/main/boards), different levels for each I'm afraid. More details probably best found out by joining the Zephyr slack channel and asking about specifics there.

Full details on the drivers supported can be found by going through https://github.com/zephyrproject-rtos/zephyr/tree/main/drivers, and https://docs.zephyrproject.org/latest/reference/index.html#api-reference in particular https://docs.zephyrproject.org/latest/reference/peripherals/index.html might be useful.

Cleo
Score: 0 | 7 months ago | 1 reply

Would this be useful for space applications?

Kate StewartSpeaker
Score: 0 | 7 months ago | no reply

Assuming you mean applications that go above the earth's atmosphere? Depends on the use case and certifications required, but don't see a reason why not. Its got a tight focus on minimum resource usage, which is going to be needed.

leandropg
Score: 0 | 7 months ago | 1 reply

Hi Kate. Amazing talk. I don't know all the security focus on Zephyr. Is amazing. I have a question:
Where I obtain a tutorial 101 for start with Zephyr on STM32?

Kate StewartSpeaker
Score: 3 | 7 months ago | 1 reply

We're working on a free online EdX course for providing an intro to Zephyr, which will hopefully be available before the end of the summer. We're using Renode simulator for the standard environment for the exercises though, rather than STM32.

For right now: https://docs.zephyrproject.org/latest/getting_started/index.html should be able to walk you through getting to blinky. There are over 30 STM32 boards in the repo, so hopefully one of them matches what you have handy.

leandropg
Score: 0 | 7 months ago | no reply

Thanks Kate... I will start to work on that :) Thanks

Kate StewartSpeaker
Score: 1 | 7 months ago | no reply

There's a .pdf of the slides that can be downloaded on the lower left of this page, for those who would like to follow the links.

JeanLabrosse
Score: 0 | 7 months ago | 1 reply

Once an API is created is it locked in or will some of the APIs change over time?

Kate StewartSpeaker
Score: 0 | 7 months ago | no reply

Hi Jean,
The LTS has the API's locked down during its support period. There is an API review committee that tracks and reviews any changes happening in development that impact the APIs.

JeanLabrosse
Score: 0 | 7 months ago | 1 reply

Why so many commits? Adding features? Bugs being corrected? This many commits makes it difficult for safety certification no?

Cleo
Score: 0 | 7 months ago | 1 reply

I think that's why they have the LTS releases every two years. That would leave enough time to put them through the safety auditing process.

Kate StewartSpeaker
Score: 0 | 7 months ago | no reply

Yes, there is an LTS every 2 years. Once an LTS is cut, only bug fixes which is much less frequent. The 50K commits are in Development tree. Its mostly features being added - with over 250 boards, there's a lot of driver, config, etc. information. The LTS 2 is going to be the basis for the 61508 certification, but we're preparing the code base to get it ready now.

OUR SPONSORS