Mercurial > public > ostc4
annotate ostc4pack/README.linux @ 240:625d20070261 div-fixes-5
Improvement SPI stability/recoverability
The core part of this commit comes from careful code reading. The core is the
swap of Scheduler_Request_sync_with_SPI(SPI_SYNC_METHOD_SOFT) and
SPI_Start_single_TxRx_with_Master(). This code is sitting in an if-clause
that is triggered on SPI comms failure. Instead of blindly trying to
communicate again (which will very likely fail again), first try to reset
the comms link, and then try to communicate again. That simply makes
more sense in this case.
This is heavily tested, on 2 simple dives, and 5 very long deco schedules
from the simulator (10+ hour deco's), and a lot of small simulated dives
(upto 2h runtime). Of all these tests, only one long session failed after
9 out of 11h runtime. Analyzing that one failure, suggests that the
RTE is looping in some error handler, which (obviously) results in
a SPI comms failure as a result. I consider this not part of this change.
Additionally, some more cleanup is done in this code.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
author | Jan Mulder <jlmulder@xs4all.nl> |
---|---|
date | Mon, 08 Apr 2019 11:49:13 +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 |