Hi,
I am developing a device based on the PCA10059 board, SDK v15.3.0, and softdevice v6.1.1, and I want to imply that I am using the FDS module with 20 pages in my firmware.
I have a strange problem with PCA10059. I have a PCA10059 dongle which I am using for a while. problem is in this manner that, after programming the firmware hex file to this PCA10059 dongle through the DFU (with PCA10059 default bootloader) and the nrfConnect desktop version, instead of executing the programmed firmware bootloader enters in the DFU mode again (and the DFU led blinks with red light).
this happens while the generated hex file (which does not work in the old PCA10059) works fine on the fresh PCA10059 dongle.
as I know bootloader checks firmware integrity by calculating CRC of the firmware (and softdevice?) and comparing it to the stored CRC in the setting page during booting up and if it fails bootloader enters to DFU mode. but how it is possible that stored CRC in the setting page becomes corrupted?
any idea to solve this problem would be appreciated.
thanks
