Nordic SDK QSPI driver call

[ARPITHA CHANDRASHEKAR]

Hi all,

             We had implemented Nordic QSPI using "nrf_drv_qspi_write" and "nrf_drv_qspi_read" operation , however I am seeing for page to write in flash of 4096 bytes with 512 bytes of QSPI write size limitation its taking 8.6 milli sec , when many streams (sensor data at stretch to be written into system) streams are getting hanged when flash logging is enabled .

So, wanted to check basic operations "nrf_drv_qspi_write" and "nrf_drv_qspi_read" if it blocks other sensor operations to process data ? Is it blocking call? If so how do we configure into dma mode?

Please help

[haakonsh]

The callback is called with the NRFX_QSPI_EVENT_DONE event when either a read, write, erase, or custom instruction has finished. 

Do note that the nRF52820 (as you've listed as the product) does not have a QSPI peripheral, only the nRF52840 and nRF5340 has one. 

[ARPITHA CHANDRASHEKAR]

its nRRF52840. 

[ARPITHA CHANDRASHEKAR]

Is there any way we could differentiate between read/write/erase ? I would want to have only for write

[haakonsh]

No, I'm afraid not. It's based on the HW signal called EVENTS_READY that is generated on any transfer completion. 

You'll have to put a SW state-machine on top of the driver in order to know what source triggered the EVENTS_READY signal.

[ARPITHA CHANDRASHEKAR]

Hi,

    1. Is there a way we could differentiate between read/write/erase. 

2. Do we need to set handler based Interrupt for qspi?

Right now NRFX_QSPI_CONFIG_IRQ_PRIORITY 6 .