Debugging With app_scheduler?

[lorenzoFIL]

Hi All,

Hopefully this is just a quick question... but I was wondering, if I set a breakpoint in my program while I am using the app_scheduler and app_timer2, should this cause an error? 

The code I'm currently working on is based off of the ble hid mouse example, so it was using the app scheduler. So I know when using a soft device, you cannot set breakpoints, but I thought that if I deactivated it, I would be able to use breakpoints again. (I'm trying to create a version of my code that does not use BLE)

Anyways, I was finding that without the soft device, I was still running into an error, seems like error 0x4 which corresponds to a full queue? My thinking then is that when I have a breakpoint, the timer and scheduler are still running, and so my queue ends up full? Is this the right way of thinking?

[Kenneth]

Do you know whi api call return queue full? Typically clocks are still running when setting a breakpoint, so once you run code from breakpoint it likely will be many app timers that have experied yes. You can try to increase APP_TIMER_OP_QUEUE_SIZE and SCHED_QUEUE_SIZE to see if that helps.

Kenneth

[lorenzoFIL]

Hi,

I believe it's occuring in timer_expire() in app_timer2. Specifically when the code tries to do app_sched_event_put(). 

For the time being, I am not using the scheduler, and it seems to be working with breakpoints.

So all in all, it seems that my initial theory for why the breakpoints were causing a fault seems to be right... right? 

[Kenneth]

lorenzoFIL said:

So all in all, it seems that my initial theory for why the breakpoints were causing a fault seems to be right... right? 

Likely right yes.

Kenneth