This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Not enough room for the DFU

Hello,

I'm starting a new project on a NRF52810, and i need to use the pairing feature in my application. As a result i need to compile the FDS driver. If i'm doing so, i wont have enough room for the DFU.

Here is the memory mapping : 

- 0xFF8 -> 0x18FEB (SOFTDEVICE)

- 0x19000 -> 0x26EEB (APPLICATION)

- FDS should go here but there is not enough room for two pages ! (should use 0x27000 and 0x28000 pages)

- 0x28000 -> 0x2E000 (BOOTLOADER)

- 0x2E000 -> 0x2E00037F (USED BY THE BOOTLOADER SETTINGS ?)

- 0x2F000 -> 0x2F00037F (USED BY THE BOOTLOADER SETTINGS ?)

Is there a way to use the peer manager without the FDS ? Or do i need to switch on a different CPU such as the NRF52832 ?

Thank you in advance,

Best regards,

Aurélien

Parents
  • Hi Aurélien,

    The peer manager needs FDS for storing bonds, and there is no support for using the peer manager without FDS. (If you only need pairing and not bonding it you theoretically do not need to store anything persistently in flash, but there is no support for not including FDS in the peer manger even if it would not be needed in that special case).

    If you only need pairing and not bonding then an option could be to skip the peer manger and use SoftDevice APIs directly. The simplest case would be legacy just works pairing, which is explained in this message sequence chart.

Reply
  • Hi Aurélien,

    The peer manager needs FDS for storing bonds, and there is no support for using the peer manager without FDS. (If you only need pairing and not bonding it you theoretically do not need to store anything persistently in flash, but there is no support for not including FDS in the peer manger even if it would not be needed in that special case).

    If you only need pairing and not bonding then an option could be to skip the peer manger and use SoftDevice APIs directly. The simplest case would be legacy just works pairing, which is explained in this message sequence chart.

Children
Related