A tested, ready-to-consume Zephyr port of LibOSDP with a devicetree-bound OSDP driver layer. Wire a UART in your board's devicetree and call high-level OSDP APIs straight from your application — no transport, framing, or secure-channel plumbing to write yourself.
Months of board bring-up and protocol scaffolding, already done — packaged as a Zephyr SDK you drop into your west workspace.
A tested, ready-to-consume LibOSDP port for Zephyr — not a do-it-yourself integration you assemble from upstream sources and hope compiles on your target.
It is the full SIA OSDP protocol surface — secure channel, file transfer, multi-drop — running on a real-time OS, validated rather than left as an exercise.
Drivers expose LibOSDP to your application through standard Zephyr idioms, so OSDP fits the same subsystem model as every other peripheral in your build.
The driver layer owns the wire — transport, framing, timing — leaving your application to work against the high-level OSDP API instead of byte buffers.
Declare the UART your OSDP bus is wired to as a devicetree node and point the OSDP driver at it. Bringing up a new board is a devicetree change, not a port.
From there you call the high-level OSDP calls directly in your app — the SDK turns a DTS uart entry into a working OSDP endpoint with nothing left to wire by hand.
Buildable Control Panel and Peripheral Device application stubs ship with the SDK, so you start from a working example rather than a blank main().
Use them as the skeleton of your product firmware — flash, watch a secure-channel session come up, then grow it into your own CP or PD.
An update service keeps the port current as LibOSDP evolves, so protocol fixes and new capabilities reach your build without a re-port each time.
You stay on a maintained baseline instead of pinning to a one-off snapshot that drifts further from upstream every release.
Every licence includes a year of updates and support out of the box, with renewal per additional year whenever you want to stay current.
Support comes from the people who maintain the port — direct answers about the SDK, not a generic ticket queue.
Need it inside a real end product? Optional integration and customization support takes the SDK the last mile — board specifics, application logic, and product-level requirements.
Engage us as much or as little as you need: a self-serve SDK for teams that want to run with it, hands-on help for teams that want a partner.
The SDK builds on standard Zephyr boards through a west workspace — anything with a Zephyr UART driver works. You point the OSDP driver at a UART node in your board's devicetree, so bringing up a new board is a devicetree change, not a port.
You declare the UART your OSDP bus is wired to as a devicetree node and reference it from the OSDP driver. From there you call the high-level LibOSDP APIs directly in your application — the SDK owns the transport, framing, and secure channel, so there is no UART or RS-485 plumbing to write yourself.
Every licence includes one year of updates and support — tracking new LibOSDP releases. After that, support and updates can be renewed per additional year. Integration and customization help for your end product is available on top, whenever you need it.
Osprio Pro firmware is built on this exact SDK — the same LibOSDP-on-Zephyr port and OSDP driver layer. We depend on it ourselves, so it stays maintained and you get support from the people who ship on it.
Have a question? Ask us →