https://devzone.nordicsemi.com/f/nordic-q-a/10292/change-to-use-timer1-of-timer-example-it-failed[test result] change to use Timer1 of timer example,it failed. if you use timer0, it is OK.. SDK IS 9.0: nRF51_SDK_9.0.0_2e23562\examples\peripheral\timer [test step] 1, test timer0, it is ok. 2. i want to test of timer1, so i change the demoen-USTelligent Community 13Tue, 17 Nov 2015 10:20:00 GMThttps://devzone.nordicsemi.com/thread/38203?ContentTypeID=1Tue, 17 Nov 2015 10:20:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c93ff098-7499-4d31-ad7f-be9ee0fdb112hawk<p>thanks a lot.. in the file of nrf_drv_config.h, it has detail configuration of timers..</p> <p>Timer0 has 32bits width, Timer1 and Timer2 have 16 bits width.. So when you use timer,</p> <p>nrf_drv_timer_init(&amp;TIMER_LED, NULL, timer_led_event_handler), maybe it is not good for us,</p> <p>it will use default configuration by using NULL, it use 16MHz , prescaler = 0, as default; 1 tick＝ 0.0625 us, the time of 1 tick is so small, As result , total ticks of time you set are so large, maybe the length of</p> <p>this number is longer than 16bits . So my problem appeared.. thank JohnBrown .</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/38202?ContentTypeID=1Tue, 17 Nov 2015 10:07:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:659c0894-ab84-412b-9e6e-7ffd4593d055JohnBrown<p>You are aware that timer0 is the only one that has the 24 bit and 32 bit modes? The others are limited to 8 and 16 bit modes. This caught me out once.</p><div style="clear:both;"></div>