Mercurial > public > ostc4
view RefPrj/Firmware/.project @ 424:2b31cf1ebbcc ImprovmentNVM_2
Added (optional) menu item to analyse log sample buffer:
The analysis function will check the ring buffer for proper closure of sectors. In case of a log sample ring corruption more than sector will show the state started (4). Depending on the time past since corruption and the location of the corrupted sector, a cleanup function will be executed if a dive is started. The dive is necessary because of the definition of sample position during OSTC startup phase.
author | ideenmodellierer |
---|---|
date | Sat, 15 Feb 2020 20:45:19 +0100 |
parents | d24395f7c939 |
children |
line wrap: on
line source
<?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>OSTC4_Firmware</name> <comment></comment> <projects> </projects> <buildSpec> <buildCommand> <name>org.eclipse.cdt.managedbuilder.core.genmakebuilder</name> <triggers>clean,full,incremental,</triggers> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.cdt.managedbuilder.core.ScannerConfigBuilder</name> <triggers>full,incremental,</triggers> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.cdt.core.cnature</nature> <nature>org.eclipse.cdt.managedbuilder.core.managedBuildNature</nature> <nature>org.eclipse.cdt.managedbuilder.core.ScannerConfigNature</nature> <nature>fr.ac6.mcu.ide.core.MCUProjectNature</nature> <nature>fr.ac6.mcu.ide.core.MCUSingleCoreProjectNature</nature> </natures> <linkedResources> <link> <name>Common</name> <type>2</type> <locationURI>OSTC4/Common</locationURI> </link> <link> <name>Discovery</name> <type>2</type> <locationURI>OSTC4/Discovery</locationURI> </link> </linkedResources> <variableList> <variable> <name>OSTC4</name> <value>$%7BWORKSPACE_LOC%7D/ostc4</value> </variable> </variableList> </projectDescription>