dc22-wp-badge-firmware/fw_dc22_stm32l100/include
true 03376cc654 Initial port of STM32L100 code
This code was originally written for use with the CooCox IDE back in 2014. It uses ST StdPeriphLib (SPL) as opposed to HAL.

I have ported this using the built-in board definition for a board that supports the SPL. After making some small changes (mostly to include paths, but also un-inlining a couple function calls) and removing dead code, it appears to compile cleanly.

Actual binary is untested.
2023-02-11 06:32:15 -08:00
..
README Initial port of STM32L100 code 2023-02-11 06:32:15 -08:00
pirate.h Initial port of STM32L100 code 2023-02-11 06:32:15 -08:00
stm32l1xx_conf.h Initial port of STM32L100 code 2023-02-11 06:32:15 -08:00
stm32l1xx_it.h Initial port of STM32L100 code 2023-02-11 06:32:15 -08:00
usb_conf.h Initial port of STM32L100 code 2023-02-11 06:32:15 -08: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