From 5aa9fdaf8eb5c9bebcb839715bcff6d5dad50f62 Mon Sep 17 00:00:00 2001 From: Greg Sandstrom Date: Wed, 20 Dec 2023 11:17:52 -0800 Subject: [PATCH] initial PIO project creating for nano every, add SD card and RTClib dependencies --- dirwin-nano-every/.gitignore | 5 ++++ dirwin-nano-every/.vscode/extensions.json | 10 +++++++ dirwin-nano-every/include/README | 39 ++++++++++++++++++++++++++ dirwin-nano-every/lib/README | 46 +++++++++++++++++++++++++++++++ dirwin-nano-every/platformio.ini | 17 ++++++++++++ dirwin-nano-every/src/main.cpp | 18 ++++++++++++ dirwin-nano-every/test/README | 11 ++++++++ 7 files changed, 146 insertions(+) create mode 100644 dirwin-nano-every/.gitignore create mode 100644 dirwin-nano-every/.vscode/extensions.json create mode 100644 dirwin-nano-every/include/README create mode 100644 dirwin-nano-every/lib/README create mode 100644 dirwin-nano-every/platformio.ini create mode 100644 dirwin-nano-every/src/main.cpp create mode 100644 dirwin-nano-every/test/README diff --git a/dirwin-nano-every/.gitignore b/dirwin-nano-every/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/dirwin-nano-every/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/dirwin-nano-every/.vscode/extensions.json b/dirwin-nano-every/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/dirwin-nano-every/.vscode/extensions.json @@ -0,0 +1,10 @@ +{ + // See http://go.microsoft.com/fwlink/?LinkId=827846 + // for the documentation about the extensions.json format + "recommendations": [ + "platformio.platformio-ide" + ], + "unwantedRecommendations": [ + "ms-vscode.cpptools-extension-pack" + ] +} diff --git a/dirwin-nano-every/include/README b/dirwin-nano-every/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/dirwin-nano-every/include/README @@ -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 diff --git a/dirwin-nano-every/lib/README b/dirwin-nano-every/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/dirwin-nano-every/lib/README @@ -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 +#include + +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 diff --git a/dirwin-nano-every/platformio.ini b/dirwin-nano-every/platformio.ini new file mode 100644 index 0000000..bbc302a --- /dev/null +++ b/dirwin-nano-every/platformio.ini @@ -0,0 +1,17 @@ +; 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:nano_every] +platform = atmelmegaavr +board = nano_every +framework = arduino +lib_deps = + arduino-libraries/SD@^1.2.4 + adafruit/RTClib@^2.1.3 diff --git a/dirwin-nano-every/src/main.cpp b/dirwin-nano-every/src/main.cpp new file mode 100644 index 0000000..cb9fbba --- /dev/null +++ b/dirwin-nano-every/src/main.cpp @@ -0,0 +1,18 @@ +#include + +// put function declarations here: +int myFunction(int, int); + +void setup() { + // put your setup code here, to run once: + int result = myFunction(2, 3); +} + +void loop() { + // put your main code here, to run repeatedly: +} + +// put function definitions here: +int myFunction(int x, int y) { + return x + y; +} \ No newline at end of file diff --git a/dirwin-nano-every/test/README b/dirwin-nano-every/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/dirwin-nano-every/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PlatformIO Test Runner 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/en/latest/advanced/unit-testing/index.html -- 1.9.1