• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 10 replies
  • Subscribers 63 subscribers
  • Views 6713 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 127258
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

fds data corrupted

Konstantin

Hello all,

My project based on NRF52832 SDK13 has some bug I trying to solve. Some users of my product very rarly faces with problem of constantly rebooting NRF52. After some investigations I'm revealed that the bond info sectors contain very strage data and the fds_init(void) function allways returns FDS_ERR_NO_PAGES. In the attachment you can find hex dump of those three sectors and screenshot of debug window with deatails about m_pages struct while in pages_init() function. I have build some protection code to just erase all fds pages in case of this error, but I want to understant the reason of error. May be it is already solved in SDK14?

Parents
  • 0

    The FDS is used only by Peer Manager, my own code uses flash write operation only through nrf_dfu_settings_write(). My project uses the bootloader and buttonless DFU. I performed DFU process many times without that type of error. I don't suspect the bootloader to be the reason of data corruption in the FDS storage. My first post is the result of debugging of fds_init(). I just saw very strange data in the FDS storage region (hex dump included) and thought that someone can explain possible reason of that sort of data. Can it be a result of interrupted garbage collection for example?

Reply
  • 0

    The FDS is used only by Peer Manager, my own code uses flash write operation only through nrf_dfu_settings_write(). My project uses the bootloader and buttonless DFU. I performed DFU process many times without that type of error. I don't suspect the bootloader to be the reason of data corruption in the FDS storage. My first post is the result of debugging of fds_init(). I just saw very strange data in the FDS storage region (hex dump included) and thought that someone can explain possible reason of that sort of data. Can it be a result of interrupted garbage collection for example?

Children
No Data
Related