Mercurial > public > ostc4
annotate Documentations/dump-rte.cfg @ 311:ddbe8bed5096 cleanup-4
bugfix: make stopwatch and divetime run in sync
And this shows the fundamental issue in the difference between dive time and
stopwatch time. The dive time is constructed on the RTE, and rather
independently, the stopwatch time is constructed on CPU1.
This works rather well, but not perfect. This commit fixes things in
a relatively straightforward way. Instead of incrementing the stopwatch
locally on CPU1, simply use the same time data that is coming from the
RTE. Some logic was added to make this stopwatch resettable again.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
| author | Jan Mulder <jlmulder@xs4all.nl> |
|---|---|
| date | Wed, 29 May 2019 14:02:27 +0200 |
| parents | 01cc5959f199 |
| children |
| rev | line source |
|---|---|
| 34 | 1 #! openocd -f |
| 2 # Define the prob used: | |
| 3 source [find interface/stlink-v2.cfg] | |
| 4 set WORKAREASIZE 0x8000 | |
| 5 transport select hla_swd | |
| 6 | |
| 7 # Reset options | |
| 8 set ENABLE_LOW_POWER 1 | |
| 9 set STOP_WATCHDOG 1 | |
| 10 reset_config srst_only srst_nogate connect_assert_srst | |
| 11 | |
| 12 # Seelct the right chip | |
| 13 set CHIPNAME stm32f411RETx | |
| 14 set CONNECT_UNDER_RESET 1 | |
| 15 source [find target/stm32f4x.cfg] | |
| 16 | |
| 17 # Allow to continue execution after a connection: | |
| 18 init_reset run | |
| 19 | |
| 20 #puts "Flash banks:" | |
| 21 #flash banks | |
| 22 | |
| 23 #puts "Reading..." | |
| 24 #flash dump_image CPU2-RTE-dump.hex 0x00000000 0x8000 | |
| 25 | |
| 26 #puts "Done." | |
| 27 #exit |