Hardware Abstraction Layer (HAL) API Reference
Modules |
|
Common Microcontroller Functions | |
Token Access | |
Sample APIs for Peripheral Access | |
System Timer Control | |
Functions that provide access to the system clock.
|
|
Symbol Timer Control | |
HAL Configuration | |
HAL Utilities | |
Bootloader Interfaces | |
Custom Bootloader HAL |
Detailed Description
EM35x Microprocessors
HAL function names have the following prefix conventions:
halCommon: API that is used by the EmberZNet stack and can also be called from an application. This API must be implemented. Custom applications can change the implementation of the API but its functionality must remain the same.
hal: API that is used by sample applications. Custom applications can remove this API or change its implementation as they see fit.
halStack: API used only by the EmberZNet stack. This API must be implemented and should not be directly called from any application. Custom applications can change the implementation of the API, but its functionality must remain the same.
halInternal:
API that is internal to the HAL. The EmberZNet stack and applications must never call this API directly. Custom applications can change this API as they see fit. However, be careful not to impact the functionalty of any halStack or halCommon APIs.
See also
hal.h
.