hardware timer in nrf connect sdk - counter alarm sample

RE: hardware timer in nrf connect sdk - counter alarm sample

Salman — Tue, 26 Jul 2022 12:54:54 GMT

I check similar issues and came across this ticket.

NRF Connect v2.0.0 - merging 'alarm' sample with 'peripheral_uart' sample

it turns out that I can not use CONFIG_COUNTER_RTC0=y I have to use CONFIG_COUNTER_RTC2=y

Its working now.

RE: hardware timer in nrf connect sdk - counter alarm sample

Salman — Tue, 26 Jul 2022 11:36:41 GMT

I have changed the idle stack and main stack in prj.conf as below but still getting the exact same error.

RE: hardware timer in nrf connect sdk - counter alarm sample

Susheel Nuguru — Fri, 22 Jul 2022 05:09:45 GMT

> 00> [00:00:02.004,699] <err> os: Current thread: 0x20001e20 (idle 00)

This shows that the hardfault seems to be happening in the idle thread, so I would suggest you to increase the idle stack and main stack sizes to begin with.

RE: hardware timer in nrf connect sdk - counter alarm sample

Salman — Thu, 21 Jul 2022 06:19:53 GMT

I will check the it on the DK as well. Mean while can you tell me from where I can change the stack sizes?

RE: hardware timer in nrf connect sdk - counter alarm sample

Susheel Nuguru — Thu, 21 Jul 2022 06:17:55 GMT

Have you tried to run the same application on the nRF52 DK? if you do not get the same error on the DK then it must be something with your custom board. If you get the same error on the DK, then we need to focus on the changes you made in your application.

It is saying that there is a hardfault in the idle thread, one of the common reasons that could happen is due to stack overflow. Have you checked if your application have set up enough stack sizes for the threads?