- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Only after software download does our central get the bond callback after a connection.
ie.
1. We download our app to central
2. Central connects to peripheral #1, and gets one bond callback, and communication is OK between central and peripheral, central disconnects.
3. Central connects to peripheral #2, gets 1 callback, comm OK between central and peripheral 2, central disconnects.
4. But now, central never gets another bond callback, EVEN IF POWER CYCLED, and NEVER AGAIN UNTIL SOFTWARE APP IS DOWNLOADED AGAIN.
Why is this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is a call lesmpkeys_removeAllBondInfo to do that. Meanwhile I strongly recommend against using that technique. That will make your solution very insecure with an easy way to break.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bonding is typically once in a lifetime event. After you bond LE stack saves the generated keys. When you start security next time around bonding will not happen, but encryption will be set. When you flash new FW the EEPROM/SFLASH is erased so bonding info is not saved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Victor. That explains it.
How can we erase this section of flash, to reset it?
Every time our board powers up, we want to reset these states that are stored in flash -- to reduce risk; so that when we reset or power up board, we know we are in the exact same reset state.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is a call lesmpkeys_removeAllBondInfo to do that. Meanwhile I strongly recommend against using that technique. That will make your solution very insecure with an easy way to break.