3 ms·

Is there an comparison to FreeRTOS and mbed? I could not find a good article online so far. There is a "Why create another RTOS?" section under https://www.zeph

Is there an comparison to FreeRTOS and mbed? I could not find a good article online so far. There is a "Why create another RTOS?" section under https://www.zephyrproject.org/what-is-zephyr/ https://www.zephyrproject.org/what-is-zephyr/ but it's very light on details.

smarx007 7y ago
https://youtu.be/1cOP_jLG6l4 https://youtu.be/1cOP_jLG6l4 is a very interesting keynote answering some of my questions.
travisgriggs 7y ago
I found this link (https://www.osrtos.com/ https://www.osrtos.com/) really useful 2 years ago. I don't know how up to date it is. In the end I went with a little known entry called TNEO because I liked Frank Dmitry's writup about it. It's really hard to compare these things though. Zephyr is like a mini Linux complete with device tree, build system, configuration files and drivers. All of which you get to determine the correctness of. Something like FreeRTOS can seem both much simpler and harder. It's mostly just C Source. If you need a stack or a driver, you get to own that yourself. But it's like, right there in front of you. No need to learn somebody else's favorite build system, etc. Do what makes most sense for you. We went with TNEO because the ultimate feature we needed was aggressive processor sleep ability for power savings. I have not found any that solve this well out of the box. They're built for demo boards that stay plugged into the wall. And to be fair, there's a size-able chunk of IoT devices that sit near lots of power. I asked a former coworker who helped me with TNEO (and before that he and I had worked quite a bit with FreeRTOS and RIOT as well as a lot of just no RTOS) how he's liking Zephyr in his new job. He said it was hell to set up and get working right, but the slack community around it had been helpful, but seemed to be nice at the moment, especially since they were using chipsets it was know to work well on. He did note that the power save story was no better than our previous experiences, but he's working on powered devices.

smarx007 7y ago

https://youtu.be/1cOP_jLG6l4 https://youtu.be/1cOP_jLG6l4 is a very interesting keynote answering some of my questions.

travisgriggs 7y ago

I found this link (https://www.osrtos.com/ https://www.osrtos.com/) really useful 2 years ago. I don't know how up to date it is. In the end I went with a little known entry called TNEO because I liked Frank Dmitry's writup about it. It's really hard to compare these things though. Zephyr is like a mini Linux complete with device tree, build system, configuration files and drivers. All of which you get to determine the correctness of. Something like FreeRTOS can seem both much simpler and harder. It's mostly just C Source. If you need a stack or a driver, you get to own that yourself. But it's like, right there in front of you. No need to learn somebody else's favorite build system, etc. Do what makes most sense for you. We went with TNEO because the ultimate feature we needed was aggressive processor sleep ability for power savings. I have not found any that solve this well out of the box. They're built for demo boards that stay plugged into the wall. And to be fair, there's a size-able chunk of IoT devices that sit near lots of power. I asked a former coworker who helped me with TNEO (and before that he and I had worked quite a bit with FreeRTOS and RIOT as well as a lot of just no RTOS) how he's liking Zephyr in his new job. He said it was hell to set up and get working right, but the slack community around it had been helpful, but seemed to be nice at the moment, especially since they were using chipsets it was know to work well on. He did note that the power save story was no better than our previous experiences, but he's working on powered devices.