Mercurial > public > ostc4
annotate ostc4pack/README.linux @ 197:c853f5d23bb7 div-fixes-cleaup-2
cleanup: fix (harmless) use before assign
While looking around for possible wrong CNS values in the logbook header,
I see this "interesting" thing. Simply assign the current CNS data to the
global state, before using it to issue a warning. In practice, this does
not fix any real bug, as the code is run very often, so the global state
data is always (very) recent. It simply does not look right.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
author | Jan Mulder <jlmulder@xs4all.nl> |
---|---|
date | Thu, 21 Mar 2019 11:41:59 +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 |