nrf_drv_qspi_write taking around 500 micro sec ( long time to write ) . Why it could be problem ?

[ARPITHA CHANDRASHEKAR]

nrf_drv_qspi_write taking around 500 micro sec ( long time to write ) . How to optimize nrf_drv_qspi_write time.?

[Amanda Hsieh]

Hi, 

How much data are you writing in nrf_drv_qspi_write()? When you called nrf_drv_qspi_init(&config, ...), what was the parameter for config.phy_if.sck_freq?

-Amanda H.

[ARPITHA CHANDRASHEKAR]

Hi,

      We are using 32 Mhz clock still getting 600 micro sec per transaction. Isnt it huge?

[Amanda Hsieh]

Hi,

Not sure about your calculations, but it is 32Mb/s * 4 = 128Mbps, so 512 bytes should take 4µs. However, that means that 600µs is even longer. 

May I know how you measure the time, and what other things your application is doing? Are you using BLE? If so the softdevice may be busy using the radio. Do you get 600µs every time or sometimes only? If only sometimes, it may suggest that the softdevice keeps the CPU busy. Do you have an event handler or a blocking call to the tx function?

-Amanda H.

[ARPITHA CHANDRASHEKAR]

Yes 32Mbits / sec * 4 = 128 MBits/sec = 128/8 Mbytes/sec = 16 Mbytes / sec. Ideally 512 bytes of transfer should take 32 micro sec. I am seeing 600 micro sec consistently. Yes we are using BLE. We have an event handler in nand_flash_init function? Which event handler are you talking about?