Mercurial > public > ostc4
view Documentations/dump-rte.cfg @ 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 | 01cc5959f199 |
children |
line wrap: on
line source
#! openocd -f # Define the prob used: source [find interface/stlink-v2.cfg] set WORKAREASIZE 0x8000 transport select hla_swd # Reset options set ENABLE_LOW_POWER 1 set STOP_WATCHDOG 1 reset_config srst_only srst_nogate connect_assert_srst # Seelct the right chip set CHIPNAME stm32f411RETx set CONNECT_UNDER_RESET 1 source [find target/stm32f4x.cfg] # Allow to continue execution after a connection: init_reset run #puts "Flash banks:" #flash banks #puts "Reading..." #flash dump_image CPU2-RTE-dump.hex 0x00000000 0x8000 #puts "Done." #exit