Mercurial > public > ostc4
view ostc4pack/README.linux @ 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 | 9c77cfe8c2b2 |
children |
line wrap: on
line source
README.linux ------------ 1. Compile the pack utilities cd src make checksum_final_add_fletcher make OSTC4pack_V4 2. Edit create_full_update_bin.sh Set BUILD_PATH to the location where you build the individual parts of the firmware using the OpenSTM23 IDE. Set BUILD_TYPE the either Debug or Release (or any other build style you defined in the OpenSTM23 IDE). Set the "build project names" as defined in the OpenSTM23 IDE. 3. Simpy run create_full_update_bin.sh Run it in the ostc4pack folder of the repository, and a file with name like OSTC4_<date>.bin is created containg the individual blobs.