Mercurial > public > ostc4
annotate Documentations/dump-rte.cfg @ 726:8f3a8c85a6c4
Bugfix data synchronization after RTE start:
In previous version invalid data may be transferred in case the communication is corrupted directly after RTE startup. Root cause was that the data was evaluated without caring if a communication error was reported. In the new version the startup condition and evaluation of data is only done if valid data has been received by the RTE => SPI communication is up and runnig.
author | Ideenmodellierer |
---|---|
date | Sat, 14 Jan 2023 20:35:40 +0100 |
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 |