Osal Snv Read in profiles

SkyMan

Hi,

when i call osal_snv_read in the sensortagTask, it's ok.

But when i call it in an BLE event like in irtempservice in

static bStatus_t sensor_WriteAttrCB(uint16_t connHandle, gattAttribute_t *pAttr,
                                    uint8_t *pValue, uint16_t len,
                                    uint16_t offset, uint8_t method)
{
  bStatus_t status = SUCCESS;
  uint8_t notifyApp = 0xFF;
  uint16_t uuid;

  // If attribute permissions require authorization to write, return error
  if (gattPermitAuthorWrite(pAttr->permissions))
  {
    // Insufficient authorization
    return (ATT_ERR_INSUFFICIENT_AUTHOR);
  }

  if (utilExtractUuid16(pAttr,&uuid) == FAILURE) {
    // Invalid handle
    return ATT_ERR_INVALID_HANDLE;
  }

  switch (uuid)
  {
    case SENSOR_DATA_UUID:
      // Should not get here
      break;

    case SENSOR_CONFIG_UUID:
       osal_snv_read(0x82,sizeof(pValue), &pValue);
       break;

like here, i execute exit()...

/****************************************************************************/
/*                                                                          */
/* LOADER_EXIT -							    */
/* 									    */
/* SET C$$EXIT LABEL SO THE DEBUGGER KNOWS WHEN THE C++ PROGRAM HAS	    */
/* COMPLETED.  THIS CAN BE REMOVED IF THE DEBUGGER IS NOT USED.		    */
/*                                                                          */
/****************************************************************************/
static void loader_exit(void)
{
#if defined(EMBED_CIO_BP)
   __asm("         .global C$$EXITE");
#if defined(__32bis__)
   __asm("C$$EXITE:.word 0xDEFED0FE");
#else
   __asm("	 .align  4");
#if defined(__big_endian__)
   __asm("C$$EXITE:.half 0xDEFE");
#else
   __asm("C$$EXITE:.half 0xD0FE");
#endif /* __big_endian__ */
#endif /* __32bis__      */

#else  /* !EMBED_CIO_BP */
   __asm("        .global C$$EXIT");
   __asm("C$$EXIT: nop");
#endif
}

I don't understand.

Thanks for your help.

over 9 years ago

0 Tim C over 9 years ago

TI__Mastermind 34660 points

sensor_WriteAttrCB is a callback function which executes in the BLE Stack context. osal_snv_read should not be called from the stack context because, among other reasons, it is a time-consuming process and could break the timing of the stack. In general you should limit processing in stack callbacks, similar to ISRs. I would recommend posting an event from the write attribute callback to the application and then performing the snv read in the application context.

See SensorTag_charValueChangeCBSensorTag_charValueChangeCB() for an example of this. This is also described in Section 4.3.3 of the SDG: www.ti.com/.../swru393b.pdf

Bluetooth®︎

Bluetooth forum

Osal Snv Read in profiles