How to use 51822 RTC on softdevice?

RE: How to use 51822 RTC on softdevice?

Mr.M — Tue, 20 Jun 2017 08:22:47 GMT

Ok, thanks for your help !

RE: How to use 51822 RTC on softdevice?

Jørgen Holmefjord — Tue, 20 Jun 2017 08:18:38 GMT

Yes, you can use app timer to create more timers using RTC1 in the application.

RE: How to use 51822 RTC on softdevice?

Mr.M — Tue, 20 Jun 2017 08:17:19 GMT

thanks for your replay,you are right,when I want to use RTC1 ,the complier prompts me that Error: L6200E: Symbol RTC1_IRQHandler multiply defined (by app_timer.o and nrf_drv_rtc.o). So, if I want to use RTC in ble_app_uart_example, I'll just use app_timer ?

RE: How to use 51822 RTC on softdevice?

Jørgen Holmefjord — Tue, 20 Jun 2017 08:02:00 GMT

Hi,

From the softdevice specifications, you can see that RTC0 is blocked by the softdevice, not RTC1. You should be able to use RTC1, but note that the ble_app_uart example use the BSP module, which again use the app_timer library. The app_timer use RTC1, so you might see some conflicts if using RTC1 for other tasks.

You should check the error codes returned by the function calls, as RK suggested.

Best regards,

Jørgen

RE: How to use 51822 RTC on softdevice?

RK — Tue, 20 Jun 2017 04:12:00 GMT

ok that's good because if it's in the app_error_fault_handler() it probably got there because a function returned non-zero and was checked by APP_ERROR_CHECK() so you should have a stack trace saying how you got there plus the error code. If you find the function which returned the non-zero code plus the code, it should be fairly simple from there to work out why.

RE: How to use 51822 RTC on softdevice?

Mr.M — Tue, 20 Jun 2017 04:01:37 GMT

thanks for your replay,Maybe I didn't describe it clearly.The problem is that when I add the function rtc_config() ,the program will run into app_error_fault_handler();

RE: How to use 51822 RTC on softdevice?

RK — Tue, 20 Jun 2017 03:50:25 GMT

how about providing more information about what 'can not run' means, what error messages you've seen, what debugging you've attempted and perhaps a code snippet.