• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 90 subscribers
  • Views 1320 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 282924
Options

storing sensor data to flash

kizhimon

Hi,

SDK - 17.1.0

I want to store my sensor data to the internal flash memory of nRF52810 for a long time. I have some questions here:

  1. The data sheet says the flash memory is 192 KB for nRF52810. How much memory from 192 kB will be available for user to store the data ? Please note that I am not using softdevice
  2. Which interface should I use and why ? (FDS or FSTORAGE)
Parents
  • 0

    1 Flash memory holds your code, initialization constants, nRF code modules (like FlashDataStorage code ).

    You need to link all these pieces and look at the load map to see what they have taken then you can determine how many PAGES you can allocate for FDS. The symbol __exide_end is the end of the used flash. Allocate the next higher page address ( xx000) as the  start address for .storage_flash section in the the link commands. Better to leave an extra page for code growth. 

    2 FDS supports variable length records assigned to files. each record uses 3 words of overhead (including the 2 byte record key and 2 byte fileID) . If your application expects to add/update/delete data FDS will manage those things for you. If you have many many small records (relative to the 3 words header) you should consider blocking them into almost page size records.(2 additional words of overhead are in each page).

    FSTORAGE simply uses pages.

Reply
  • 0

    1 Flash memory holds your code, initialization constants, nRF code modules (like FlashDataStorage code ).

    You need to link all these pieces and look at the load map to see what they have taken then you can determine how many PAGES you can allocate for FDS. The symbol __exide_end is the end of the used flash. Allocate the next higher page address ( xx000) as the  start address for .storage_flash section in the the link commands. Better to leave an extra page for code growth. 

    2 FDS supports variable length records assigned to files. each record uses 3 words of overhead (including the 2 byte record key and 2 byte fileID) . If your application expects to add/update/delete data FDS will manage those things for you. If you have many many small records (relative to the 3 words header) you should consider blocking them into almost page size records.(2 additional words of overhead are in each page).

    FSTORAGE simply uses pages.

Children
No Data
Related