This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Z-Stack Home 1.2.0 : leap into the future +5347 seconds

Other Parts Discussed in Thread: Z-STACK, CC2530

Hi,

We use Home-Automation profile based on SampleSwitch project & CC2530... We upgraded our application from Z-Stack 2.5.0 to Z-Stack Home 1.2.0. 

Each hour, we fix the time to our sensor,  using 'osal_setClock' in OSAL_Clock file to set it up.

Almost after 9 days of using our application on all our sensors,  we observed that suddlendly the clock had added +5347 seconds than what was expected... And we didn't set the wrong timestamp!

Looking at the code, we have some doubts about osalMcuDivide31By16To16() used in the macro CONVERT_320US_TO_MS_ELAPSED_REMAINDER...

We setted back the previous code from Z-Stack 2.5.0 and we didn't meet that kind of issue since 1 month.

Regards,

Leo