bring source code into PlatformIO

code/.gitignore

@@ -0,0 +1,6 @@
+.pio
+.pioenvs
+.piolibdeps
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json

code/.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

code/.vscode/extensions.json

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

code/.vscode/settings.json

@@ -0,0 +1,6 @@
+{
+    "terminal.integrated.env.windows": {
+        "PATH": "C:\\Users\\salfter\\.platformio\\penv\\Scripts;C:\\Users\\salfter\\.platformio\\penv;C:\\Program Files (x86)\\Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\Windows\\System32;C:\\Windows;C:\\Windows\\System32\\wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\Windows\\System32\\OpenSSH\\;C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE\\Core-Static;C:\\Program Files\\dotnet\\;C:\\Program Files\\Microsoft SQL Server\\130\\Tools\\Binn\\;C:\\Program Files (x86)\\Microsoft SQL Server\\Client SDK\\ODBC\\130\\Tools\\Binn\\;C:\\Program Files (x86)\\Microsoft SQL Server\\140\\Tools\\Binn\\;C:\\Program Files (x86)\\Microsoft SQL Server\\140\\DTS\\Binn\\;C:\\Program Files (x86)\\Microsoft SQL Server\\140\\Tools\\Binn\\ManagementStudio\\;C:\\Program Files\\Microsoft VS Code\\bin;C:\\Program Files\\Git\\cmd;C:\\Program Files (x86)\\GnuPG\\bin;C:\\Program Files\\Calibre2\\;C:\\Program Files\\PuTTY\\;C:\\Users\\salfter\\AppData\\Local\\Microsoft\\WindowsApps;C:\\Program Files\\GPAC;C:\\Program Files\\GPAC;C:\\Program Files\\GPAC;C:\\Program Files (x86)\\Nmap;c:\\localbin;;C:\\Program Files (x86)\\Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\Windows\\System32;C:\\Windows;C:\\Windows\\System32\\wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\Windows\\System32\\OpenSSH\\;C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE\\Core-Static;C:\\Program Files\\dotnet\\;C:\\Program Files\\Microsoft SQL Server\\130\\Tools\\Binn\\;C:\\Program Files (x86)\\Microsoft SQL Server\\Client SDK\\ODBC\\130\\Tools\\Binn\\;C:\\Program Files (x86)\\Microsoft SQL Server\\140\\Tools\\Binn\\;C:\\Program Files (x86)\\Microsoft SQL Server\\140\\DTS\\Binn\\;C:\\Program Files (x86)\\Microsoft SQL Server\\140\\Tools\\Binn\\ManagementStudio\\;C:\\Program Files\\Microsoft VS Code\\bin;C:\\Program Files\\Git\\cmd;C:\\Program Files (x86)\\GnuPG\\bin;C:\\Program Files\\Calibre2\\;C:\\Program Files\\PuTTY\\;C:\\Users\\salfter\\AppData\\Local\\Microsoft\\WindowsApps;C:\\Program Files\\GPAC;C:\\Program Files\\GPAC;C:\\Program Files\\GPAC;C:\\Program Files (x86)\\Nmap;c:\\localbin;",
+        "PLATFORMIO_CALLER": "vscode"
+    }
+}

code/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

code/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 <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

code/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:uno]
+platform = atmelavr
+board_build.mcu = atmega328p
+board_build.f_cpu = 16000000L
+
+upload_protocol = arduino
+upload_speed = 115200

code/src/main.cpp

@@ -0,0 +1,127 @@
+#include <avr/io.h>
+#include <util/delay.h>
+
+#define	HFUSE	0xDF	// Default for ATmega48/88/168, for others see
+#define	LFUSE	0x62	// http://www.engbedded.com/fusecalc/
+
+/*
+#define  DATA    PORTD // PORTD = Arduino Digital pins 0-7
+#define  DATAD   DDRD  // Data direction register for DATA port
+#define  VCC     8		PB0
+#define  RDY     12     PB4 // RDY/!BSY signal from target
+#define  OE      11		PB3
+#define  WR      10		PB2
+#define  BS1     9		PB1
+#define  XA0     13		PB5
+#define  XA1     18    	PC4	// Analog inputs 0-5 can be addressed as
+#define  PAGEL   19    	PC5	// digital outputs 14-19
+#define  RST     14    	PC0	// Output to level shifter for !RESET
+#define  BS2     16		PC2
+#define  XTAL1   17		PC3
+
+#define  BUTTON  15    	PC1	// Run button
+#define  LED     0
+*/
+
+// PORTB
+#define	_VCC	(1<<0)
+#define	_RDY	(1<<4)
+#define	_OE		(1<<3)
+#define	_WR		(1<<2)
+#define	_BS1	(1<<1)
+#define	_XA0	(1<<5)
+
+// PORTC
+#define	_XA1	(1<<4)
+#define	_PAGEL	(1<<5)
+#define	_RST	(1<<0)
+#define	_BS2	(1<<2)
+#define	_XTAL1	(1<<3)
+
+#define	_BUTTON	(1<<1)
+
+void HardwareInit()
+{
+	DDRB	= ~(_RDY);			// all outputs except RDY (PB4)
+	PORTB	= 0x00;				// no pull-up
+
+	DDRC	= ~(_BUTTON);		// all outputs except BUTTON (PC1)
+	PORTC	= (_BUTTON)|(_RST);	// pull-up and 12V off (PC0 = 1)
+
+	DDRD	= 0xff;				// all outputs
+	PORTD	= 0x00;
+}
+
+void sendcmd(unsigned char command)
+{
+	PORTC |= _XA1;
+	PORTB &= ~(_XA0|_BS1);
+	
+	PORTD = command;
+
+	PORTC |= _XTAL1;
+	_delay_ms(1);
+	PORTC &= ~(_XTAL1);
+	_delay_ms(1);
+}
+
+void writefuse(unsigned char fuse, char highbyte)
+{
+	PORTC &= ~(_XA1);
+	PORTB |= _XA0;
+	_delay_ms(1);
+
+	PORTD = fuse;
+	PORTC |= _XTAL1;
+	_delay_ms(1);
+	PORTC &= ~(_XTAL1);
+
+	if (highbyte)
+		PORTB |= _BS1;
+	else
+		PORTB &= ~(_BS1);
+
+	PORTB &= ~(_WR);
+	_delay_ms(1);
+	PORTB |= _WR;
+	_delay_ms(100);
+}
+
+int main()
+{
+	HardwareInit();
+
+	for (;;)
+	{
+		while (PINC & _BUTTON) {}	// wait for button
+
+		// Initialize pins to enter programming mode
+		PORTC &= ~(_PAGEL|_XA1|_BS2);
+		PORTB &= ~(_XA0|_BS1);
+	
+		// Enter programming mode
+		PORTB |= _VCC|_WR|_OE;
+		_delay_ms(1);
+		PORTC &= ~(_RST);
+		_delay_ms(1);
+
+		// Program HFUSE
+		sendcmd(0b01000000);
+		writefuse(HFUSE, 1);
+
+		// Program LFUSE
+		sendcmd(0b01000000);
+  		writefuse(LFUSE, 0);
+
+		_delay_ms(1000);			// allow button to be released
+
+		// Exit programming mode
+		PORTC |= _RST;
+
+		// Turn off outputs
+		PORTD = 0x00;
+		PORTB &= ~(_VCC|_WR|_OE|_XA0|_BS1);
+		PORTC &= ~(_PAGEL|_XA1|_BS2);
+	}
+}
+

code/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