Mercurial > public > ostc4
view ostc4pack/README.linux @ 232:f0069f002c55 div-fixes-4-1
Bugfix: make date/time setting work over reboots
Setting the time/date over the UART interface or by the menu, seems
to work, but a reboot of the RTE brings back strange, seemingly
random, time.
The reason for this is rather simple. In the settings, a time
is stored, based on some flawed logic, and that time was restored
on reboot. There is no reason to store any time, when the moment of
restoring it is unrelated in time. So, the fix is simple: do not
set time (in the RTC) based on some time from the past. The whole idea
of a RTC is that it does preserve the time for you, as long its
powered. Any attempt to do things better using stored time data is
futile (and nonsense).
And while working on his, also kick out some useless code from the RTE.
There is no reason to initialize the time on the RTC to some random
time/date in the past. A zero data/time is as good and any random
date.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
author | Jan Mulder <jlmulder@xs4all.nl> |
---|---|
date | Wed, 03 Apr 2019 21:11:56 +0200 |
parents | 9c77cfe8c2b2 |
children |
line wrap: on
line source
README.linux ------------ 1. Compile the pack utilities cd src make checksum_final_add_fletcher make OSTC4pack_V4 2. Edit create_full_update_bin.sh Set BUILD_PATH to the location where you build the individual parts of the firmware using the OpenSTM23 IDE. Set BUILD_TYPE the either Debug or Release (or any other build style you defined in the OpenSTM23 IDE). Set the "build project names" as defined in the OpenSTM23 IDE. 3. Simpy run create_full_update_bin.sh Run it in the ostc4pack folder of the repository, and a file with name like OSTC4_<date>.bin is created containg the individual blobs.