cu-msp-bridge 0.12.0

Copper bridge to talk to MSP devices over serial.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

# cu-msp-bridge

Bridge that combines the MSP source/sink tasks into one serial transport.  It exposes a single TX channel (`requests`) that accepts batches of [`cu_msp_lib::structs::MspRequest`] messages and a single RX channel (`responses`) that yields [`MspResponse`] batches decoded from the line.

## Resources and configuration

The bridge expects a `serial` resource. For std targets use the built-in `StdSerialBundle`, which opens a serial port and stores it as `Mutex<StdSerial>` under `<bundle>.serial`.

| Key          | Type   | Default        | Description                                                |
|--------------|--------|----------------|------------------------------------------------------------|
| `device`     | string | `/dev/ttyUSB0` | Path to the serial device (can be a PTY).                  |
| `baudrate`   | u32    | `115200`       | Serial baud rate.                                          |
| `timeout_ms` | u64    | `50`           | Read timeout passed to the serial driver in milliseconds.  |

```ron
resources: [
  (
    id: "fc",
    provider: "cu_msp_bridge::StdSerialBundle",
    config: { "device": "/dev/ttyUSB0", "baudrate": 115200 },
  ),
],
bridges: [
  (
    id: "msp_bridge",
    type: "cu_msp_bridge::CuMspBridgeStd",
    resources: { serial: "fc.serial" },
    channels: [ Tx (id: "requests"), Rx (id: "responses") ],
  ),
],
```

For embedded targets, provide your own bundle that moves the UART into the `ResourceManager` (e.g. a `spin::Mutex<SerialPort>`). See `examples/cu_elrs_bdshot_demo` and `examples/cu_msp_bridge_loopback` for end-to-end wiring and config mutation.