OL2385SWUG datasheet(27/64 Pages) NXP

27 / 64 page

NXP Semiconductors

OL2385SWUG

SIGFOX software driver

OL2385SWUG

All information provided in this document is subject to legal disclaimers.

User guide

Rev. 2.1 — 6 April 2018

27 / 64

For a more detailed description of the software driver API (function signatures,

parameters) refer to the API programmer's guide (included in the SIGFOX software driver

zip file).

6.2.4.3 Blocking and nonblocking functions

The SIGFOX driver includes functions for blocking and Nonblocking SPI communication.

Blocking functions send a SPI frame and wait for an acknowledgment frame from the

sample driver. Nonblocking functions send a SPI frame and immediately return. The user

has to call another function to receive an acknowledgment.

For the most part, the SIGFOX driver uses blocking communication functions because

they are simpler to implement. The user only needs to call a blocking function to send a

SPI command and to get a response containing the desired data.

Nonblocking functions are useful when the wait time for a response is several seconds.

This applies to SPI commands that involve transmissions to the SIGFOX network, such

as Send Payload, Send Bit and Send Out of Band. Nonblocking communication for

these types of SPI commands is more practical because the MCU can do useful work

while waiting for the acknowledgment. The functions in Table 6 implement nonblocking

communication, Figure 19 shows typical usage of these functions.

Table 6. Nonblocking functions

Function name

Description

SF_SendCommandNonBlock

Sends a SPI command to the SIGFOX device and does not wait

for an acknowledgment

SF_IsAckFrameReady

Checks if the SIGFOX device is ready to send an

acknowledgment

SF_ReadAckFrameNonBlock

Reads an acknowledgment frame

Figure 19. Using nonblocking functions

OL2385SWUG датащи(PDF) 27 Page - NXP Semiconductors