Videos

A Zephyr User Story – Franco Saworski, blik GmbH

By November 14, 2018 No Comments

 

Summary

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 touch points are board support, the low power subsystem, the memory and file system 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

Franco Saworski has shipped industry IoT products in startups since early 2015. Currently he is team lead for embedded development at blik GmbH. Formerly Mr Saworski was lead embedded developer for ProGlove. Between 2009 and 2015 he studied physics at LMU Munich. Between 2012 and 2014 he was a working student for software and hardware development at Max-Planck-Institute of Quantum Optics. In early 2015 he started working at the startup Workaround, better known as ProGlove, as a pre-seed employee and lead software developer for their wearable hand scanner system. There he was on the team which 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. Late in 2017 he assumed his current role as embedded hardware and software lead at startup blik in their pre-seed stage. There he is developing a battery powered sensor node and receiver used to track load carriers, amongst other goods, in logistics and industry. With his former experience he is helping to shape the team, building development processes, working towards production at scale of currently developed hardware product. During his work at blik, he publicly contributed code back to ZephyrOS, which is running on their sensorunit.