Mercurial > public > ostc4
annotate ostc4pack/README.linux @ 199:ac58a9fb92ac div-fixes-cleaup-2
Bugfix: fix initial CNS data in the logbook header
Apparently, there has been confusion in the past about the data format of the
CNS data in the logbook. This seems to be partially fixed back in 2015, but
this fix forgot that the initial CNS data is also in the logbook header.
So, now, the logbook header also stores the initial CNS data in a correct way,
which fixes the problem of strange CNS values at the very start of repetitive
dives, that get reset in the dive profile after the first CNS sample data comes
along.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
| author | Jan Mulder <jlmulder@xs4all.nl> |
|---|---|
| date | Fri, 22 Mar 2019 08:36:39 +0100 |
| 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 |