Mercurial > public > ostc4

view ostc4pack/README.linux @ 897:65772ddee88c Evo_2_23

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Use dive profile as source for simulator: If a dive is marked in the log view then its depth profil will be used as source for the simulator. In the first implementation only the depth data is used => Deco data will be calculated in scope of the simulator.
author ideenmodellierer
date Thu, 26 Sep 2024 18:36:05 +0200
parents 9c77cfe8c2b2
children
line wrap: on
line source

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.