Bugfix: make max depth move with current depth (part 1) The display in dive mode of the max depth was updated before the actual depth, which looks very strange. The reason for this was conceptually simple. The depth value was averaged over a set of depth samples, but the current depth was only taken from the current sample. So, per definition, on an initial descend, the current depth is always bigger (deeper) than any average from previous shallower samples. This part 1 commit introduces a new function that is used immediate after reception of the new sample from the RTE. This function does the trivial average of a set of samples. Notice that also the surface and ambient mbar pressures are taken into account (which are used heavily over the entire code). This is a consistency thing. We should base any further calculation from the data presented in the UI, instead of presenting A, and use A' for further calculations. Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>

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.