Porting Guide¶
This section provides information that must be considered when porting the SDK to a new hardware platform. Special attention must be given to MCU selection, SPI configuration, SPARK Wireless Core interfacing and new hardware driver development in the Board Support Package (BSP). The porting guide is structured into articles which contain information for each topic.
For successful porting, two main steps are required:
Provide a BSP for the desired hardware platform.
Link the new BSP to the SPARK applications and Cores by creating a new BSP interface implementation.
The following articles and annexes offer guidance on the BSP and BSP interface layer development.
Articles¶
Annexes¶
An annex is created for each structure and function that are part of the BSP. Examples for the EVK1.4 carrier board are also provided as a reference.
Annex swc_radio_hal_t structure
This annex provides in-depth information on the main child element of the swc_hal_t structure.
This annex provides in-depth information on macros to enter and exit critical sections of the code.
Annex context_switch function pointer
This annex provides in-depth information on the context_switch function pointer, a child element of the swc_hal_t structure.
Annex get_tick_quarter_ms function pointer
This annex provides in-depth information on the get_tick_quarter_ms function pointer, a child element of the swc_hal_t structure.
Annex wireless callback functions
This annex provides in-depth information on the callback setters implementation required by the user hardware BSP.
Part of the Wireless Core porting article, this annex provides an outlook into the dual radio exclusive child elements of the swc_hal_t structure.
Annex EVK1.4 MCU priority list
Shows the IRQ priority level definitions of the the EVK1.4 BSP that can be used as an example.