Mercurial > public > ostc4
annotate Documentations/dump-rte.cfg @ 814:26ae9e8f24fd
Dev Bugfix: O2 values of new detected sensors were shown as invalid:
In the previous version sometime O2 values were shown as invalid (red) after a autodetection cycle was run. After sleep/wakeup cycle the status were shown correct. Rootcause was that the out of bounds detection is based on the divesettings while the HW menu were only updating the common settings regarding active / inactive sensors. The problem has been solved by adding an divesettings update within the HW / sensor menu.
author | Ideenmodellierer |
---|---|
date | Sun, 03 Sep 2023 17:58:12 +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 |