os_cputime_delay_ticks does not put the task to sleep; it was meant for short blocking delays. The nrf_delay_ms() function doesnt put the task to sleep either so I am not sure why you are seeing a difference between the two.
> On Jan 26, 2017, at 6:03 AM, then yon <[email protected]> wrote: > > Dear Jiacheng, > > Thanks for your reply. > > When i used os_cputime_delay_ticks() function it will cause my app hang and > it will never goes into idle stat. > > I found the solution by using the nrf_delay_ms from nordic sdk. > > Thank you. > > Regards, > > Then Yoong Ze > > > On 26/1/2017 7:41 PM, WangJiacheng wrote: >> Hi Then, >> >> The OS time tick resolution is defined by OS_TICKS_PER_SEC. >> >> If you want higher time resolution, use CPU time. The default CPU time tick >> is 1 microsecond, function os_cputime_delay_ticks() should be used. >> >> Moreover, you can change CPU timing frequency to change CLOCK_FREQ and >> OS_CPUTIME_FREQ in syscfg.yml. >> >> Jiacheng >> >> >> >>> 在 2017年1月26日，16:00，then yon <[email protected]> 写道： >>> >>> Dear Support, >>> >>> I'm working on a timing critical app; but the os_time_delay didn't gave me >>> a precise timing. >>> >>> Currently the min delay i can get is more than 2ms with os_time_delay >>> function. >>> >>> Somehow i notice that the clock time have up to microsecond precision; but >>> how do i make a delay with that? >>> >>> Thank you. >>> >>> Regards, >>> >>> Then Yoong Ze >> . >> >
