Battery service & debug problem

RE: Battery service & debug problem

MartinBL — Wed, 08 Jun 2016 15:06:44 GMT

In your last image you have written DEBUGBLE_STACK_SUPPORT_REQD in one word while it is supposed to be DEBUG and BLE_STACK_SUPPORT_REQD. Also, try to enable "C99 mode".

RE: Battery service & debug problem

Greed — Tue, 07 Jun 2016 16:16:18 GMT

Thanks. Battery Service can work. But i still can't see the error in debug mode. There is my operation . First , I push the "step over" button. Second , It was stop at bsp_init(). Third , error_code doesn't have value in "call stack + locals" window. Like the picture below.

If I use this solution , I will see the error.Like the picture below.

RE: Battery service & debug problem

MartinBL — Tue, 07 Jun 2016 08:42:44 GMT

See my edited answer.

RE: Battery service & debug problem

Greed — Mon, 06 Jun 2016 15:12:59 GMT

I updated some information, thanks.

RE: Battery service & debug problem

MartinBL — Mon, 06 Jun 2016 14:37:22 GMT

What do you mean by "but it doesn't change by ADC"? Can you upload your project files in a .zip-file?

RE: Battery service & debug problem

MartinBL — Mon, 06 Jun 2016 14:31:40 GMT

I can't see your pictures. Can you please edit your original post and insert them there? Maybe you can post your main.c file as well? EDIT: never mind. I can see your pictures now.

RE: Battery service & debug problem

Greed — Mon, 06 Jun 2016 14:28:42 GMT

Hi, First , I set the breakpoint at adc_init() , and push the 'run' button.

Second , I push the 'step' button. It will stop , but i can't see the error_code value at Call Stack + Locals.

RE: Battery service & debug problem

MartinBL — Mon, 06 Jun 2016 11:54:06 GMT

Hi. You can see how to use the err_code and APP_ERROR_CHECK() here.

You should also be able to see the value of err_code if you look in the "Call Stack + Locals" field.

Do you get an error when you use the ADC?

EDIT:

It looks like your battery_level_meas_timeout_handler() timer is never called. This is because you are calling APP_TIMER_INIT() twice. You call it first inside timers_init(), as is standard procedure in the SDK. Then you create your battery timer with app_timer_create(). Then you call APP_TIMER_INIT() again, effectively overwriting the battery timer you just created. So the first thing you need to do is to uncommend APP_TIMER_INIT() in your main() function. If you start your debugger now you will see that ble_conn_params_init() returns an error. If you enter ble_conn_params_init() you will see that the error occurs when app_timer_create() is called. The returned error is error 4; NRF_ERROR_NO_MEM. This error is returned if the timer operations queue is full and what you need to do is to change

#define APP_TIMER_MAX_TIMERS            (2 + BSP_APP_TIMERS_NUMBER)                 /**< Maximum number of simultaneously created timers. */

#define APP_TIMER_MAX_TIMERS            (3 + BSP_APP_TIMERS_NUMBER)                 /**< Maximum number of simultaneously created timers. */

In your main file. This will allocate more memory to the app timer module.