Hello all,My code sends a command to a cyble-214015-1 writing a characteristic and then waits for a notification on the same charmtu is 70 bytes and n...
Show More
Hello all,
My code sends a command to a cyble-214015-1 writing a characteristic and then waits for a notification on the same char
mtu is 70 bytes and notify is 3 bytes: 32 2E 9B
Sometimes it works but sometimes it fails: after a timeout of 5 s I pause psoc creator 4.2 and I find this:
The timeout happens on my pc because the command is not syncronized with events, but I receive EVT_CONNECTION_TERMINATED_NOTIFICATION from cy5677, that is CYBLE_EVT_GAP_DEVICE_DISCONNECTED.
The device seems stucked
The function that sends the notification is:
void BLE_notify(uint16_t h, void * v, uint16_t lenght)
{
if (connesso) {
CYBLE_GATTS_HANDLE_VALUE_NTF_T hvntf = {
.attrHandle = h
} ;
uint8_t * dati = (uint8_t *) v ;
while (lenght) {
if (CYBLE_STACK_STATE_BUSY == CyBle_GattGetBusyStatus()) {
CyBle_ProcessEvents() ;
continue ;
}
uint16_t dim = lenght ;
if (dim > mtu-3)
dim = mtu-3 ;
hvntf.value.len = dim ;
hvntf.value.val = dati ;
CYBLE_API_RESULT_T ris = CyBle_GattsNotification(cyBle_connHandle, &hvntf) ;
CyBle_ProcessEvents() ;
switch (ris) {
case CYBLE_ERROR_OK:
DBG_PRINT_HEX("notif ", dati, dim) ;
lenght -= dim ;
dati += dim ;
break ;
case CYBLE_ERROR_MEMORY_ALLOCATION_FAILED:
// Bisogna aspettare che lo stack spedisca i dati
CyBle_ProcessEvents() ;
break ;
default:
// ??? esco
DBG_PRINTF("ERR %s %d ris = 0x%04X\n", __FILE__, __LINE__, ris) ;
lenght = 0 ;
break ;
case CYBLE_ERROR_INVALID_PARAMETER:
// notifiche disabilitate
DBG_ERR ;
lenght = 0 ;
break ;
case CYBLE_ERROR_INVALID_OPERATION:
// Riprovo
DBG_ERR ;
CyBle_ProcessEvents() ;
break ;
}
}
}
else {
DBG_ERR ;
}
}
What am I doing wrong?
Show Less
Solved
