How to store peer data in BLE peripheral to use after the BLE peripheral reboots?

RE: How to store peer data in BLE peripheral to use after the BLE peripheral reboots?

mirhamza708 — Mon, 09 Oct 2023 14:29:48 GMT

Okay guys i have solved my problem by using the app button instead of the bsp. Also i and not using the ble button module (i just created my own functionality with the app buttons.

RE: How to store peer data in BLE peripheral to use after the BLE peripheral reboots?

mirhamza708 — Fri, 06 Oct 2023 17:33:37 GMT

Yes, that's exactly the problem.

static void buttons_leds_init(bool * p_erase_bonds)
{
    ret_code_t err_code;
    bsp_event_t startup_event;

    err_code = bsp_init(BSP_INIT_LEDS | BSP_INIT_BUTTONS , bsp_event_handler);
//
    APP_ERROR_CHECK(err_code);

    //err_code = bsp_btn_ble_init(NULL, &startup_event);
    //APP_ERROR_CHECK(err_code);

    *p_erase_bonds = (startup_event == BSP_EVENT_CLEAR_BONDING_DATA);
    NRF_LOG_INFO("%d",startup_event);
}

I commented the two lines and now it works. I power cycled the board and I am able to connect. But now I need a little help in understanding the BLE buttons IDs. In the bsp_btn_ble.h I have these defines as shown in the code below I don't get where does this ID comes from like how is it actually connected to my actual buttons because I want to use one button on the mouse board, which when I press, should remove the bonding data or maybe some other function.

code snippet from bsp_btn_ble.h file

#define BTN_ID_WAKEUP             0  /**< ID of button used to wake up the application. */
#define BTN_ID_SLEEP              0  /**< ID of button used to put the application into sleep mode. */
#define BTN_ID_DISCONNECT         0  /**< ID of button used to gracefully terminate a connection on long press. */
#define BTN_ID_WAKEUP_BOND_DELETE 1  /**< ID of button used to wake up the application and delete all bonding information. */
#define BTN_ID_WHITELIST_OFF      1  /**< ID of button used to turn off usage of the whitelist. */

I have only defined 6 buttons in my custom_board_mouse.h file which looks like this

#define BUTTONS_NUMBER 6

#define BUTTON_1       2
#define BUTTON_2       3
#define BUTTON_3       4
#define BUTTON_4       5
#define BUTTON_5       12
#define BUTTON_6       28

#define BUTTON_PULL    NRF_GPIO_PIN_PULLUP

#define BUTTONS_ACTIVE_STATE 0

#define BUTTONS_LIST { BUTTON_1, BUTTON_2, BUTTON_3, BUTTON_4, BUTTON_5, BUTTON_6 }

#define BSP_BUTTON_0   BUTTON_1
#define BSP_BUTTON_1   BUTTON_2
#define BSP_BUTTON_2   BUTTON_3
#define BSP_BUTTON_3   BUTTON_4
#define BSP_BUTTON_4   BUTTON_5
#define BSP_BUTTON_5   BUTTON_6

How do I know which button from my custom_board_mouse.h file is given the ID of the, for example, BTN_ID_WAKEUP_BOND_DELETE. Or more importantly, how do i assign one of my buttons from custom_board_mouse.h file as BTN_ID_WAKEUP_BOND_DELETE.

Thank you so much for answering my previous question. If you give me some insight on this I would be really grateful.

RE: How to store peer data in BLE peripheral to use after the BLE peripheral reboots?

Einar Thorsrud — Fri, 06 Oct 2023 14:43:22 GMT

Hi,

There is no fundamental difference between a pin reset and a power-cycle when it comes to retaining the bonds, which is stored in flash, so I am suprised you see a difference in behavior. Is there any other difference between these two cases when you test?

Also, the SDK examples use a button hat is read at startup, and if pressed, bonds are deleted. Could that be the case here? Either that the button is pressed (if testing on a DK), or that this features is kept in the firmware even if your custom HW does not use this pin (so it is floating), or it is held low, for instance? You can see this code by searching for "delete_bonds" in main.c.

RE: How to store peer data in BLE peripheral to use after the BLE peripheral reboots?

mirhamza708 — Fri, 06 Oct 2023 07:30:29 GMT

I will add some more information that I just found out, If I reset the board with the reset push button then the peer data remains there and I can connect back to my laptop after push button reset. But after a power reset I am unable to reconnect.