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 cu_linux_resources::LinuxResources as the provider. It opens serial devices and exposes fixed serial slots such as <bundle>.serial0 through <bundle>.serial5. For serial config keys (serialN_dev, serialN_baudrate, parity/stopbits/timeout), see cu_linux_resources README: Config Keys / Serial.

resources: [
  (
    id: "linux",
    provider: "cu_linux_resources::LinuxResources",
    config: { "serial3_dev": "/dev/ttyUSB0", "serial3_baudrate": 115200 },
  ),
],
bridges: [
  (
    id: "msp_bridge",
    type: "cu_msp_bridge::CuMspBridgeStd",
    resources: { serial: "linux.serial3" },
    channels: [ Tx (id: "requests"), Rx (id: "responses") ],
  ),
],

For embedded targets, provide your own bundle that moves the UART into the ResourceManager as an owned resource. If your UART type is not Sync, wrap it once at bundle registration time with cu_linux_resources::Exclusive<T>. See examples/cu_elrs_bdshot_demo and examples/cu_msp_bridge_loopback for end-to-end wiring and config mutation.