sc7-testo-firmware/include
true 6394c3aaff Implement flash config storage
Calibration needs to be saved for each badge in continuity mode. Added a flash-backed user config storing option with basic wear leveling. Have NOT yet tested the write and erase functions.
2023-11-01 07:45:44 -07:00
..
README Initial repository layout, add datasheets and device pack 2023-10-16 14:26:16 -07:00
adc.h Change some ADC parameters 2023-11-01 06:05:01 -07:00
flash.h Implement flash config storage 2023-11-01 07:45:44 -07:00
hsv2rgb.h Added initial RGBLED program, basic button handling 2023-10-22 00:40:01 -07:00
led.h WIP code 2023-10-19 16:20:41 -07:00
probe.h Fix diode check limits, allow for two-mode continuity limit 2023-10-31 19:50:30 -07:00
py32f0xx_conf.h WIP code 2023-10-16 14:29:23 -07:00
py32f0xx_it.h WIP code 2023-10-16 14:29:23 -07:00
rand.h Added more RGBLED programs, ADC fixups 2023-10-31 07:46:11 -07:00
rgbprog.h Implement flash config storage 2023-11-01 07:45:44 -07:00
testo.h Continuity and diode mode initial implementation 2023-10-21 19:45:15 -07:00
userio.h Fix diode check limits, allow for two-mode continuity limit 2023-10-31 19:50:30 -07:00

README

This directory is intended for project header files.

A header file is a file containing C declarations and macro definitions
to be shared between several project source files. You request the use of a
header file in your project source file (C, C++, etc) located in `src` folder
by including it, with the C preprocessing directive `#include'.

```src/main.c

#include "header.h"

int main (void)
{
 ...
}
```

Including a header file produces the same results as copying the header file
into each source file that needs it. Such copying would be time-consuming
and error-prone. With a header file, the related declarations appear
in only one place. If they need to be changed, they can be changed in one
place, and programs that include the header file will automatically use the
new version when next recompiled. The header file eliminates the labor of
finding and changing all the copies as well as the risk that a failure to
find one copy will result in inconsistencies within a program.

In C, the usual convention is to give header files names that end with `.h'.
It is most portable to use only letters, digits, dashes, and underscores in
header file names, and at most one dot.

Read more about using header files in official GCC documentation:

* Include Syntax
* Include Operation
* Once-Only Headers
* Computed Includes

https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html