
Host Driver Overview
17
SWRU455A – February 2017 – Revised March 2017
Copyright © 2017, Texas Instruments Incorporated
Overview
1.4.2 OS versus Non-OS
The same driver can work on platforms running an OS, and platforms without an operating system (non-
OS).
An OS adaptation layer is used for binding the host driver and the target OS. The driver already comes
with a built-in adaptation layer for platforms running without an OS. Other platforms require a simple OS
adaptation layer.
This adaptation layer must wrap two major objects:
•
Sync object – Object intended to synchronize between different contexts and interrupt routines
•
Lock object – Object intended to protect a shared resource
The driver pre-allocates all the required OS resources (dynamic or static according to the setting) on
calling sl_Start. The number of allocated objects is calculated according to the maximum concurrent
actions required by the user.
The SimpleLink host driver does not use its own processing context. To bind a context to the driver, the
user can implement a spawn mechanism, or use the built-in spawn mechanism provided by the driver. If
the built-in mechanism is used, the host application must create dedicated context to the driver and call
sl_Task from this context. For platforms without an OS, the application must call to the sl_Task function
repeatedly from its main loop.
1.4.3 Quick Reference
shows a quick reference to the entire set of APIs provided by the host driver.