SDK 15.3.0 Flash_fstorage example not working as expected

RE: SDK 15.3.0 Flash_fstorage example not working as expected

Amanda Hsieh — Fri, 22 Nov 2019 08:47:04 GMT

The reason for this behavior is the following: When flash is erased, all bits in flash is set to '1'. Writing to flash consists of setting the necessary bits to '0'. Setting bits back to '1' can only be done by erasing the flash page.

If you did not erase the flash, some of them will already be '0', and some new ones will have to be switched. In addition, some bits that should be '1' will also be '0', because it is already written before. Therefore, it will not work as you expect.

Please also see this post.

-Amanda H.

RE: SDK 15.3.0 Flash_fstorage example not working as expected

BEplane — Thu, 21 Nov 2019 13:52:54 GMT

I was able to get the example to work by erasing the board first.

In SES:

Target >> Connect J-Link
Target >> Erase All
Target >> Download

Do you have an explanation of why this does not work if you do not erase? The idea is that you are writing to flash, so regardless of what is there I would expect the value to be written?

RE: SDK 15.3.0 Flash_fstorage example not working as expected

Amanda Hsieh — Thu, 21 Nov 2019 12:34:25 GMT

Hi Paul,

Could you erase the flash with the following command and load the image again?

nrfjprog -e

I tested the project under \nRF5_SDK_15.3.0_59ac345\examples\peripheral\flash_fstorage\pca10056\s140. It could work as the following figure, and you also could view the values in the Segger memory window.

-Amanda H.