diff --git a/Lab2_Final/src/main.cpp b/Lab2_Final/src/main.cpp index 9e141bb..332b4cd 100644 --- a/Lab2_Final/src/main.cpp +++ b/Lab2_Final/src/main.cpp @@ -1,7 +1,5 @@ #include - - // Variable to hold button State, this needs to be globally avaialable int buttonState; diff --git a/Lab3_Classes/.gitignore b/Lab3_Classes/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/Lab3_Classes/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/Lab3_Classes/.vscode/extensions.json b/Lab3_Classes/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/Lab3_Classes/.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/Lab3_Classes/include/README b/Lab3_Classes/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/Lab3_Classes/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/Lab3_Classes/lib/README b/Lab3_Classes/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/Lab3_Classes/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/Lab3_Classes/platformio.ini b/Lab3_Classes/platformio.ini new file mode 100644 index 0000000..207fd96 --- /dev/null +++ b/Lab3_Classes/platformio.ini @@ -0,0 +1,20 @@ +; 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:nucleo_f401re] +platform = ststm32 +board = nucleo_f401re +framework = mbed + +[env:nucleo_f746zg] +platform = ststm32 +board = nucleo_f746zg +framework = mbed + diff --git a/Lab3_Classes/src/main.cpp b/Lab3_Classes/src/main.cpp new file mode 100644 index 0000000..43bf1ee --- /dev/null +++ b/Lab3_Classes/src/main.cpp @@ -0,0 +1,71 @@ +#include + +class Flasher{ + // Variables + private: + DigitalOut theLed; + int state; + + + // Methods + + public: + + Flasher(PinName thePin, int startState) : theLed(thePin){ + state = startState; + } + + void flash(){ + if (state == 0){ + theLed = 1; + thread_sleep_for(1000); + theLed = 0; + thread_sleep_for(1000); + } + else { + theLed = 1; + thread_sleep_for(5000); + theLed = 0; + thread_sleep_for(5000); + } + } + +}; + + + +// Variable to hold button State, this needs to be globally avaialable +int buttonState; + +// Hander Function for our Buton Press +void handler(){ + printf("Update Button State\n"); + buttonState = !buttonState; + + } + +int main() { + + // put your setup code here, to run once: + + //Setup the User Buton as an Input + InterruptIn theButton(USER_BUTTON); + + //Bind the interupt to a function + theButton.rise(&handler); + + // Global Flasher Object + Flasher theFlasher(LED1, 0); + + + while(1) { + // put your main code here, to run repeatedly: + + //Print the State of our button + printf("Button State is %d\n", buttonState); + + theFlasher.flash(); + + + } +} diff --git a/Lab3_Classes/test/README b/Lab3_Classes/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/Lab3_Classes/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 diff --git a/Lab3_Functions/.gitignore b/Lab3_Functions/.gitignore new file mode 100644 index 0000000..89cc49c --- /dev/null +++ b/Lab3_Functions/.gitignore @@ -0,0 +1,5 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch diff --git a/Lab3_Functions/.vscode/extensions.json b/Lab3_Functions/.vscode/extensions.json new file mode 100644 index 0000000..080e70d --- /dev/null +++ b/Lab3_Functions/.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/Lab3_Functions/include/README b/Lab3_Functions/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/Lab3_Functions/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/Lab3_Functions/lib/README b/Lab3_Functions/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/Lab3_Functions/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/Lab3_Functions/platformio.ini b/Lab3_Functions/platformio.ini new file mode 100644 index 0000000..207fd96 --- /dev/null +++ b/Lab3_Functions/platformio.ini @@ -0,0 +1,20 @@ +; 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:nucleo_f401re] +platform = ststm32 +board = nucleo_f401re +framework = mbed + +[env:nucleo_f746zg] +platform = ststm32 +board = nucleo_f746zg +framework = mbed + diff --git a/Lab3_Functions/src/main.cpp b/Lab3_Functions/src/main.cpp new file mode 100644 index 0000000..23bf9b4 --- /dev/null +++ b/Lab3_Functions/src/main.cpp @@ -0,0 +1,52 @@ +#include + + + +// Variable to hold button State, this needs to be globally avaialable +int buttonState; + +// Hander Function for our Buton Press +void handler(){ + printf("Update Button State\n"); + buttonState = !buttonState; + } + +void flash(DigitalOut theLed, int sleep){ + theLed = 1; + thread_sleep_for(sleep); + theLed = 0; + thread_sleep_for(sleep); +} + +int main() { + + // put your setup code here, to run once: + + //Setup the User Buton as an Input + InterruptIn theButton(USER_BUTTON); + + //Bind the interupt to a function + theButton.rise(&handler); + + + + while(1) { + // put your main code here, to run repeatedly: + + //Setup the LED1 pin to be a digital output called ledOne + DigitalOut ledOne(LED1); + + + //Print the State of our button + printf("Button State is %d\n", buttonState); + + + //Is the Button Pressed + if (buttonState) { + flash(ledOne, 2000); + } + else{ + flash(ledOne, 500); + } + } +} diff --git a/Lab3_Functions/test/README b/Lab3_Functions/test/README new file mode 100644 index 0000000..9b1e87b --- /dev/null +++ b/Lab3_Functions/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