RE: Unknown bytes at several unused addresses after flashing firmware

mbozic — Thu, 28 May 2020 11:55:57 GMT

Ah, great!

Example on which I built my application is using FDS. I'm not using it directly but it's included in the project.

Which is great because I though I have an error somewhere or doing something wrong. 🙂

Thank you very much!

Br,

Mladen

RE: Unknown bytes at several unused addresses after flashing firmware

Jørgen Holmefjord — Thu, 28 May 2020 11:09:19 GMT

Hi,

What you are seeing is the Page tag of FDS. FDS is by default set to use 3 pages in most examples. These pages are initialized at run-time and are not included in the application HEX-file. If a bootloader is present, the FDS pages should be placed at the 3 pages right below the bootloader, otherwise at the top of the flash. If you do not explicitly use FDS in your application, it is also used by peer_manager library to store bonding data in flash. You did not say anything about how you flashed the chip, and if you erased it first, but I'm suspecting that you have previously run a non-bootloader application that utilizes FDS, and not preformed an "erase all" operation before flashing the application with bootloader merged? By default, only pages that contain data in the hex-file will be erased (section erase).

Best regards,
Jørgen