Re: Timestamp for logs

2016-04-08 Thread will sanfilippo
It does seem like all those bits are unnecessary. Either 48 or 64 bits seems plenty. One note: if we want to use the same logging infrastructure for the controller in the ble stack we will need sub-millisecond precision. 1 microsecond units would be preferable; 16 bits for time since last

Re: Timestamp for logs

2016-04-08 Thread Christopher Collins
On Thu, Apr 07, 2016 at 10:33:26PM -0700, Vipul Rahane wrote: > Hello, > > I agree with your statement. We do not know on what kind of devices > Mynewt would be ported to. Sleepy devices which are meant to work for > 20 years running on a single coin cell battery will rollover the time > stamp in

Timestamp for logs

2016-04-07 Thread Vipul Rahane
Hello, Currently the timestamp for logs is a 64 bit value which comes from a 32 bit os_time counter. This counter counts ticks as opposed to seconds since boot or UTC timestamp. These are 1 ms ticks and so will rollover in 49 days. We have an API os_get_timeofday() which fills up a structure