2 unstable releases

0.2.0 Dec 2, 2024
0.1.0 Aug 28, 2024

#2241 in Embedded development

Download history 63/week @ 2024-12-13 47/week @ 2024-12-20 41/week @ 2024-12-27 28/week @ 2025-01-03 31/week @ 2025-01-10 80/week @ 2025-01-17 25/week @ 2025-01-24 174/week @ 2025-01-31 54/week @ 2025-02-07 36/week @ 2025-02-14 30/week @ 2025-02-21 2/week @ 2025-02-28

205 downloads per month
Used in 3 crates

MIT/Apache

30KB
635 lines

Persistent Settings Management Serial Interface

Description

This crate provides a simple means to load, configure, and store device settings over a serial (i.e. text-based) interface. It is ideal to be used with serial ports and terminal emulators, and exposes a simple way to allow users to configure device operation.

Example

Let's assume that your settings structure looks as follows:

#[derive(miniconf::Tree, ...)]
struct Settings {
    broker: String,
    id: String,
}

A user would be displayed the following terminal interface:

 help
AVAILABLE ITEMS:
  get [path]
  set <path> <value>
  store [path]
  clear [path]
  platform <cmd>
  help [ <command> ]

> get
Available settings:
/broker: "test" [default: "mqtt"] [not stored]
/id: "04-91-62-d2-a8-6f" [default] [not stored]

Design

Settings are specified in a miniconf::TreeKey settings tree and are transferred over the serial interface using JSON encoding. This means that things like strings must be encased in quotes.

Limitations

Currently, there is a hardcoded limit of 128-bytes on the settings path. This is arbitrary and can be changed if needed.

Dependencies

~1.5–2.2MB
~46K SLoC