Hi Noelle, here are some quick answers, from my point of view (caveat: I do not have serious hands-on experience with Zephyr).
> 1) Are there advantages / disadvantages to the different kinds of groups supporting and contributing to RIOT vs Zephyr (Europe/US, academic/industry, ?/?) Coarsely: RIOT is more grassroots and mainly of European origin, while Zephyr is more corporate and of mainly of American origin (it stems from an Intel product). In practice, the RIOT community also collaborates/overlaps quite a bit with the IETF community, which could be a plus for communication protocols aspects. > 2) Are there advantages / disadvantages I should be aware of for using the OS commercially (compared to Zephyr) Both RIOT and Zephyr are used in various commercial products, as far as I know. For experience with RIOT commercial use, you could consider asking Continental about their experience (they actively contribute and maintain code). They sell a RIOT-powered telematics module for car-sharing, see for instance https://summit.riot-os.org/2019/blog/speakers/vincent-dupont/ > 3) Are there advantages / disadvantages to the hardware abstraction method RIOT uses (vs DTS in Zephyr) I do not know enough about Zephyr's abstraction model to answer this question. That said: RIOT's abstraction provides portability of your code to ~150 different types of boards and to a large variety of microcontrollers architectures. > 4) What is the goal of the development of the OS (use by industry, academic, educational use, hobby)? RIOT developers combines industry contributors (large companies, and SMEs), makers/tinkerers and academics. The goal is to develop and maintain a community-driven, general-purpose OS for IoT microcontroller-based devices which cannot use Linux-class operating systems due to on-board resource constraints. Best, Emmanuel On Mon, Mar 9, 2020 at 5:02 PM Noëlle Clement <n.clem...@abelsensors.com> wrote: > Hi RIOT users! > > My team is looking into the possibility to transition from a bare-metal > application to an OS for our embedded controllers. We develop IoT and > wireless sensors solutions, for which we have also developed our own > controller and platform. A lot of in-house development and maintenance! > > Would some of you be willing to answer some questions about why RIOT OS > would be a good choice for us? (The main comparison right now is between > RIOT-OS, Zephyr Project and ThreadX) > > To give a summary of the reasons for even looking into a more advanced > architecture: there are a few features common in embedded (IoT) OS' that > would be very convenient for future development of the controller. Things > like hardware abstraction and task scheduling are very welcome. In general > we want to make it easier to maintain the code (pre- and post release) and > decrease time-to-market for new controller versions (with new/upgraded > hardware modules). A common requirement that also applies to us are the > resource constraints and the ultra low power features (we need to be able > to use the low power modes for the STM32L151CC, but that can be added in > the port). Real-time isn’t a priority for us at all, although the priority > (pre-emptive)-based scheduling would be very useful. > The controller is part of the in-house developed IoT system, which > currently is mostly used for Smart Waste and Smart Silo products (detecting > fill rates in both). > > A few questions that popped up during my own research on this (mostly > about RIOT vs Zephyr): > 1) Are there advantages / disadvantages to the different kinds of groups > supporting and contributing to RIOT vs Zephyr (Europe/US, > academic/industry, ?/?) > 2) Are there advantages / disadvantages I should be aware of for using the > OS commercially (compared to Zephyr) > 3) Are there advantages / disadvantages to the hardware abstraction method > RIOT uses (vs DTS in Zephyr) > 4) What is the goal of the development of the OS (use by industry, > academic, educational use, hobby)? > 5) Any technical limitations I should be aware of? > 6) Any technical advantages (over Zephyr)? > > Any help is really appreciated! > > All the best, > Noelle > > _______________________________________________ > users mailing list > users@riot-os.org > https://lists.riot-os.org/mailman/listinfo/users >
_______________________________________________ users mailing list users@riot-os.org https://lists.riot-os.org/mailman/listinfo/users
