How to clear the bonding data every time you make a connection

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
3 posts / 0 new
Last post
sogabe
Offline
Last seen:3 years 2 months ago
加入:2017-09-19 05:34
How to clear the bonding data every time you make a connection

Hello, Dialog.

This time, we are developing software based on ble_app_all_in_one.
When pairing, I think that saving the bonding data to FLASH and not sending the advertisement packet.
I'd like to send the advertisement packet again after disconnecting.
Can you teach us an effective method of not saving bonding data or clearing bonding data?

Keywords:
Device:
STS_Dialog (not verified)
Hi sogababe,

Hi sogababe,

Please give me more information about:

1) What kind of advertising do you want to make after the connection (for example non connectable)?

2) How do you check that the system is blocked when the flash is erased?

BR,

STS_Dialog.

sogabe
Offline
Last seen:3 years 2 months ago
加入:2017-09-19 05:34
Thank you for your reply.

Thank you for your reply.

I'm sorry, I realized that I do not have to store the bonding data in FLASH.
It is in user_config.h
#定义USER_CFG_APP_BOND_DB_USE_SPI_FLASH
If you invalidate it, it is recognition that bonding data will not be saved in FLASH.
In my program, because I am using a secondary boot loader, I was thinking to use 0x1E000 ~ 0x1EFFF on FLASH memory map as user data storage area.
However, in app_bond_db.h, when USER_CFG_APP_BOND_DB_USE_SPI_FLASH is valid,
#define APP_BOND_DB_DATA_OFFSET (0x1E000)
Since this line becomes effective, it seems that offsets will collide.
I believe that this triggered my program to cause unstable behavior.
It seems that it can be solved by invalidating storage in FLASH.

Thank you very much.