Mercurial > public > ostc4
annotate ostc4pack/README.linux @ 301:a09b1855d656 cleanup-4
cleanup, RTE: factor out scheduleCheck_pressure_reached_dive_mode_level
The detection of the start of dive mode is conceptually simple (when the
pressure sensor reaches a certain threshold, we are diving). This said,
there are multiple implementations over the entire code base to answer
the question: are we diving?
This commit factors out scheduleCheck_pressure_reached_dive_mode_level used
only in the RTE, in favor of is_ambient_pressure_close_to_surface, which
is used in both RTE and CPU1 firmware.
I had a little hope that is would fix the 1 second difference between
the initial stopwatch and the divetime, but it does not.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
| author | Jan Mulder <jlmulder@xs4all.nl> |
|---|---|
| date | Mon, 20 May 2019 10:05:27 +0200 |
| parents | 9c77cfe8c2b2 |
| children |
| rev | line source |
|---|---|
| 163 | 1 README.linux |
| 2 ------------ | |
| 3 | |
| 4 1. Compile the pack utilities | |
| 5 | |
| 6 cd src | |
| 7 make checksum_final_add_fletcher | |
| 8 make OSTC4pack_V4 | |
| 9 | |
| 10 2. Edit create_full_update_bin.sh | |
| 11 | |
| 12 Set BUILD_PATH to the location where you build the individual parts | |
| 13 of the firmware using the OpenSTM23 IDE. | |
| 14 | |
| 15 Set BUILD_TYPE the either Debug or Release (or any other build style you | |
| 16 defined in the OpenSTM23 IDE). | |
| 17 | |
| 18 Set the "build project names" as defined in the OpenSTM23 IDE. | |
| 19 | |
| 20 3. Simpy run create_full_update_bin.sh | |
| 21 | |
| 22 Run it in the ostc4pack folder of the repository, and a file with name | |
| 23 like OSTC4_<date>.bin is created containg the individual blobs. | |
| 24 |