Mercurial > public > ostc4
view wiki/Using OpenSTM32.md @ 557:2702bfa7b177
Stabilityfix: Do not trust lastDiveLogID == 0 at startup:
If dive settings are reset for some reason also the lastDiveLogID is set to 0. Most likly the consostency check will find a valid entry. But this entry might not be the last one => return an error value to trigger the find function. Calling "find" at every startup is normal behavior if TRUST_LOG_CONSISTENCY is not set and was default for a long time => low risk
In addition a check of the header adresses has been added to identify a potential error while writing log samples
author | Ideenmodellierer |
---|---|
date | Thu, 12 Nov 2020 20:03:00 +0100 |
parents | 0e7c16dd774d |
children |
line wrap: on
line source
# Using OpenSTM32 IDE to Compile OSTC4 Firmware # The free and Open [STM32 IDE](http://www.openstm32.org/System%2BWorkbench%2Bfor%2BSTM32) is an integrated development environment based on _Eclipse_ that will allows you to compile and link code for the OSTC4 dive computer. You will then be able to generate `.bin` firmware files to upload to your computer using your favourite tools, eg. [OSTC Companion](https://ostc-planner.net/companion). 1. Register on http://www.openstm32.org/ : that will allows you to download the IDE. 2. Once registered and logged in, you can go to _Documentation_ and _Installation Manual_. Follow the instructions to install the IDE (available for Windows 7, MacOS and Linux). 3. Use the ready made project ... in ... Or you can create a brand new project by following the _How To_'s: - [HowTo compile CPU1-Discovery main firmware](Detailed CPU1-Discovery Project.md) - [HowTo compile CPU1-Discovery protected area firmware](Detailed CPU1-Upper Project.md) - [HowTo compile CPU2-RTE real-time firmware](Detailed CPU2-RTE Project.md) - [HowTo generate uploadable firmware file](Make Firmware File.md)