A tested, ready-to-consume port of LibOSDP for Zephyr RTOS 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 RTOS — the full SIA OSDP surface (secure channel, file transfer, multi-drop) validated on a real-time OS, not a DIY integration you assemble from upstream and hope compiles.
Drivers expose LibOSDP through standard Zephyr idioms and own the wire — transport, framing, timing — so your application works 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 driver at it. Bringing up a new board is a devicetree change, not a port — a DTS entry becomes a working OSDP endpoint.
Buildable Access Control Unit and Peripheral Device app stubs ship with the SDK — flash one, watch a secure-channel session come up, then grow it into your own ACU or PD firmware instead of starting from a blank main().
An update service keeps the port current as LibOSDP evolves, so protocol fixes and new capabilities reach your build without a re-port — a maintained baseline, not a one-off snapshot that drifts from upstream.
Every licence includes a year of updates and support out of the box, renewable per additional year — direct answers from the people who maintain the port, not a generic ticket queue.
Optional hands-on help takes the SDK the last mile into a real product — board specifics, application logic, and product-level requirements — as much or as little as you need.
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 →