Mercurial > public > ostc4
annotate ostc4pack/README.linux @ 425:86fcac4cc43a ImprovmentNVM_2
Added function to analyse the sampel ringbuffer:
The function will show 0 for used sectors, 4 for the sector currently in use and 5 for empty sectors. This allows identification of log sample index position and identification of a buffer corruption (more than 2 sectors have state 4)
The repair function writes dummy bytes to the end of the active buffer with the lower sector number. This decision is based on the fact that corruption results typically in a reset of index to buffer start address. After repair the writing will be continued using the hugher buffer marked as used.
author | ideenmodellierer |
---|---|
date | Sat, 15 Feb 2020 20:50:20 +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 |