Mercurial > public > ostc4
annotate ostc4pack/README.linux @ 557:2702bfa7b177
Stabilityfix: Do not trust lastDiveLogID == 0 at startup:
If dive settings are reset for some reason also the lastDiveLogID is set to 0. Most likly the consostency check will find a valid entry. But this entry might not be the last one => return an error value to trigger the find function. Calling "find" at every startup is normal behavior if TRUST_LOG_CONSISTENCY is not set and was default for a long time => low risk
In addition a check of the header adresses has been added to identify a potential error while writing log samples
author | Ideenmodellierer |
---|---|
date | Thu, 12 Nov 2020 20:03:00 +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 |