OS time tick initialization

Hello: Porting the OS to the nrf51 has exposed an issue for certain cortex-M MCU’s, namely the lack of SysTick. Furthermore, it may be advantageous from a power perspective to use a different timer for the OS time tick. Thus, the problem is this: how does the developer pick the timer to use

Re: Moving towards a beta release

Some thoughts (belatedly): * I dont think we need coredump in B1. * Do we need a different BLE MCU/transceiver for first release? Not sure if we should spend time on the stack as opposed to diverting it to porting to a different MCU/transceiver. * Do we need separate host/controller for first

Re: OS time tick initialization

Well, that would have been a better way to put it if you ask me. :-) A good example of picking a different timer would be time accuracy vs power related savings. For example, a device that is constantly powered may want to use a timer off a high accuracy crystal as opposed to one that is lower

Re: OS time tick initialization

I¹ll throw in my support as well. Certainly on some processors different timers have different current draw and require different sleep states. For wearables, this is super critical for battery life. I expect that folks will want to use alternate timers for the system tick to maximize battery

Re: OS time tick initialization

One more quick note. I think that there are probably a number of things in the MCU that are good defaults for most folks, but we may want to allow override in the BSP. I wish I had a good list, but I don’t :(. On 2/2/16, 2:43 PM, "p...@wrada.com" wrote: >I¹ll throw in my