geon, thank you for the response.
I did add the new custom service according to Step 1 in the linked OTA Fixed Stack document.
In the existing project I started from, I only had to call the CyBle_Start() function to get the services working.
I wound up solving the issue, and it turned out to be a mismatch of the GAP security settings in the BLE component.
When implementing the bootloader functionality, I started with the Bootloader project from the BLE_OTA_FixedStack_Bootloader example, then copied over the custom service from the existing BLE component, to the new one, and failed to check the GAP security settings which were different from what the phone application was expecting.
To find the error, I had added some serial output to the BLE callback, printing out the uint32 event number every time the callback was executed.
void bleCallback(uint32 event, void *event_param)
{
...
if (event != CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT)
{
char eventBuffer[10];
sprintf(eventBuffer, "%lu", event);;
send_serial(eventBuffer);
}
...
}
When connecting to the target with the iOS application, I could see that the CYBLE_EVT_GAP_AUTH_FAILED event was getting called twice.
I looked in the CyBle_Stack.h file to find the following.
/** Authentication process failed between two devices. The return value of type
CYBLE_GAP_AUTH_FAILED_REASON_T indicates the reason for failure. */
CYBLE_EVT_GAP_AUTH_FAILED,
This led to adding the following code to the BLE callback, found from this example.
case CYBLE_EVT_GAP_AUTH_FAILED:
authFailReason = ((CYBLE_GAP_AUTH_FAILED_REASON_T *)event_param);
char authFailReasonCode[3];
snprintf(authFailReasonCode, sizeof(authFailReasonCode), "%lu", (uint32)(*authFailReason));
send_serial("* Authentication Fail");
send_serial(authFailReasonCode);
The authentication reason code corresponded to CYBLE_GAP_AUTH_ERROR_INSUFFICIENT_ENCRYPTION_KEY_SIZE.
Reading the BLE_OTA_FixedStack_Bootloader.pdf, I found a mention on security on page 21.
I then used the PC CySmart application to match the security settings set in the GAP BLE component, and CySmart was able to see all of the services and actively exchange data with them. I changed the BLE component GAP settings to match what the iOS application was expecting, and the application was able to access all of the expected services again. So they were there, it just wasn't apparent that the authentication was failing with the iOS application.
