first commit (WIP)

.gitignore

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

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

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "cmake.configureOnOpen": false
+}

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

include/main.h

@@ -0,0 +1,68 @@
+// Pin definitions
+#define PIN_QCA700X_INT 9             // SPI connections to QCA7000X
+#define PIN_QCA700X_CS 34
+#define SPI_MOSI 35
+#define SPI_MISO 37
+#define SPI_SCK 36
+
+/*====================================================================*
+ *   SPI registers QCA700X
+ *--------------------------------------------------------------------*/
+
+#define QCA7K_SPI_READ (1 << 15)                // MSB(15) of each command (16 bits) is the read(1) or write(0) bit.
+#define QCA7K_SPI_WRITE (0 << 15)
+#define QCA7K_SPI_INTERNAL (1 << 14)            // MSB(14) sets the Internal Registers(1) or Data Buffer(0)
+#define QCA7K_SPI_EXTERNAL (0 << 14)
+
+#define	SPI_REG_BFR_SIZE        0x0100
+#define SPI_REG_WRBUF_SPC_AVA   0x0200
+#define SPI_REG_RDBUF_BYTE_AVA  0x0300
+#define SPI_REG_SPI_CONFIG      0x0400
+#define SPI_REG_INTR_CAUSE      0x0C00
+#define SPI_REG_INTR_ENABLE     0x0D00
+#define SPI_REG_RDBUF_WATERMARK 0x1200
+#define SPI_REG_WRBUF_WATERMARK 0x1300
+#define SPI_REG_SIGNATURE       0x1A00
+#define SPI_REG_ACTION_CTRL     0x1B00
+
+#define QCASPI_GOOD_SIGNATURE   0xAA55
+
+#define MODEM_POWERUP 0
+#define MODEM_WRITESPACE 1
+#define MODEM_CM_SET_KEY_REQ 2
+#define MODEM_CM_SET_KEY_CNF 3
+#define MODEM_CONFIGURED 10
+
+
+#define CM_SET_KEY 0x6008
+#define CM_GET_KEY 0x600C
+#define CM_SC_JOIN 0x6010
+#define CM_CHAN_EST 0x6014
+#define CM_TM_UPDATE 0x6018
+#define CM_AMP_MAP 0x601C
+#define CM_BRG_INFO 0x6020
+#define CM_CONN_NEW 0x6024
+#define CM_CONN_REL 0x6028
+#define CM_CONN_MOD 0x602C
+#define CM_CONN_INFO 0x6030
+#define CM_STA_CAP 0x6034
+#define CM_NW_INFO 0x6038
+#define CM_GET_BEACON 0x603C
+#define CM_HFID 0x6040
+#define CM_MME_ERROR 0x6044
+#define CM_NW_STATS 0x6048
+#define CM_SLAC_PARAM 0x6064
+#define CM_START_ATTEN_CHAR 0x6068
+#define CM_ATTEN_CHAR 0x606C
+#define CM_PKCS_CERT 0x6070
+#define CM_MNBC_SOUND 0x6074
+#define CM_VALIDATE 0x6078
+#define CM_SLAC_MATCH 0x607C
+#define CM_SLAC_USER_DATA 0x6080
+#define CM_ATTEN_PROFILE 0x6084
+#define CM_GET_SW 0xA000
+
+#define MMTYPE_REQ 0x0000   // request
+#define MMTYPE_CNF 0x0001   // confirmation = +1
+#define MMTYPE_IND 0x0002
+#define MMTYPE_RSP 0x0003

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

platformio.ini

@@ -0,0 +1,24 @@
+; 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
+
+[platformio]
+description = ESP32-PLC
+
+[env:um_tinys3]
+platform = espressif32
+board = um_tinys3
+framework = arduino
+upload_port = COM5
+monitor_port = COM5
+
+build_flags =
+		-DARDUINO_USB_MODE=1
+		-DARDUINO_USB_CDC_ON_BOOT=1				  
+		-DCORE_DEBUG_LEVEL=5