1 Reply Latest reply on Sep 13, 2015 2:43 AM by rohit.kumar

    How to debug BLE stack

    robert.seczkowski

      After some time CustomEventHandler is not called.

         

      How to debug BLE stack?

         

      What is the requirement for BLE stack to call Event Handler?

         

      Why BLE stack source is not available?

         

       

         

      BLE stack looks as follows:

         

      void CustomEventHandler(uint32 event, void *eventParam) {

         

      }

         

       CyBle_Start( CustomEventHandler );

         

      for(;;){

         

      CyBle_ProcessEvents();

         

      }

        • 1. Re: How to debug BLE stack
          rohit.kumar

          CustomEventHandler will only be called when there is an activity on the BLE side. Such activities include connection, disconnection, advertisement/scanning start/stop, write request/response, MTU exchange request/response, etc. Unless it is a procedure that requires application intervention, the BLE stack will take care of the activities and the CustomEventHandler will not be called.

             

          For what activity are you expecting the CustomEventHandler to be called? Are there any interrupts in your design that have higher priority than bless interrupt and are being called frequently.?