added Arduino Due test script

test/DueSerialTest/.gitignore

@@ -0,0 +1,5 @@
+.pio
+.vscode/.browse.c_cpp.db*
+.vscode/c_cpp_properties.json
+.vscode/launch.json
+.vscode/ipch

test/DueSerialTest/.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"
+    ]
+}

test/DueSerialTest/README.md

@@ -0,0 +1,2 @@
+This is a Platform IO test script for the Arduino Due which can be used to sent different kind
+of strings via the serial interface (RX1 and TX1) to the Vorago board.

test/DueSerialTest/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

test/DueSerialTest/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

test/DueSerialTest/platformio.ini

@@ -0,0 +1,15 @@
+; 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:due]
+platform = atmelsam
+board = due
+framework = arduino
+monitor_speed = 115200

test/DueSerialTest/src/main.cpp

@@ -0,0 +1,75 @@
+#include <Arduino.h>
+
+enum SendModes {
+  ECHO,
+  ONLY_WRITE,
+  ONLY_READ,
+  WRITE_READ
+};
+
+enum StringModes {
+  FIXED,
+  VARIABLE
+};
+
+// Configure the test application here
+SendModes SEND_MODE = SendModes::WRITE_READ;
+StringModes STRING_MODE = StringModes::VARIABLE;
+uint8_t STRING_IDX = 0;
+
+String STRINGS[4] = {
+  "$Hi\n",
+  "$Hello\n",
+  "$Hello World\n",
+  "$Hello and Merry Christmas to all of you!\n"
+};
+
+void setup() {
+  // put your setup code here, to run once:
+  Serial.begin(115200);
+  Serial.println("Starting Arduino Serial Test script..");
+  Serial1.begin(115200);
+  if(STRING_MODE == StringModes::VARIABLE) {
+    STRING_IDX = 0;
+  }
+  pinMode(LED_BUILTIN, OUTPUT);
+}
+
+void loop() {
+  static byte ICOMING_BYTE = 0;
+  static uint32_t GLOBAL_IDX = 0;
+  digitalWrite(LED_BUILTIN, !digitalRead(LED_BUILTIN));
+  // put your main code here, to run repeatedly:
+  // send data only when you receive data:
+  if (SEND_MODE == SendModes::ONLY_WRITE or SEND_MODE == SendModes::WRITE_READ) {
+    Serial.println("Sending string..");
+    if(STRING_MODE == StringModes::VARIABLE) {
+      STRING_IDX += 1;
+    }
+    Serial1.write(STRINGS[STRING_IDX].c_str());
+  }
+  if(
+    SEND_MODE == SendModes::WRITE_READ or
+    SEND_MODE == SendModes::ONLY_READ or
+    SEND_MODE == SendModes::ECHO
+  ) {
+    if (Serial1.available() > 0) {
+      // read the incoming byte:
+      String readString = Serial1.readStringUntil('\n');
+
+      Serial.print(GLOBAL_IDX);
+      Serial.print(" - ");
+      GLOBAL_IDX++;
+      // say what you got:
+      Serial.print("I received: ");
+      Serial.println(readString);
+      if(SEND_MODE == SendModes::ECHO) {
+        delay(200);
+        Serial.println("Sending back echo message");
+        String sendBack = readString + '\n';
+        Serial1.write(sendBack.c_str());
+      }
+    }
+  }
+  delay(3000);
+}

test/DueSerialTest/test/README

@@ -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