> I do note that they elected to use a 32-bit UNIX time register, and > they don't have an alternate part with a 64-bit - which means it would be > susceptible to the UNIX epoch bug in 2038 if the data was simply consumed > right out of the register. Shame that the part didn't come with just 4 more > byte registers, that puts the burden of patching on the software people - > meaning the CPU would have to be awake more to handle the correction for > 32-bit unsigned to 64-bit signed and keep track of rollovers, potentially > eroding some of the low power benefits.
Not a problem. It's 2 lines of code. It's the same problem as the GPS week number roll over (WNRO). If the reading is less than the build time of the software, add in the overflow bit. That's good for 136 years. I wonder if any gear using those chips will still be running 100 years from now. -- These are my opinions. I hate spam. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com and follow the instructions there.
