// process the BLE events in the stack
I'm still struggling in solving this issue...
I'm using a pin to understand where we have the "crash", I'm driving this pin High, just after I put the chip in low power mode.
and when it crashes the pin stays high, indicating that the issue happens inside CyBle_ProcessEvents();
Any idea ?
Can you give more details about the issue. I tried to port this code to development kit, I have changed the switch input to P2.7. Now after pressing the switch I'm able to see the device advertising.
1)Can you Attach the device to Running Target and check where exactly its getting stuck.
2)Did you get a chance to probe PWM_OUT? Is it staying high continuously?
3)Are you able to recreate the issue on development kit?
it seems that the firmware is getting "trapped" inside the CyBle_ProcessEvents(); for some reason...
driving the pin PWM_OUT high and low, I think I have managed to prove that.
the Heap is set to 0x200 and the Stack is 0x1000...
When this "crash" happens, I have proved that WDT ISR and Button ISR are still working...
I have made one change that maybe has fixed the issue (but it doesn't make sense yet to me)
I have changed the IMO clock from 3 MHZ to 16 MHz
Now on 5 units, I'm unable to reproduce the issue.
Did I fix the issue? why this should make a difference?
I assume you are using a custom board. Can you try if you are able to recreate the issue on development kit. We would like to see if this is hardware specific issue.