• State Verified Answer
  • Replies 2 replies
  • Subscribers 89 subscribers
  • Views 1113 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 128627
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Simply setting PSTORAGE_DATA_START_ADDR 0x4B000 causes BLE operation to become unreliable.

PACMAN

We are using an nrf52 with SoftDevice Version s132 v2.0.1.

We are loooking to use pstorage. For testing purposes we use the pstorage start address 0x78000(BANK1).

Altered below in pstorage_platform.h

#define PSTORAGE_DATA_START_ADDR    ((PSTORAGE_FLASH_PAGE_END - PSTORAGE_NUM_OF_PAGES - 1) \
//                                     PSTORAGE_FLASH_PAGE_SIZE)                                 /**< Start address for persistent data, configurable according to system requirements. /
#define PSTORAGE_DATA_START_ADDR    0x78000 // <-- WORKS

This seems to work fine. However when we try 0x4B000 (without carrying out any pstorage operations), the BLE "Just Works" functionality starts to have problems. A central device can connect, but is soon disconnected.

#define PSTORAGE_DATA_START_ADDR    0x4B000 <-- JUST WORKS BONDING HAS PROBLEMS

I believe 0x4B000 is also BANK1, and not BANK0.

The pstorage init is found in DM_init(Device Manager).

It looks like the setting is having some side effects. Any thoughts would be appreciated.

Related