Mercurial > public > ostc4
view wiki/Using OpenSTM32.md @ 837:18946846b95b Evo_2_23
Bugfixes and code cleanup for BF views:
BF views gauge and apnoe were using "dive computer" T3 view functions which caused some problem because these legacy views were not intended to work with customer view selection. A switch condition has been added to skip these kind of functions in case a design other T3 is in use.
Another potential problem was that there were two definitions for T3 and T7 views which were basically the same. If they wold not be the same the switching functionality wold not work properly. To avoid this problem in futur the arrays have been merged => the view are handled sing the (newer) cv_view arrays instead of the standard_views which were in used before the user could the views which should be shown.
author | ideenmodellierer |
---|---|
date | Wed, 27 Dec 2023 19:37:17 +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)