According to the documentation:
Fixed Stack OTA Bootloader
In case of Fixed Stack OTA Bootloader, the bonding information is allocated in the scope of the bootloader project. Therefore, even after the bootloadable project is upgraded, bonding information is intact and will be erased only if the device is reprogrammed using a SWD programmer.
So, if we bonded while running the bootloadable, connection should be allowed when shifting into bootloader. And likewise, if a connection is made while running bootloader, the bonding keys should still be good after firmware upgrade is complete and the system runs the bootloadable. But I am not finding this to be the case. Even running the CySmart app, once I "Forget" the device so I can pair with it to do the OTA upgrade, I am unable to reconnect with the device until I first "Forget" again.
Has this problem be solved? I'm facing the same issue.Hope Cypress can help us to fix this.
I resolved the original issue by fixing the way I was saving the bonding keys. But now that I have updated from BLE component 2.30 to 3.10, it has resurfaced. But I can tell you the 'fix' is to be sure you are saving the bonding keys.
My application do not need bonding, So is it possible that bond in bootloader, but do not bond in bootloadable project.
Hi, when you say the fix is to make sure you are saving the bonding keys, are you doing this in the Bootloader code? Or the Bootloadable code?
In our setup, I'm saving the bonding info in the Bootloadable code, but not in the Bootloader code.