PSoC™ 6 Forum Discussions

Hi everybody,

I'm working on project with a PSoC 6, using MTB 3.1, Eclipse as IDE and when initiating "Building Application" the "Auto-discovery in progress..." takes forever and makes a fast working impossible.  How can I make this faster, like the fast incremental builds one is used form other build systems?

BR

Bernhard

I have an application on a PSOC63 with FreeRTOS running BLE in dual-core mode. It offload data quickly through bursts of large notifications (512 ATT MTU size, 495 byte payload). The project follows the examples of  "CE223508_PSoC6_BLE_MultiSlave_RTOS" for setting up a BLE Task capable of handling multiple slaves (BLE connections), and the offload/notification parameters of "CE222046_Throughput_Measurement" for maximum throughput.

All notifications are sent from this method, where the connection status, busy status and notification enable status are checked before calling the API:

uint8_t i;
/* Send notification top all the connected device */
for(i = 0; i < CY_BLE_CONN_COUNT; i++)
{
    /* Confirm that the BLE stack is ready */
    if (Cy_BLE_GATT_GetBusyStatus(appConnHandle[i].attId) == CY_BLE_STACK_STATE_FREE)
    {
        /* Check if the client/slave is both connected and subscribed to this notification */
        if((Cy_BLE_GetConnectionState(appConnHandle[i]) ==  CY_BLE_CONN_STATE_CONNECTED )&&
            Cy_BLE_GATTS_IsNotificationEnabled(&appConnHandle[i], handleValuePair.attrHandle))
        {
            /* Send BLE notification */
            cy_stc_ble_gatts_handle_value_ntf_t param =
             {
                /* Fill all fields of the Write request structure ... */
                .connHandle    = appConnHandle[i],
                .handleValPair = handleValuePair,
            };
            
            bleApiResult = Cy_BLE_GATTS_Notification(&param);
            
            /* Check if the operation has been successful */
            if(bleApiResult == CY_BLE_SUCCESS)
            {
                DebugPrintf("Info     : BLE - Sent notification. \r\n");
            }
            else
            {
                DebugPrintf("Failure! : BLE - Sending notification. Error Code: %d \r\n", bleApiResult);
            }
        }
    }
    else
    {
        /* Stack is busy, the current notification data will be dropped */ 
        Task_DebugPrintf("Error    : BLE - Stack busy to send notification", 0u);
    }
}

When the "Maximum number of BLE connections" is set to 1 in the BLE component, the application runs with no issue. However, if the "Maximum number of BLE connections" is set to 2, I begin to receive "CY_BLE_ERROR_MEMORY_ALLOCATION_FAILED" error responses from the Cy_BLE_GATTS_Notification (or Cy_BLE_GATTS_SendNotification) methods when sending notifications rapidly, which eventually results in a CM4 Fault. A second BLE device does not need to connect to cause this issue, just allowing a second seems to cause it. At no time during the calling sending of notification do I see the STACK_BUSY event. I call Cy_BLE_ProcessEvents()  before and after the send notification.

I've tried debugging this from every angle, changing the size of the BLE message payloads, changing the allotted RAM of CM0 and CM4, but cannot get the issue resolved.