SWRU455M February 2017 – October 2020 CC3120 , CC3120MOD , CC3130 , CC3135 , CC3135MOD , CC3220MOD , CC3220MODA , CC3220R , CC3220S , CC3220SF , CC3230S , CC3230SF , CC3235MODAS , CC3235MODASF , CC3235MODS , CC3235MODSF , CC3235S , CC3235SF
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:
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 a context dedicated to the driver and call sl_Task from this context. For platforms without an OS, the application must call the sl_Task function repeatedly from its main loop.