Roadmap¶
This is where things stand, in order. We don't publish dates: a step moves to done when its evidence exists.
- Foundations Done
The organisation and its settings as code,
ci-toolsv1,espidf-toolsv1,driver-template, the handbook and the documentation platform, and this portal. - Chip drivers 22 release candidates
22 public drivers, each tagged
v0.1.0-rc.1with host tests, a fuzzer, MISRA C++:2023 checks, an ESP32 example and a documentation site, in the kokeb-labs-drivers organisation. The driver request pipeline decides which chip comes next. - Hardware validation Next Every driver is at level H0 today. A driver moves to H1 when a defined bench rig has run its example with the logs kept, and to H2 when a hardware engineer signs off. A release candidate that passes the bench is tagged again, on the same commit, as its release. Help with a bench is welcome: see contributing.
- kb-core and MCU ports In development The framework that joins drivers to interfaces, handlers and an RTOS layer, and ports for ESP32 and STM32. These repositories are not public yet. Drivers stay usable without them.
- Open boards Started
Open KiCad boards built around the drivers, in the
kokeb-labs-open-boards organisation, each traced from its needs to its
test results.
board-template, the parts library and the circuit-block library exist; the first board, a BMP581 breakout, is at concept stage and nothing has been built or verified yet. - Tools for users A command-line tool, a board configurator and a documentation hub. Planned: nothing to try yet.
Language standard¶
Drivers target C++20 today. The standard will move up under the stated policy when every compiler we ship for supports it and the checks are ready for it, not on a date.
Follow along¶
- Releases: watch a repository on GitHub (Watch, Custom, Releases).
- Discussions: questions and ideas in the kokeb-labs discussions and the drivers discussions.
- Driver requests shape step 2: ask for a chip.