cleanup, RTE: factor out scheduleCheck_pressure_reached_dive_mode_level The detection of the start of dive mode is conceptually simple (when the pressure sensor reaches a certain threshold, we are diving). This said, there are multiple implementations over the entire code base to answer the question: are we diving? This commit factors out scheduleCheck_pressure_reached_dive_mode_level used only in the RTE, in favor of is_ambient_pressure_close_to_surface, which is used in both RTE and CPU1 firmware. I had a little hope that is would fix the 1 second difference between the initial stopwatch and the divetime, but it does not. 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.