Forward 100ms time stamp to RTE and handle logbook in main loop Because of code execution variance between 100ms cycle event and start of SPI communication, the synchronization between Main and RTE may shift. To avoid these shifts the time stamp of the 100ms event is forwarded to the RTE which is now able to adapt to small variations. One variation point was the storage of dive samples within the external flash. Taking a closer look how this function works, moving it from the timer callback to the main loop should not be an issue. A critical point of having the function in the timer call back was the sector clean function which is called (depending on dive data) every ~300minutes and may take 250ms - 1500ms.

README.linux
------------

1. Compile the pack utilities

cd src
make checksum_final_add_fletcher
make OSTC4pack_V4

2. Edit create_full_update_bin.sh

Set BUILD_PATH to the location where you build the individual parts
of the firmware using the OpenSTM23 IDE. 

Set BUILD_TYPE the either Debug or Release (or any other build style you 
defined in the OpenSTM23 IDE).

Set the "build project names" as defined in the OpenSTM23 IDE.

3. Simpy run create_full_update_bin.sh

Run it in the ostc4pack folder of the repository, and a file with name
like OSTC4_<date>.bin is created containg the individual blobs.