migration to Zephyr

[ck-telecom]

I'm excited that something about migration to Zephyr

Gerard has served on the Zephyr working group for a while - his advice is that we could look into moving management of the fundamental operating system (drivers, architecture, SDK, compatibility layers) to the umbrella of a group like Linux Foundation or Apache Software Foundation, which have a lot of experience in open source project management. He’s also pushing for us to migrate to Zephyr instead of FreeRTOS as the foundation. This seems like a pretty reasonable goal, though it will be a pretty big software lift. Good news is that our bootloader for Pebble Time 2 is already built with Zephr.

so before I try something, I wanna talk about how migrate to Zephyr?
pebble OS abstraction layer - I see PebbleOS/src/libos seems few kernel APIs

[ericmigi]

Hey! What do you want to try?

[ericmigi]

cc @gmarull

[gmarull]

Thanks for the interest, @ck-telecom ! Migrating to Zephyr will likely be a long journey if it happens :-)... I guess the first step is to make sure vanilla Zephyr runs well on our boards (initial support is already upstream, but we miss a lot of drivers). Once it is done, I'd start reimplementing simpler things like the recovery firmware (PRF), so that we, e.g., get all the BLE parts working. Then we should probably re-implement all the user-facing APIs, re-using PebbleOS stuff, and in some others just use Zephyr facilities (all the driver side, board support, etc. is pretty bad in PebbleOS for example). This is the tricky part.