Mercurial > public > ostc4
annotate ostc4pack/README.linux @ 307:b6436edfb2c0 cleanup-4
cleanup: factor out unused stopwatch code
Visually, this looks a bit of a dangerous cleanup, but its not :-)
To explain this cleanup: stopwatch_seconds is never used, so assign
to it is useless, and the variable can be removed. Now,
stopwatch_start_at_this_dive_time_seconds is not used any more, so
remove it as well. Now, look at the boolResetStopwatch code. It
is used but only to reset itself. This makes the whole stopwatch
block in data_exchange_main.c a useless thing. All the other
cleanup is trivial.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
| author | Jan Mulder <jlmulder@xs4all.nl> |
|---|---|
| date | Wed, 22 May 2019 22:22:15 +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 |