Roadmap

[kaspar030]

This is the Roadmap tracking issue, See below breakdown, more or less kept up-to-date. For now we are prioritizing features and issues relating to the 1st release milestone.

Development tools & Documentation

• Build system
  • evaluate & confirm or drop use of laze
  • provide working out-of-tree workflow #332
• [Tracking Issue] Documentation Improvements #164

OS functionality

• Support defmt
• Multicore support tracking: SMP Support  #243
  • Async executor on second core
  • Scheduler support for "regular" threads on both cores
• unify "console"
• Configuration storage feat: riot-rs-storage #277
• Sensor abstraction WIP: sensor abstraction & hardware setup file #271 feat(embassy-arch): provide peripheral-independent I2C and SPI types #317 feat(embassy): provide a GPIO API unified across architectures  #322
• OTA updates

Embassy integration

• Dispatch to correct embassy init()
• Support per-board drivers initialization -> covered through riot-rs-boards & autostart tasks
• Support application portability
  • 1. "portable" blinky
    This needs simple gpio or led abstraction (enumeration?)
  • 2. "portable" sensor reading
    This needs a way (in build system, code) to easily add sensor drivers.
  • "portable" simple network application
  • make 1. / 2. networked
• Get back linkme support

Hardware Support

• Extended Cortex-M support
  • rpi-pico support
• RISC-V support
  • Add any RISC-V board
  • riot-rs-rt bringup
  • embassy => supporting esp32c3/6
  • riot-rs-threads RISC-V task switching threads: add support for RISC-V (esp32 only) #182 [Tracking Issue] riot-rs-threads: add RISC-V support #157
• "native" support
• MPU support
  • Cortex-M
  • RISC-V
  • use for detecting stack overflows
  • support completely sandboxed thread

RIOT-c support

(postponed)

Basic (Layer<5) networking support

• Basic (Layer<5) networking support
• TCP/IP and UDP
• 802.15.4 / 6LoWPAN
• Bluetooth
• LoRa

Extended (Layer>4) networking + security

• feat: MQTT client #335
• CoAP road map #226
• 802.15.4 link layer security
• TLS and DTLS
• Crypto library

Device Livecycle

• On-boarding
  • TOFU
  • Zero-Touch
  • Explicit / dedicated configuration (inspired by this fedi thread + see below)
• feat: SUIT client #336

Extend embassy integration

• low-power
• Multiple timers
• Board support trait not using a trait

Extend hardware support

• nrf5340
• re-think riot-rs-boards
• stm32

CI

• Testing Framework
• integrate embedded-test #331
• set up CI testing on hardware

Formal Verification

• Tracking formal verification status #140

[chrysn]

Addendum for Device Lifecycle:

• On-boarding

  • Explicit / dedicated configuration.

    When networking itself requires onboarding that has neither TOFU nor Zero-Touch capabilities, it'd be convenient to have a cheap extra on-boarding channel. This may be USB Ethernet, WebUSB or Bluetooth, which can set up WiFi credentials. Using that interface should ideally be accessible to users unfamiliar with programming, eg. by having configuration options exposed as MTP files, or even a web application that provides different levels of interface to an attached device's configuration (eg. key-value manipulation or forms for described fields).

    (inspired by a fedi thread)