Bug in hrs example?

[Michal]

I want to use FDS in my application. Lets assume I do not have a bootloader. This is part of my linker script describing memory regions.

MEMORY
{
  FLASH (rx) : ORIGIN = 0x1f000, LENGTH = 0x61000
  RAM (rwx) :  ORIGIN = 0x200024b0, LENGTH = 0xdb50
}

I defined 4 pages for FDS. I want to know if application code will overwrite my fds pages when reflashing assuming application will be bigger than 0x5d000. If so shouldn't FLASH region be 0x5d00 ? And another way: will fds overwrite my application code?

I saw that in ble_app_hrs_c application linker script looks like above but there are 3 pages for FDS. Isn't that a bug ? Or maybe there is protection mechanism

[FormerMember]

That memory section in the linker script tells which part of flash and RAM that is available for the application (including the FDS).

This answer explains where FDS data will be stored in flash.

Update 09.06.2017: Yes, you are right, the application could potentially overwrite the FDS space. So yes, changing the compilation flash settings to exclude the FDS space is the right thing to do, and the flash region length should be 0x5D000.

Note: FDS will not override the application.

[FormerMember]

I have updated my answer to answer your question.