A Zephyr User Story - Franco Saworski, blik GmbH

A Zephyr User Story - Franco Saworski, blik GmbH
The choice for an RTOS can be an opaque one. There are a number of RTOS' available with different levels of feature sets, abstractions and out-of-the-box board support, which make the choice from a blank slate a very diverse one.
Franco will guide you through the decision process for an RTOS and goes on to discuss implementation details. The choice is driven by factors from a startup environment, including a small development team, industry standards and testing. Explicit technical touchpoints are board support, the lowpower subsystem, the memory and filesystem subsystems, and the networking subsystem.
Franco presents this from his three-year experience with Zephyr in the role as lead developer for industrial IoT systems in two startups. He has gained his knowledge over time from porting a bare-metal application to the RTOS, and upgrading the project to a new release version.
About Franco Saworski
Between 2009 and 2015 I studied physics at LMU Munich. Between 2012 and 2014 I was working student for software and hardware development at Max-Planck-Institute of Quantum Optics.
In early 2015 I started working at the startup Workaround, better known as ProGlove, as a pre-seed employee and lead software developer for their wearable handscanner system. We prototyped the scanner, also known as "Mark", close to the customer and shipping two product releases, "Mark One" and "Mark One S". The software was ported to "Mark One S" with Zephyr. Building the software dev team, our team culture, and our development, production, and compliance processes made my role diverse and a shaping experience.
Late in 2017 I assumed my current role as embedded hardware and software lead at startup blik in their pre-seed stage. We develop a battery powered sensor node and receiver used to track load carriers, amongst other goods, in logistics and industry. With my former experience I am shaping our team, building development processes, working towards production at scale of our currently developed hardware product.
During my work at blik, we publicly contributed code back to ZephyrOS, which is running on our sensorunit.