view ostc4pack/create_full_update_bin.sh @ 301:a09b1855d656 cleanup-4

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>
author Jan Mulder <jlmulder@xs4all.nl>
date Mon, 20 May 2019 10:05:27 +0200
parents 9c77cfe8c2b2
children f4b553da620a
line wrap: on
line source

#!/bin/bash

#
# path and file name settings
#

# the build products are here
BUILD_PATH="$HOME/OSTC4workspace"

# Debug or Release build
BUILD_TYPE="Release"

# build project names
CPU1_DISCOVERY="CPU1-Discovery"
CPU1_FONTPACK="CPU1-FontPack"
CPU2_RTE="CPU2-RTE"

#
# End of path and file name settings
#

#
# Copy the bin files to pack. Build them seperately
#
cp $BUILD_PATH/$CPU1_DISCOVERY/$BUILD_TYPE/$CPU1_DISCOVERY.bin .
cp $BUILD_PATH/$CPU1_FONTPACK/$BUILD_TYPE/$CPU1_FONTPACK.bin .
cp $BUILD_PATH/$CPU2_RTE/$BUILD_TYPE/$CPU2_RTE.bin .

#
# OSTC4pack_V4 all
#
./src/OSTC4pack_V4 1 $CPU1_DISCOVERY.bin
./src/OSTC4pack_V4 2 $CPU1_FONTPACK.bin
./src/OSTC4pack_V4 0 $CPU2_RTE.bin

#
# Final pack
#
./src/checksum_final_add_fletcher ${CPU1_DISCOVERY}_upload.bin \
				${CPU1_FONTPACK}_upload.bin \
				${CPU2_RTE}_upload.bin