DevLibs

Drivers for various electronic modules, written in plain C so they can be dropped into just about any embedded project.

Every library follows the same structure: a portable C core that contains all the device logic and knows nothing about the hardware, plus a thin platform layer that implements a handful of hardware dependent functions.

<LIBRARY>/
├── <name>.h portable C core, public API
├── <name>.c portable C core, device logic
├── platform/
│ ├── arduino/<name>-arduino.{h,cpp}
│ ├── mbed/<name>-mbed.{h,cpp}
│ └── stm32cube/<name>-cube-hal.{h,c}
├── docs/ datasheets (where available)
├── README.md
├── library.json PlatformIO manifest
├── library.properties Arduino IDE manifest
└── lib_build.py PlatformIO platform selection script

The core declares its hardware dependencies as extern functions at the bottom of <name>.h, and the device object carries a void* platform_dev pointer that each platform layer fills in through its <name>_<platform>_init() helper.

Select the platform implementation with the PLATFORM build flag; lib_build.py takes care of the include path and source filtering:

[env:nucleo_f091rc]
platform = ststm32
framework = arduino
build_flags = -D PLATFORM=arduino

1. Create platform/<yours>/<name>-<yours>.{h,c}.
2. Implement the extern functions listed at the bottom of <name>.h.
3. Add a <name>_<yours>_init() helper that stores your descriptor in dev->platform_dev and then calls <name>_init(dev).

See any existing platform layer for a reference implementation.

MIT, except where a library ships its own LICENSE.txt:

• RF22 - Copyright (C) 2011 Mike McCauley, GPL V2 or commercial
• RFM69
• SX1278

Lukasz Uszko - lukasz.uszko@gmail.com