Posted on November 10, 2017 at 09:28Ok, thanks for this discussion.
Ok so i think that RTC is used as the library and the given example use STOP and STANBY mode a lot.
So i will make a method to can update the RTC properly. This method will :
- update the alarm A (use by the delay wakeup over RTC library feature)
- so update the delay alarm reference time
I am really surprise that i don't find a such solution already implemented somewhere....
With this, the delay registered should not be modified. The library TImeServer.c managing the delay queue/list should not be disturb. The only remaining problem is the method
TimerGetElapsedTime that could have a really bigger reply than the waited one.
for this remaining problem, I think that st should refactor these two methods in their library/example :
TimerGetCurrentTime/TimerGetElapsedTime. I think that TimerGetCurrentTime should give a reference to keep internal reference on the given time to can update it, if rtc is updated. In this way if this reference is later used in the TimerGetCurrentTime method, the correct elapsed time will be computed.
I found also a bug in the st example project. As the systick is not used,
HAL_InitTick is redefined locally to do nothing. BUT HAL_GetTick is not redefined anywhere in the code given by st.In such way, actually, all project given with the lrwan library are bugged. All HAL synchronous method that are using a timeout can not return on this timeout on strange isssue : the HAL_GetTick method return always 0. THis is the cas of the SPI_WaitOnFlagUntilTimeout method that are used by the lrwan library. THis is the case of of the HAL method used in rtc also..... It will be the case on I2C or UART method if you add theses feature to given project.
