This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
hi,
Following steps are carrying out to iOS phone with ECU.
-connect the smartphone
- open the app
- close the Bluetooth of the smartphone
- wait some minutes (10-15)
- go outside the range of the unit (2 floors or 100m).
- come back in range and activate again the Bluetooth
I wont connecting to iOS smartphone again it showing "GAP_LE_Authentication_Response Failed: -512".
Hi Amir,
I've assigned an expert to comment. In the meantime, can you answer the following questions?
Hi Ammar,
Thank you for reply!
We have Bluetooth BT chip P/N : BL6450CQRVMR and Stack is TI Bluetopia 4.2.1.0
This project is Automotive based where ECU is integrated with BLE. The smartphone and this ECU connected via Bluetooth for Call management and music management.
First we connect the iOS device and disconnect for 15 min. In that time ECU goes in sleep mode. After when we try to reconnect iOS device whos information already stored in ECU after 15min.
It shows authentication failed This is message is showing when iOS device try to reconnect after 15 min. This following some log capture.
etLE_Authentication with size 36.
13:23:43.138 -> latKeyRequest:
13:23:43.138 -> BD_ADDR: 0x5B9109CC7DFD.
13:23:43.138 -> BD_ADDR: 0x5E8F405B6272.
13:23:43.138 -> Address Resolved
13:23:43.138 -> valid LTK :
13:23:43.138 -> get pairing info :
13:23:43.138 -> GAP_LE_Authentication_Response Failed: -512.
13:09:04.564 -> GAP_LE_Advertising_Enable success : 0
13:09:04.564 ->
13:09:04.564 -> Pairing Mode Enabled LE
13:09:04.564 ->
13:09:04.564 -> SetDisc successful : 0
13:09:04.564 -> Pairing Mode Enabled Classic
13:09:11.916 ->
13:09:11.916 -> atIOCapabilityResponse: 0xF0766FE1DB0D
13:09:11.916 -> Capabilities: Display Yes/No
13:09:11.916 ->
13:09:11.916 -> atIOCapabilityRequest: 0xF0766FE1DB0D
13:09:11.916 -> Auth success.
13:09:12.053 ->
13:09:12.053 -> atUserConfirmationRequest: 0xF0766FE1DB0D
13:09:12.053 ->
13:09:12.053 -> Auto Accepting:
13:09:12.053 -> GAP_Authentication_Response success.
13:09:12.992 -> Un-handled Auth. Event.
13:09:13.027 ->
13:09:13.027 -> atLinkKeyCreation: 0xF0766FE1DB0D
13:09:13.096 ->
13:09:13.096 -> BD_ADDR: 0xF0766FE1DB0D.
13:09:13.234 ->
13:09:13.234 -> HFRE Open Port Indication, ID: 0x0001, Board: 0xF0766FE1DB0D.
13:09:13.269 ->
13:09:13.269 -> OpenPortIndication: Number of active connections: 1
13:09:13.339 ->
13:09:13.339 -> HID Open Indication, ID: 0x001D, Board: 0xF0766FE1DB0D
13:09:13.444 -> etHFRE_Control_Indicator_Status_Confirmation: Serverportindex : 0
13:09:13.444 -> HFRE Control Indicator Status Confirmation, ID: 0x0001
13:09:13.444 -> Description: SERVICE
13:09:13.444 -> Value : FALSE.
13:09:13.444 -> ServerPortIndex : 1.
13:09:13.444 -> IsConnected : TRUE.
13:09:13.479 -> IsInActiveSCO : FALSE.
13:09:13.479 -> IsInActiveAudio : FALSE.
13:09:13.479 -> etHFRE_Control_Indicator_Status_Confirmation: Serverportindex : 0
13:09:13.479 -> HFRE Control Indicator Status Confirmation, ID: 0x0001
13:09:13.479 -> Description: CALL
13:09:13.479 -> Value : FALSE.
13:09:13.479 -> ServerPortIndex : 1.
13:09:13.479 -> IsConnected : TRUE.
13:09:13.479 -> IsInActiveSCO : FALSE.
13:09:13.479 -> IsInActiveAudio : FALSE.
13:09:13.479 -> etHFRE_Control_Indicator_Status_Confirmation: Serverportindex : 0
13:09:13.479 -> HFRE Control Indicator Status Confirmation, ID: 0x0001
13:09:13.514 -> Description: CALLSETUP
13:09:13.514 -> Value : 0.
13:09:13.514 -> ServerPortIndex : 1.
13:09:13.514 -> IsConnected : TRUE.
13:09:13.514 -> IsInActiveSCO : FALSE.
13:09:13.514 -> IsInActiveAudio : FALSE.
13:09:13.514 -> etHFRE_Control_Indicator_Status_Confirmation: Serverportindex : 0
13:09:13.514 -> HFRE Control Indicator Status Confirmation, ID: 0x0001
13:09:13.514 -> Description: BATTCHG
13:09:13.514 -> Value : 3.
13:09:13.514 -> ServerPortIndex : 1.
13:09:13.514 -> IsConnected : TRUE.
13:09:13.514 -> IsInActiveSCO : FALSE.
13:09:13.548 -> IsInActiveAudio : FALSE.
13:09:13.548 -> etHFRE_Control_Indicator_Status_Confirmation: Serverportindex : 0
13:09:13.548 -> HFRE Control Indicator Status Confirmation, ID: 0x0001
13:09:13.548 -> Description: SIGNAL
13:09:13.548 -> Value : 1.
13:09:13.548 -> ServerPortIndex : 1.
13:09:13.548 -> IsConnected : TRUE.
13:09:13.548 -> IsInActiveSCO : FALSE.
13:09:13.548 -> IsInActiveAudio : FALSE.
13:09:13.548 -> etHFRE_Control_Indicator_Status_Confirmation: Serverportindex : 0
13:09:13.548 -> HFRE Control Indicator Status Confirmation, ID: 0x0001
13:09:13.582 -> Description: ROAM
13:09:13.582 -> Value : FALSE.
13:09:13.582 -> ServerPortIndex : 1.
13:09:13.582 -> IsConnected : TRUE.
13:09:13.582 -> IsInActiveSCO : FALSE.
13:09:13.582 -> IsInActiveAudio : FALSE.
13:09:13.617 ->
13:09:13.617 -> HFRE Open Service Level Connection Indication, ID: 0x0001
13:09:13.617 -> RemoteSupportedFeaturesValid : TRUE
13:09:13.617 -> RemoteSupportedFeatures : 0x000007EF
13:09:13.617 -> RemoteCallHoldMultipartySupport : 0x0000006F
13:09:13.651 -> HFRE Enable Call Line Identification 0
13:09:13.651 -> HFRE Enable Remote Call Waiting Notification
13:09:13.651 -> StatusResult 0
13:09:13.651 -> ServerPortIndex : 1.
13:09:13.651 -> IsConnected : TRUE.
13:09:13.651 -> IsInActiveSCO : FALSE.
13:09:13.651 -> IsInActiveAudio : FALSE.
13:09:13.685 ->
13:09:13.685 -> HFRE Command Result, ID: 0x0001
13:09:13.685 -> Type 0
13:09:13.685 -> Code 0.
13:09:13.685 ->
13:09:13.685 -> HFRE Command Result, ID: 0x0001
13:09:13.685 -> Type 0
13:09:13.685 -> Code 0.
13:09:26.183 ->
13:09:26.183 -> etLE_Connection_Complete with size 16.
13:09:26.183 -> Status: 0x00.
13:09:26.183 -> Role: Slave.
13:09:26.183 -> Address Type: Random.
13:09:26.183 -> BD_ADDR: 0x5E8F405B6272.
13:09:26.183 -> Connection_Interval: 30.
13:09:26.183 -> Slave_Latency: 0.
13:09:26.183 -> Supervision_Timeout: 720.
13:09:26.183 -> >> Step 1 : LE_CONN_SUCCESS
13:09:26.183 ->
13:09:26.183 -> etGATT_Connection_Device_Connection with size 16:
13:09:26.217 -> Connection ID: 7.
13:09:26.217 -> Connection Type: LE.
13:09:26.217 -> Remote Device: 0x5E8F405B6272.
13:09:26.217 -> Connection MTU: 23.
13:09:26.392 -> MTU update: 83>> Step 2 : SMID : PAIR
13:09:27.290 -> >> Step 3 : SMNAME_Success
13:09:27.359 ->
13:09:27.359 -> HFRE_Close_Port: Function Successful.
13:09:27.359 -> SetDisc disable successful
13:09:27.359 -> Pairing Mode Disabled
13:09:27.394 -> >>Step 4: Pair_Success
13:09:28.403 ->
13:09:28.403 -> OS type Requested>>Step 6: OS identified : 49
13:09:28.438 -> Attempting to Pair to 0x5E8F405B6272.
13:09:28.438 -> GAP_LE_Request_Security returned 0.
13:09:28.508 ->
13:09:28.508 -> etLE_Authentication with size 36.
13:09:28.508 -> Pairing Request: 0x5E8F405B6272.
13:09:28.508 -> IO Capability: lcKeyboardDisplay.
13:09:28.508 -> MITM: FALSE.
13:09:28.508 -> Bonding Type: Bonding.
13:09:28.508 -> OOB: OOB Not Present.
13:09:28.508 -> Secure Connections: SC Pairing.
13:09:28.543 -> Keypress Notifications: NO.
13:09:28.543 -> Encryption Key Size: 16.
13:09:28.543 -> Sending Keys:
13:09:28.543 -> LTK: YES.
13:09:28.543 -> IRK: YES.
13:09:28.543 -> CSRK: NO.
13:09:28.543 -> Receiving Keys:
13:09:28.543 -> LTK: YES.
13:09:28.543 -> IRK: YES.
13:09:28.543 -> CSRK: NO.
13:09:28.543 -> Sending Pairing Response to 0x5E8F405B6272.
13:09:28.543 -> GAP_LE_Authentication_Response returned 0.
13:09:28.648 -> Local BD_ADDR: 0xF8300290FB9D
13:09:32.256 ->
13:09:32.256 -> etLE_Authentication with size 36.
13:09:32.256 -> latConfirmationRequest : TRUE.
13:09:32.256 -> Invoking Just Works.
13:09:32.815 ->
13:09:32.815 -> etLE_Encryption_Change with size 27.
13:09:32.815 -> Paired in LE Secure Connections mode.
13:09:32.815 -> Saved the LTK for this device.
13:09:32.883 ->
13:09:32.883 -> etLE_Authentication with size 36.
13:09:32.883 -> identity Information from RemoteDevice: 0x5E8F405B6272.
13:09:32.883 -> StoreBonding: BD_ADDR: 0x5E8F405B6272.
13:09:32.883 ->
13:09:32.883 -> etLE_Authentication with size 36.
13:09:32.918 -> Pairing Status: 0x5E8F405B6272.
13:09:32.918 -> Status: 0x00.
13:09:32.918 -> Key Size: 16.
13:09:32.918 -> ANS GATT_Start_Service_Discovery() success.
13:09:33.439 ->
13:09:33.439 -> Service 0x0014 - 0x0017, UUID: 180F.
13:09:33.474 ->
13:09:33.474 ->
13:09:33.474 -> 2A19
13:09:33.856 -> Service 0x0023 - 0x002C, UUID: 7905F431B5CE4E99A40F4B1E122D00D0.
13:09:33.856 ->
13:09:33.856 ->
13:09:33.856 -> 69D1D8F345E149A898219BBDFDAAD9D9
13:09:33.856 -> 9FBF120D630142D98C5825E699A21DBD
13:09:33.856 -> Notification_Sourse 28
13:09:33.856 ->
13:09:33.856 -> 22EAC6E924D64BB5BE44B36ACE7C7BFB
13:09:34.199 -> Service 0x002D - 0x0038, UUID: 89D3502B0F36433A8EF4C502AD55F8DC.
13:09:34.199 ->
13:09:34.199 ->
13:09:34.199 -> 9B3C81D857B14A8AB8DF0E56F7CA51C2
13:09:34.199 -> 2F7CABCE808D411F9A0CBB92BA96C102
13:09:34.199 -> C6B2F38C23AB46D8A6ABA3A870BBD5D7
13:09:34.234 -> Service Discovery Operation Complete, Status 0x00.
13:09:34.234 ->
13:09:34.234 -> ANS Service Discovery Summary
13:09:34.234 -> Supported New Alert Category: Supported
13:09:34.234 -> Attempting to configure CCCDs...
13:09:34.234 ->
13:09:34.234 -> Success - AMS found on this device : 45GATT_Write_Request successful : 46
13:09:34.234 -> Success - BAT_level Service found on this device : 47 GATT_Read_Value_Request successfulCCCD Configuration Success.
13:09:34.234 -> 2f
13:09:34.306 -> Write Response.
13:09:34.306 -> Connection ID: 7.
13:09:34.306 -> Transaction ID: 43.
13:09:34.306 -> Connection Type: LE.
13:09:34.306 -> BD_ADDR: 0x5E8F405B6272.
13:09:34.306 -> Bytes Written: 2.
13:09:34.336 ->
13:09:34.336 -> Write Response.
13:09:34.371 -> Connection ID: 7.
13:09:34.371 -> Transaction ID: 44.
13:09:34.371 -> Connection Type: LE.
13:09:34.371 -> BD_ADDR: 0x5E8F405B6272.
13:09:34.371 -> Bytes Written: 2.
13:09:34.406 ->
13:09:34.406 -> Write Response.
13:09:34.406 -> Connection ID: 7.
13:09:34.406 -> Transaction ID: 45.
13:09:34.406 -> Connection Type: LE.
13:09:34.406 -> BD_ADDR: 0x5E8F405B6272.
13:09:34.406 -> Bytes Written: 2.
13:09:34.474 ->
13:09:34.474 -> Write Response.
13:09:34.474 -> Connection ID: 7.
13:09:34.474 -> Transaction ID: 46.
13:09:34.474 -> Connection Type: LE.
13:09:34.474 -> BD_ADDR: 0x5E8F405B6272.
13:09:34.474 -> Bytes Written: 8.
13:09:34.474 ->
13:09:34.474 -> PlayBack Datasource : 0 0 0 4d 75 73 69 63
13:09:34.509 -> PlayBack Datasource : 0 1 0 30 2c 2c
13:09:34.543 -> Write Response.
13:09:34.543 -> Connection ID: 7.
13:09:34.543 -> Transaction ID: 47.
13:09:34.543 -> Connection Type: LE.
13:09:34.543 -> BD_ADDR: 0x5E8F405B6272.
13:09:34.543 -> Bytes Written: 2.
13:09:34.612 ->
13:09:34.612 -> Read Response.
13:09:34.612 -> Connection ID: 7.
13:09:34.612 -> Transaction ID: 48.
13:09:34.612 -> Connection Type: LE.
13:09:34.612 -> BD_ADDR: 0x5E8F405B6272.
13:09:34.646 -> Data Length: 1.
13:09:34.646 -> Data: { 0x2b }
13:09:58.363 ->
13:09:58.363 -> HCI Mode Change Event, Status: 0x00, Connection Handle: 1, Mode: Sniff, Interval: 384
13:10:05.953 -> GAP_Disconnect_Link successful
13:10:05.988 -> GAP Set cmNonConnectableMode success : 0SetDisc disable successful
13:10:05.988 -> Pairing Mode Disabled
13:10:05.988 -> Attempting to configure CCCDs...
13:10:05.988 ->
13:10:05.988 -> Success - AMS found on this device : 63
13:10:05.988 -> Success - BAT_level Service found on this device : 64 CCCD Configuration Success.
13:10:06.023 -> 40
13:10:06.023 -> HCI Mode Change Event, Status: 0x00, Connection Handle: 1, Mode: Active, Interval: 0
13:10:06.023 ->
13:10:06.023 -> HID Close Indication, ID: 0x001D
13:10:06.023 ->
13:10:06.023 -> Write Response.
13:10:06.023 -> Connection ID: 7.
13:10:06.023 -> Transaction ID: 61.
13:10:06.023 -> Connection Type: LE.
13:10:06.023 -> BD_ADDR: 0x5E8F405B6272.
13:10:06.056 -> Bytes Written: 2.
13:10:06.090 ->
13:10:06.090 -> Write Response.
13:10:06.090 -> Connection ID: 7.
13:10:06.090 -> Transaction ID: 62.
13:10:06.090 -> Connection Type: LE.
13:10:06.090 -> BD_ADDR: 0x5E8F405B6272.
13:10:06.090 -> Bytes Written: 2.
13:10:06.160 ->
13:10:06.160 -> Write Response.
13:10:06.160 -> Connection ID: 7.
13:10:06.160 -> Transaction ID: 63.
13:10:06.160 -> Connection Type: LE.
13:10:06.160 -> BD_ADDR: 0x5E8F405B6272.
13:10:06.160 -> Bytes Written: 2.
13:10:06.195 ->
13:10:06.195 -> Write Response.
13:10:06.230 -> Connection ID: 7.
13:10:06.230 -> Transaction ID: 64.
13:10:06.230 -> Connection Type: LE.
13:10:06.230 -> BD_ADDR: 0x5E8F405B6272.
13:10:06.230 -> Bytes Written: 2.
13:10:21.046 -> Baud Rate Updated: 9600
13:10:21.046 -> GAP_LE_Connection_Parameter_Update_Request Success : SLEEP Mode.
13:10:21.046 ->
13:10:21.046 -> APL_MOD_enableSleepMode : SUCCESS
13:10:21.183 ->
tLE_Connection_Parameter_Update_Response : 1.
13:10:21.598 ->
13:10:21.598 -> etLE_Connection_Parameter_Updated with size 14.
13:10:21.598 -> Status: 0x00.
13:10:21.633 -> BD_ADDR: 0x5E8F405B6272.
13:10:21.633 -> Connection Interval: 150.
13:10:21.633 -> Slave Latency: 0.
13:10:21.633 -> Supervision Timeout: 5000.
13:13:13.950 ->
13:13:13.950 -> etGATT_Connection_Device_Disconnection with size 12:
13:13:13.950 -> Connection ID: 7.
13:13:13.985 -> Connection Type: LE.
13:13:13.985 -> Remote Device: 0x5E8F405B6272.
13:13:13.985 ->
13:13:13.985 -> etLE_Disconnection_Complete with size 9.
13:13:13.985 -> >> Step Last : LE_DISCONN
13:13:13.985 -> Status: 0x00.
13:13:14.020 -> Reason: 0x13.
13:13:14.020 -> BD_ADDR: 0x5E8F405B6272.
13:13:14.020 -> DeleteDeviceInfoEntry : ElseGAP_LE_Advertising_Enable success : 0
13:13:15.206 ->
13:13:15.206 -> OpenStack().
13:13:16.146 -> Bluetooth Stack ID: 1
13:13:16.146 -> Change Output Power SuccessLOW ENERGY Support initialized.
13:13:16.285 -> Local BD_ADDR: 0xF8300290FB9D
13:13:16.355 -> Port Number: 1
13:13:16.355 -> HID_Register_Device_Server: Function Successful.
13:13:16.355 -> HID_Register_Device_SDP_Record: Function Successful.
13:13:16.355 -> successful HID initialization
13:13:16.355 -> Start of Firmware
13:13:16.390 -> GAP_LE_Advertising_Enable success : 0
13:13:16.390 ->
13:13:16.390 -> GAP Set cmNonConnectableMode success : 0Baud Rate Updated: 9600
13:13:31.458 ->
13:13:31.458 -> GAP_LE_Advertising_Disable Success
13:13:31.596 -> GAP_LE_Advertising_Enable success : 0
13:13:31.596 ->
13:13:31.596 -> APL_MOD_enableSleepMode : SUCCESS
13:13:36.614 -> Entering advertising sleep
13:23:42.998 ->
13:23:42.998 -> APL_MOD_disableSleepMode : Function Call : SuccessBaud Rate Updated: 115200
13:23:43.103 ->
13:23:43.103 -> APL_MOD_disableSleepMode Success
13:23:43.103 ->
13:23:43.103 -> etLE_Connection_Complete with size 16.
13:23:43.103 -> Status: 0x00.
13:23:43.103 -> Role: Slave.
13:23:43.103 -> Address Type: Random.
13:23:43.103 -> BD_ADDR: 0x5B9109CC7DFD.
13:23:43.103 -> Connection_Interval: 30.
13:23:43.103 -> Slave_Latency: 0.
13:23:43.103 -> Supervision_Timeout: 720.
13:23:43.103 -> >> Step 1 : LE_CONN_SUCCESS
13:23:43.103 ->
13:23:43.103 -> etLE_Authentication with size 36.
13:23:43.138 -> latKeyRequest:
13:23:43.138 -> BD_ADDR: 0x5B9109CC7DFD.
13:23:43.138 -> BD_ADDR: 0x5E8F405B6272.
13:23:43.138 -> Address Resolved
13:23:43.138 -> valid LTK :
13:23:43.138 -> get pairing info :
13:23:43.138 -> GAP_LE_Authentication_Response Failed: -512.
13:23:43.138 ->
13:23:43.138 -> etGATT_Connection_Device_Connection with size 16:
13:23:43.138 -> Connection ID: 1.
13:23:43.173 -> Connection Type: LE.
13:23:43.173 -> Remote Device: 0x5B9109CC7DFD.
13:23:43.173 -> Connection MTU: 23.
13:23:43.173 ->
13:23:43.173 -> etGATT_Connection_Device_Disconnection with size 12:
13:23:43.173 -> Connection ID: 1.
13:23:43.173 -> Connection Type: LE.
13:23:43.173 -> Remote Device: 0x5B9109CC7DFD.
13:23:43.173 ->
13:23:43.173 -> etLE_Disconnection_Complete with size 9.
13:23:43.173 -> >> Step Last : LE_DISCONN
13:23:43.173 -> Status: 0x00.
13:23:43.173 -> Reason: 0x3D.
13:23:43.173 -> BD_ADDR: 0x5B9109CC7DFD.
13:23:43.208 -> DeleteDeviceInfoEntry : IfDeleting EEPROM bonding infoGAP_LE_Advertising_Enable success : 0
13:23:43.662 ->
13:23:43.662 -> etLE_Connection_Complete with size 16.
13:23:43.662 -> Status: 0x00.
13:23:43.662 -> Role: Slave.
13:23:43.662 -> Address Type: Random.
13:23:43.662 -> BD_ADDR: 0x5B9109CC7DFD.
13:23:43.662 -> Connection_Interval: 30.
13:23:43.662 -> Slave_Latency: 0.
13:23:43.662 -> Supervision_Timeout: 720.
13:23:43.662 -> >> Step 1 : LE_CONN_SUCCESS
13:23:43.662 ->
13:23:43.662 -> etGATT_Connection_Device_Connection with size 16:
13:23:43.697 -> Connection ID: 2.
13:23:43.697 -> Connection Type: LE.
13:23:43.697 -> Remote Device: 0x5B9109CC7DFD.
13:23:43.697 -> Connection MTU: 23.
13:23:43.835 ->
13:23:43.835 -> etLE_Authentication with size 36.
13:23:43.835 -> latKeyRequest:
13:23:43.835 -> BD_ADDR: 0x5B9109CC7DFD.
13:23:43.835 -> BD_ADDR: 0x000000000000.
13:23:43.870 -> Address not Resolved
13:23:43.870 -> BD_ADDR: 0xFFFFFFFFFFFF.
13:23:43.870 -> Address not Resolved
13:23:43.870 -> BD_ADDR: 0xFFFFFFFFFFFF.
13:23:43.870 -> Address not Resolved
13:23:43.870 -> wont have LTK :
13:23:43.905 -> responsed :
13:23:43.940 ->
13:23:43.940 -> etGATT_Connection_Device_Disconnection with size 12:
13:23:43.975 -> Connection ID: 2.
13:23:43.975 -> Connection Type: LE.
13:23:43.975 -> Remote Device: 0x5B9109CC7DFD.
13:23:43.975 ->
13:23:43.975 -> etLE_Disconnection_Complete with size 9.
13:23:43.975 -> >> Step Last : LE_DISCONN
13:23:43.975 -> Status: 0x00.
13:23:43.975 -> Reason: 0x3D.
13:23:43.975 -> BD_ADDR: 0x5B9109CC7DFD.
13:23:43.975 -> DeleteDeviceInfoEntry : IfDeleting EEPROM bonding infoGAP_LE_Advertising_Enable success : 0
Hey Amir,
I've assigned an expert on the TI Bluetopia stack to assist you.
Can, you please provide FW logs..
Please, make sure the LTK is saved to NVM and restored upon reconnection request...
=================================
There are 2 parts of this implementation from the BT stack side to store the link key of a paired device in NVM.
- When a new device is paired, the atLinkKeyCreation event will occur in the GAP_Event_Callback. When this event occurs, you can see that the application is storing the link key in the following struct.
static LinkKeyInfo_t LinkKeyInfo[MAX_SUPPORTED_LINK_KEYS];
This struct is stored in the RAM, so it will not be retained over a power cycle. At this time, you can take a backup of the LinkKeyInfo in the NVM of the MCU.
- When the device powers up, read the backup that is stored in the NVM. Then you can pass this data to the LinkKeyInfo struct in the InitializeApplication() function after the OpenStack call is successful. This way, the previously stored LinkKeyInfo is restored after the power cycle and when the remote device tries to reconnect, the application will be able to use the previously stored link key. This occurs in the atLinkKeyRequest event of the GAP_Event_Callback.
===============================================