Mercurial > public > ostc4

view wiki/Detailed CPU1-Upper Project.md @ 557:2702bfa7b177

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 5f11787b4f42
children
line wrap: on
line source

# How to Create From Scratch a Project for _CPU1-Upper_ Code #

The main CPU (aka. _CPU1 Discovery_) firmware is splitted in two parts:
- The proper _CPU1 Discovery_ firmware, with the main code.
- The _protected upper memory_ firmware, which is programmed during _OSTC4_ production, and contains (amongst other things) code used to upload and install firmware upgrades.

## Make a specific project ##

Follow the same procedure than for [CPU1-Discovery](Detailed CPU1-Discovery Project.md), (same processor, same includes) but include the `CPU1-Upper` source directory.

**
NOT FINISHED YET... BE PATIENT
**