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.

About the library of the BLE-stack

Genius 5960 points

Hi,

There are described in the following part of the sample code CC254x keyfob.

○OSAL_KeyFobDemo.c 

const pTaskEventHandlerFn tasksArr[] = {   LL_ProcessEvent,                                            // task 0   Hal_ProcessEvent,                                           // task 1   HCI_ProcessEvent,                                           // task 2 #if defined ( OSAL_CBTIMER_NUM_TASKS )   OSAL_CBTIMER_PROCESS_EVENT( osal_CbTimerProcessEvent ),     // task 3 #endif   L2CAP_ProcessEvent,                                         // task 4   GAP_ProcessEvent,                                           // task 5   GATT_ProcessEvent,                                          // task 6   SM_ProcessEvent,                                            // task 7   GAPRole_ProcessEvent,                                       // task 8   GAPBondMgr_ProcessEvent,                                    // task 9   GATTServApp_ProcessEvent,                                   // task 10   KeyFobApp_ProcessEvent                                      // task 11 };

In the above code, you will not be able to check the contents and have become a library other than KeyFobApp_ProcessEvent.

I want to know the Write/Erase of Flash or being carried out in the library.

Information disclosure might be difficult for the library, but please cooperate.  

Best Regards,   hamada

  • Hello. The library portion of the stack writes to flash for the following reasons:

       - calibrating frequency tuning
       - calibrating Tx Power
       - calibrating clock stabilization time

    The GAP bond manager also writes to flash. You can look at this by searching for the following function:

      osal_snv_write()