1.2.21.37 1.3.25.37 1.4.21.37 1.5.25.37 1.6.22.37 1.7.23.37 1.9.19.37 1.29.23.37 1.30.18.37 1.31.18.37 1.32.26.37 1.33.16.37 1.37.18.37 1.38.21.37 1.39.18.37 1.40.20.37 SERCOMx_SPI_WriteRead Function

C

/* x = SERCOM instance number */

/* SPI master mode */

bool SERCOMx_SPI_WriteRead ( void * pTransmitData, size_t txSize, void * pReceiveData, size_t rxSize)

Summary

Write and Read data on SERCOM SPI peripheral.

Description

This function transmits "txSize" number of bytes and receives "rxSize" number of bytes on SERCOM x SPI module. Data pointed by pTransmitData is transmitted and received data is saved in the location pointed by pReceiveData. The function will transfer the maximum of "txSize" or "rxSize" data units towards completion. When interrupt is disabled, this function will be blocking in nature. In this mode, the function will not return until all the requested data is transferred. The function returns true after transferring all the data. This indicates that the operation has been completed. When interrupt is enabled, the function will be non-blocking in nature. The function returns immediately. The data transfer process continues in the peripheral interrupt. The application specified transmit and receive buffer are owned by the library until the data transfer is complete and should not be modified by the application till the transfer is complete. Only one transfer is allowed at any time. The Application can use a callback function or a polling function to check for completion of the transfer. If a callback is required, this should be registered prior to calling the SERCOMx_SPI_WriteRead() function. The application can use the SERCOMx_SPI_IsBusy() to poll for completion.

Precondition

The SERCOMx_SPI_Initialize function must have been called. If the peripheral instance has been configured for Interrupt mode and transfer completion status needs to be communicated back to application via callback, a callback should have been registered using SERCOMx_SPI_CallbackRegister() function.

Parameters

Returns

true - If configured for blocking mode, the function has received and transmitted the requested number of bytes. If configured for non-blocking mode, the request was accepted successfully and will be processed in the interrupt.

false - If both pTransmitData and pReceiveData are NULL, or if both txSize and rxSize are 0 or if txSize is non-zero but the pTransmitData is set to NULL or rxSize is non-zero but pReceiveData is NULL. In non-blocking mode, the function returns false if there is an on-going data transfer at the time of calling the function.

Example

// The following code snippet shows an example using the
// SERCOMx_SPI_WriteRead() function in interrupt mode operation using the
// callback function.

uint8_t txBuffer[4];
uint8_t rxBuffer[10];
size_t txSize = 4;
size_t rxSize = 10;

void APP_SPITransferHandler(uintptr_t context)
{
    //Transfer was completed without error, do something else now.
}

SERCOM0_SPI_Initialize();
SERCOM0_SPI_CallbackRegister(&APP_SPITransferHandler, (uintptr_t)NULL);
if(SERCOM0_SPI_WriteRead(&txBuffer, txSize, &rxBuffer, rxSize))
{
    // request got accepted
}
else
{
    // request didn't get accepted, try again later with correct arguments
}

// The following code snippet shows non-interrupt or blocking mode
// operation.

uint8_t txBuffer[4];
uint8_t rxBuffer[10];
size_t txSize = 4;
size_t rxSize = 10;

SERCOM0_SPI_Initialize();

// This function call will block.
SERCOM0_SPI_WriteRead(&txBuffer, txSize, &rxBuffer, rxSize);

Remarks

None.