commit be9b15da452fa5bf18b1441ddc3b9b001b339a46 Author: Simon Couball Date: Tue Aug 11 22:42:58 2020 +0200 Initial commit diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..16c015d --- /dev/null +++ b/.gitignore @@ -0,0 +1,7 @@ +.pio +.vscode/.browse.c_cpp.db* +.vscode/c_cpp_properties.json +.vscode/launch.json +.vscode/ipch +*.cpp-old +.vscode diff --git a/.travis.yml b/.travis.yml new file mode 100644 index 0000000..7c486f1 --- /dev/null +++ b/.travis.yml @@ -0,0 +1,67 @@ +# Continuous Integration (CI) is the practice, in software +# engineering, of merging all developer working copies with a shared mainline +# several times a day < https://docs.platformio.org/page/ci/index.html > +# +# Documentation: +# +# * Travis CI Embedded Builds with PlatformIO +# < https://docs.travis-ci.com/user/integration/platformio/ > +# +# * PlatformIO integration with Travis CI +# < https://docs.platformio.org/page/ci/travis.html > +# +# * User Guide for `platformio ci` command +# < https://docs.platformio.org/page/userguide/cmd_ci.html > +# +# +# Please choose one of the following templates (proposed below) and uncomment +# it (remove "# " before each line) or use own configuration according to the +# Travis CI documentation (see above). +# + + +# +# Template #1: General project. Test it using existing `platformio.ini`. +# + +# language: python +# python: +# - "2.7" +# +# sudo: false +# cache: +# directories: +# - "~/.platformio" +# +# install: +# - pip install -U platformio +# - platformio update +# +# script: +# - platformio run + + +# +# Template #2: The project is intended to be used as a library with examples. +# + +# language: python +# python: +# - "2.7" +# +# sudo: false +# cache: +# directories: +# - "~/.platformio" +# +# env: +# - PLATFORMIO_CI_SRC=path/to/test/file.c +# - PLATFORMIO_CI_SRC=examples/file.ino +# - PLATFORMIO_CI_SRC=path/to/test/directory +# +# install: +# - pip install -U platformio +# - platformio update +# +# script: +# - platformio ci --lib="." --board=ID_1 --board=ID_2 --board=ID_N diff --git a/include/README b/include/README new file mode 100644 index 0000000..194dcd4 --- /dev/null +++ b/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/lib/README b/lib/README new file mode 100644 index 0000000..6debab1 --- /dev/null +++ b/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/platformio.ini b/platformio.ini new file mode 100644 index 0000000..8b03f58 --- /dev/null +++ b/platformio.ini @@ -0,0 +1,16 @@ +; 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:nanoatmega328] +platform = atmelavr +board = nanoatmega328 +framework = arduino +upload_port = /dev/cu.wchusbserial* +monitor_speed = 9600 \ No newline at end of file diff --git a/src/main.cpp b/src/main.cpp new file mode 100644 index 0000000..2b60d34 --- /dev/null +++ b/src/main.cpp @@ -0,0 +1,85 @@ +#include + +/* + * Function: configureTimer + * ---------------------------- + * Configures both 16bit timer for 25 kHz pwm signals. + */ +void configureTimer() +{ + // Configure Timer 1 for PWM @ 25 kHz. + TCCR1A = 0; // undo the configuration done by... + TCCR1B = 0; // ...the Arduino core library... + TCCR1C = 0; // ...for pin 9, 10 and 11. + TCNT1 = 0; // reset timer + // non-inverted PWM on ch. A, B and C, mode 10: ph. correct PWM, TOP = ICR1 + // TCCR1A = _BV(COM1A1) | _BV(COM1B1) | _BV(COM1C1) | _BV(WGM11); + TCCR1B = _BV(WGM13) | _BV(CS10); // prescaler = 1 + TCCR1C = _BV(WGM13) | _BV(CS10); // on PIN 9,10,11 + ICR1 = 320; // TOP = 320, @16Mhz CPU -> 25kHz PWM + OCR1A = 5; // Set duty-cycle + // Configure Timer 3 + // TCCR3A = 0; + // TCNT3 = 0; + // TCCR3A = _BV(COM1A1) | _BV(WGM11); + // TCCR3B = _BV(WGM13) | _BV(CS10); + // ICR3 = 320; + + // pretty slow ~1000hz + // TCCR1A = 0; //clear timer registers + // TCCR1B = 0; + // TCNT1 = 0; + + // TCCR1B |= _BV(CS12) | _BV(CS11) | _BV(CS10); //no prescaler + // ICR1 = 320; //PWM mode counts up 320 then down 320 counts (25kHz) + + // TCCR1A |= _BV(COM1A1); //output A clear rising/set falling + + // TCCR1A |= _BV(COM1B1); //output B clear rising/set falling + + // TCCR1B |= _BV(WGM13); //PWM mode with ICR1 Mode 10 + // TCCR1A |= _BV(WGM11); //WGM13:WGM10 set 1010 +} + + +/* + * Function: setup + * ---------------------------- + * Default arduino setup function, calls all the initialization functions. + */ +void setup() +{ + Serial.begin(9600); // initialization of serial over usb. + delay(500); // wait a bit for external program to connect. + + + Serial.println("set output pins..."); + pinMode(2, OUTPUT); + pinMode(9, OUTPUT); + pinMode(7, INPUT); + + // configure timer + Serial.println("configure timer for 25kHz PWM..."); + configureTimer(); + + Serial.println("fan control setup done."); +} + +void loop() +{ + int last = digitalRead(7); + + while (1) { + int next = digitalRead(7); + + if (!last && next) { + digitalWrite(2, HIGH); + } else { + digitalWrite(2, LOW); + } + + last = next; + + delayMicroseconds(200); + } +} diff --git a/test/README b/test/README new file mode 100644 index 0000000..df5066e --- /dev/null +++ b/test/README @@ -0,0 +1,11 @@ + +This directory is intended for PIO 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 PIO Unit Testing: +- https://docs.platformio.org/page/plus/unit-testing.html