NRF Storage BUSY Error

[Vaibhav_Bansal]

I am implementing the BLE buttonless DFU 

SDK 14.2,

GCC compiler

softdevice 5.0.0

While writing the firmware data I am getting this error

00> INFO: ../../components/libraries/bootloader/dfu/nrf_dfu_flash.c +136 nrf_fstorage_write() failed with error 0x4.


00> INFO: ../../bootloaderVista/dfu_req_handling.c +1025 Failed 128 B address: 0x00047880

I tried increasing the NRF_FSTORAGE_SD_QUEUE_SIZE 1280

NRF_FSTORAGE_SD_MAX_RETRIES 16 

NRF_FSTORAGE_SD_MAX_WRITE_SIZE 128

I am writing data at 20 bytes per 2 ms after creating the data object successfully.

Any suggestion!!

[Edvin]

Hello,

Is dfu_req_handling.c a custom file? If so, I can't say why it fails.

Have you seen our implementation on the buttonless_dfu example in combination with our bootloader from the SDK?

By the look of things, if nrf_fstorage_write() returns NRF_ERROR_BUSY, it probably means that you are writing too fast to the flash. What decides how fast you call this?

BR,
Edvin

[Vaibhav_Bansal]

Hey,

I am successful in working with BLE DFU, but now I am trying to implement the SPI bootloader where I am reading the NRF firmware file from the external memory.

With BLE I had observed that Data transfer speed to quiet fast that currently I am using.
And also I tried to slow down data speed to 20 bytes per 20 ms, but still getting the same results.

[Edvin]

You should look into the application logic. If you call the flash write calls from within an interrupt, perhaps the chip doesn't release this interrupt, not allowing the fstorage module to write anything?

[Vaibhav_Bansal]

I am calling flash write from timer timeout interrupt.

Can you suggest me that why same logic is working over BLE,
because BLE also call this function from interrupt.

"ble_evt_handler" is called when we receive data from BLE and then according to the data this function is called. 
I am doing the same, in which every 100ms I am reading the data from external flash and calling the same function that BLE calls for writing the data.

But in BLE case softdevice for free but in other case it won't.

[Vaibhav_Bansal]

hey

I am able to figure our the solution, but getting hash error
Can you tell me the possible reason behind that and what will we the possible solution.

[Edvin]

I don't know why you get hash errors. Did you compare the image that you fetched via SPI with the image that was originally written? Is it identical? If not, why not? Is it the same length? Is it shorter? Try to find out why it is different.

In this solution, you have done a lot of custom work, so I am not sure why it is not working.

Did you generate the new image with nrfutil? Or are you only fetching the application's .hex file?

[Vaibhav_Bansal]

Hi 

I am able to resolve all and success with SPI bootloader for NRF,

Thanks for your support, you can close this ticket now.