Skip to main content
Create a new firmware project from scratch by telling Seb what you want: pick a board from the registry, pull datasheets, generate drivers, and wire up the app. Seb uses tool calls for all of it—no separate CLI commands for registry, create, or datasheet. One chat, from the folder where you want the project.

​
Create the project

From that directory, open Seb and ask it to create a project. It will look up boards and generate the structure for you.
  • “What boards are available?” — Seb queries the registry and lists boards
  • “Create a project for stm32f407vg” — CMake-based project with board config, ARM GCC toolchain, and build setup
  • “Create a project for nucleo-l476rg in this folder” — Same, with your chosen location
Then cd into the new project and continue in the same or a new session.

​
Add design docs and datasheets

  • Drop BOMs, schematics, or datasheets into the project’s documents/ folder, or
  • Ask Seb to pull from the registry: “Get the BMP280 datasheet” · “Get datasheets for BMP280 and MPU6050”
Seb fetches and attaches them to your project context via tool calls.

​
Generate drivers and application code

  • “Generate a driver for BMP280” · “Generate drivers for all my sensors”
  • “Validate the BMP280 driver” · “Show me how to integrate the BMP280 driver into my main application”
  • “Write a main application loop that reads from BMP280 every second” · “Create an interrupt handler for button presses” · “Implement a state machine for my application”
Seb writes and edits files; ask for changes or integration as you go.

​
Build and test

Ask Seb to build or flash, or run the commands yourself: “Build the project” · “Flash the board” — or cd build && cmake .. && make and seb debug if you prefer.

​
Keep going

Use the same chat or a new one from the project dir for follow-ups: “How should I structure my main loop?” · “What’s the best way to configure SPI for my display?” · “Add error handling to the sensor read.”