NRF_SDH_BLE_GATTS_ATTR_TAB_SIZE and RAM_START blocks execution

[DamienB]

Hello,

After adding pairing using static passkey to my nRF52840 board, i am facing a memory issue :

At the beginning of execution, the code stopped as if there was a breakpoint (but there wasn't) in the disassembly window of Segger embedded studio.

To make it work, i add to increase NRF_SDH_BLE_GATTS_ATTR_TAB_SIZE  in sdk_config.h, and i had also to change the RAM_START address in the project option => Linker.

It was working fine, but the day after, it did the same error, without changing a line in the code, so i had to increase it again.

Now, i has been several days that i have to increase this lines again and again and the values are :

RAM_START=0x20003698

#define NRF_SDH_BLE_GATTS_ATTR_TAB_SIZE 2800

Sometimes, it works and i can go back to the values i putted the first time...

What can i do to avoid this problem ?

[DamienB]

If i comment out queue_start(); in fds_init() in fds.c, it works fine.
What do i have to do to make it works properly ? Is this line necessary ?

[Kenneth]

It should be "fairly straight forward" to add passkey to an example that already support bonding, e.g. \examples\ble_peripheral\ble_app_hrs and follow message sequence chart:

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.1.1/group___b_l_e___g_a_p___p_e_r_i_p_h___b_o_n_d_i_n_g___p_k___c_e_n_t_r_a_l___o_o_b___m_s_c.html 

Not sure what the problem is in your case, sounds like FDS is not really storing data to flash (but maybe just filling up the que with data to store).

[DamienB]

Well,  pairing using passkey works.

I moved my project to SDK 15.3.0 and Mesh 3.2.0 but i still have the same problem..