NRF52810-QCAA-R datasheet(384/483 Pages) NORDIC

384 / 483 page

Peripherals

6.19.3 SPI slave operation

SPI slave uses two memory pointers, RXD.PTR and TXD.PTR, that point to the RXD buffer (receive buffer)

and TXD buffer (transmit buffer) respectively. Since these buffers are located in RAM, which can be

accessed by both the SPI slave and the CPU, a hardware based semaphore mechanism is implemented to

enable safe sharing.

See SPI transaction when shortcut between END and ACQUIRE is enabled on page 385.

Before the CPU can safely update the RXD.PTR and TXD.PTR pointers it must first acquire the SPI

semaphore. The CPU can acquire the semaphore by triggering the ACQUIRE task and then receiving the

ACQUIRED event. When the CPU has updated the RXD.PTR and TXD.PTR pointers the CPU must release the

semaphore before the SPI slave will be able to acquire it. The CPU releases the semaphore by triggering

the RELEASE task. This is illustrated in SPI transaction when shortcut between END and ACQUIRE is

enabled on page 385. Triggering the RELEASE task when the semaphore is not granted to the CPU will

have no effect.

The semaphore mechanism does not, at any time, prevent the CPU from performing read or write access

to the RXD.PTR register, the TXD.PTR registers, or the RAM that these pointers are pointing to. The

semaphore is only telling when these can be updated by the CPU so that safe sharing is achieved.

The semaphore is by default assigned to the CPU after the SPI slave is enabled. No ACQUIRED event will be

generated for this initial semaphore handover. An ACQUIRED event will be generated immediately if the

ACQUIRE task is triggered while the semaphore is assigned to the CPU.

The SPI slave will try to acquire the semaphore when CSN goes low. If the SPI slave does not manage to

acquire the semaphore at this point, the transaction will be ignored. This means that all incoming data on

MOSI will be discarded, and the DEF (default) character will be clocked out on the MISO line throughout

the whole transaction. This will also be the case even if the semaphore is released by the CPU during the

transaction. In case of a race condition where the CPU and the SPI slave try to acquire the semaphore at

the same time, as illustrated in lifeline item 2 in SPI transaction when shortcut between END and ACQUIRE

is enabled on page 385, the semaphore will be granted to the CPU.

If the SPI slave acquires the semaphore, the transaction will be granted. The incoming data on MOSI will

be stored in the RXD buffer and the data in the TXD buffer will be clocked out on MISO.

When a granted transaction is completed and CSN goes high, the SPI slave will automatically release the

semaphore and generate the END event.

As long as the semaphore is available the SPI slave can be granted multiple transactions one after the

other. If the CPU is not able to reconfigure the TXD.PTR and RXD.PTR between granted transactions, the

same TX data will be clocked out and the RX buffers will be overwritten. To prevent this from happening,

the END_ACQUIRE shortcut can be used. With this shortcut enabled the semaphore will be handed over

to the CPU automatically after the granted transaction has completed, giving the CPU the ability to update

the TXPTR and RXPTR between every granted transaction.

If the CPU tries to acquire the semaphore while it is assigned to the SPI slave, an immediate handover

will not be granted. However, the semaphore will be handed over to the CPU as soon as the SPI slave

has released the semaphore after the granted transaction is completed. If the END_ACQUIRE shortcut

is enabled and the CPU has triggered the ACQUIRE task during a granted transaction, only one ACQUIRE

request will be served following the END event.

The MAXRX register specifies the maximum number of bytes the SPI slave can receive in one granted

transaction. If the SPI slave receives more than MAXRX number of bytes, an OVERFLOW will be indicated

in the STATUS register and the incoming bytes will be discarded.

The MAXTX parameter specifies the maximum number of bytes the SPI slave can transmit in one granted

transaction. If the SPI slave is forced to transmit more than MAXTX number of bytes, an OVERREAD will be

indicated in the STATUS register and the ORC character will be clocked out.

4430_161 v1.0

384

NRF52810-QCAA-R Datasheet(PDF) 384 Page - Nordic Semiconductor

NRF52810-QCAA-R Datasheet(HTML) 384 Page - Nordic Semiconductor

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL