Timer 1 has no Different resolution

RE: Timer 1 has no Different resolution

Stuart M — Thu, 22 Dec 2016 11:17:49 GMT

Sorry this is posting on an old post and I'm aware its probably not applicable for you anymore, but for reference ...

I have had similar issues with the documentation seeming vague with regards to this. As is kind of mentioned in RK's answer, the Reference Manual gives all the options for the device range, whereas the specifics of the exact chip you have are in the Product Specification document for your exact device.

In my case for the nrf51822, the reference manual (nRF51_RM_v3.0.pdf) says all the stuff about the timers being 8/16/32 bit. However the Product Specification (nRF51822_PS_v3.1.pdf) then says TIMER1/2 are 8/16 bit only (section 4.2).

RE: Timer 1 has no Different resolution

RK — Sat, 28 Mar 2015 00:29:47 GMT

From the nRF51 manual

"The TIMER's maximum value is configured by changing the bit-width of the timer in the BITMODE register. For details on which bitmodes are supporting which timers see the device product specification."

And then from the nRF51822 product spec

Instance        Bit-width        Capture/Compare registers
TIMER0         8/16/24/32         4
TIMER1         8/16                   4
TIMER2         8/16                   4

RE: Timer 1 has no Different resolution

michael.crapse — Fri, 27 Mar 2015 17:23:14 GMT

Thank you for your reply. When the Soft device is activated I use softdevice calls and set priority to 1. I would also like to know where this is documented? Looking at the Timer//Counter documentation in the reference manual It makes it seem vague and that each timer can be 8/24/32/16 bit timers.(as each timer has these resolution)

RE: Timer 1 has no Different resolution

RK — Thu, 26 Mar 2015 00:21:00 GMT

.. and a 20 second test with the debugger shows that indeed setting TIMER1->CC[0] to 75125 does indeed only set the lower 16 bits.

RE: Timer 1 has no Different resolution

RK — Wed, 25 Mar 2015 23:59:27 GMT

Well for a start TIMER1 and TIMER2 are 8 or 16 bit timers, they don't have a 24 or 32 bit mode. So I rather suspect

NRF_TIMER1->CC[0]=75125

is actually setting it to 9589 (75125-65536) and so you're never going to get into your while loop.

You can test that pretty easily by reading back CC[0] after you set it and see what it is.

By the way, If you're using the softdevice then this

NVIC_SetPriority(TIMER1_IRQn, 0);

is using an interrupt priority you can't use. Not something causing your problem, but something which will cause you a problem in the softdevice eventually.