Mercurial > public > ostc4
view Documentations/dump-rte.cfg @ 270:2e58a4094770 write-from-sim
feature, debug: make simulator write a logbook entry
When compiling the code with -DSIM_WRITES_LOGBOOK, the simulator writes
to the logbook. This is for debug purpose only. This commit does *not*
define this SIM_WRITES_LOGBOOK, so when compiled, things are functionally
unchanged.
Caveat 1: a simulator generated log cannot be advanced with +5 min. It needs
to run in real time.
Caveat 2: The generated log is currently not "complete". For example, CCR
setpoint switches are not logged. There are likely more small events not
logged. This means that a sim generated log is not a full replacement for
real dive testing.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
author | Jan Mulder <jlmulder@xs4all.nl> |
---|---|
date | Wed, 24 Apr 2019 17:10:51 +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