Initial working platform io config

This commit is contained in:
Eric Helgeson 2021-01-18 10:05:08 -06:00
parent 5cbeecc7ba
commit 59e40a05c4
6 changed files with 146 additions and 0 deletions

7
.vscode/extensions.json vendored Normal file
View File

@ -0,0 +1,7 @@
{
// See http://go.microsoft.com/fwlink/?LinkId=827846
// for the documentation about the extensions.json format
"recommendations": [
"platformio.platformio-ide"
]
}

39
include/README Normal file
View File

@ -0,0 +1,39 @@
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

46
lib/README Normal file
View File

@ -0,0 +1,46 @@
This directory is intended for project specific (private) libraries.
PlatformIO will compile them to static libraries and link into executable file.
The source code of each library should be placed in a an own separate directory
("lib/your_library_name/[here are source files]").
For example, see a structure of the following two libraries `Foo` and `Bar`:
|--lib
| |
| |--Bar
| | |--docs
| | |--examples
| | |--src
| | |- Bar.c
| | |- Bar.h
| | |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
| |
| |--Foo
| | |- Foo.c
| | |- Foo.h
| |
| |- README --> THIS FILE
|
|- platformio.ini
|--src
|- main.c
and a contents of `src/main.c`:
```
#include <Foo.h>
#include <Bar.h>
int main (void)
{
...
}
```
PlatformIO Library Dependency Finder will find automatically dependent
libraries scanning project source files.
More information about PlatformIO Library Dependency Finder
- https://docs.platformio.org/page/librarymanager/ldf.html

40
platformio.ini Normal file
View File

@ -0,0 +1,40 @@
; PlatformIO Project Configuration File
;
; Build options: build flags, source filter
; Upload options: custom upload port, speed and extra flags
; Library options: dependencies, extra library storages
; Advanced options: extra scripting
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:genericSTM32F103C8]
platform = ststm32
board = genericSTM32F103C8
; board = bluepill_f103c8
board_build.mcu = stm32f103c8t6
board_build.core = maple
framework = arduino
lib_ignore = USBComposite/, FreeRTOS701, FreeRTOS821, FreeRTOS900, Ethernet_STM, libmaple
lib_deps =
greiman/SdFat @ ^2.0.4
upload_protocol = stlink
platform_packages = toolchain-gccarmnoneeabi@1.40804.0
build_unflags =
build_flags =
-D PIO_FRAMEWORK_ARDUINO_STANDARD_LIB
-w
-O3
-std=gnu11 -std=gnu++11 -nostdlib -mthumb -march=armv7-m -D__STM32F1__ -DARDUINO_ARCH_STM32 -MMD
-ffunction-sections -fdata-sections
-funroll-loops
-D DEBUG_LEVEL=DEBUG_NONE
; Possible work around for clones, untested.
; https://community.platformio.org/t/cannot-upload-to-stm32-bluepill-board-over-stlink-v2/3492/25
; upload_flags = -c set CPUTAPID 0x2ba01477
; [env:debug]
; build_type = debug
; debug_tool = stlink

View File

@ -252,6 +252,8 @@ FsFile LOG_FILE;
void onFalseInit(void);
void onBusReset(void);
void initFileLog(void);
void finalizeFileLog(void);
/*
* IO read.
@ -319,6 +321,7 @@ void setup()
{
// PA15 / PB3 / PB4 Cannot be used
// JTAG Because it is used for debugging.
// Comment out for Debugging in PlatformIO
disableDebugPorts();
// Serial initialization

11
test/README Normal file
View File

@ -0,0 +1,11 @@
This directory is intended for PlatformIO Unit Testing and project tests.
Unit Testing is a software testing method by which individual units of
source code, sets of one or more MCU program modules together with associated
control data, usage procedures, and operating procedures, are tested to
determine whether they are fit for use. Unit testing finds problems early
in the development cycle.
More information about PlatformIO Unit Testing:
- https://docs.platformio.org/page/plus/unit-testing.html