Initial commit 2

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

CMakeLists.txt

@@ -0,0 +1,3 @@
+cmake_minimum_required(VERSION 3.16.0)
+include($ENV{IDF_PATH}/tools/cmake/project.cmake)
+project(c1101-esp-idf)

include/README

@@ -0,0 +1,37 @@
+
+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 convention is to give header files names that end with `.h'.
+
+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

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 the executable file.
+
+The source code of each library should be placed in a separate directory
+("lib/your_library_name/[Code]").
+
+For example, see the structure of the following example libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional. for 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
+
+Example contents of `src/main.c` using Foo and Bar:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+The PlatformIO Library Dependency Finder will find automatically dependent
+libraries by scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

platformio.ini

@@ -0,0 +1,19 @@
+; 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:esp32doit-devkit-v1]
+platform = espressif32
+board = esp32dev
+framework = espidf, arduino
+monitor_speed = 115200
+build_type = debug
+build_flags = 
+	-D CONFIG_FREERTOS_HZ=1000
+lib_deps = mfurga/CC1101@^1.1.2

src/CMakeLists.txt

@@ -0,0 +1,6 @@
+# This file was automatically generated for projects
+# without default 'CMakeLists.txt' file.
+
+FILE(GLOB_RECURSE app_sources ${CMAKE_SOURCE_DIR}/src/*.*)
+
+idf_component_register(SRCS ${app_sources})

src/main.cpp

@@ -0,0 +1,64 @@
+#include <Arduino.h>
+#include "driver/gpio.h"
+#include "esp_timer.h"
+#include <cc1101.h>
+
+using namespace CC1101;
+
+
+Radio radio(12, 21, 25, 14, PIN_UNUSED, PIN_UNUSED);
+
+void loop_task(void *pvParameters) {
+
+
+    int counter = 0;
+    while (1) {
+        String data = "M7FFA Hello #" + String(counter++);
+
+        Serial.print("Transmitting: " + data + " ");
+        Status status = radio.transmit((uint8_t *)data.c_str(), data.length());
+
+        if (status == STATUS_OK) {
+            Serial.println("[OK]");
+        } else {
+            Serial.println("[ERROR]");
+        }
+
+        delay(1000);
+    }
+}
+
+
+
+extern "C" void app_main() {
+    initArduino();  // Necessary to start Arduino core in ESP-IDF
+    
+    Serial.begin(115200);
+    delay(1000);
+    Serial.println("Starting ...");
+    delay(3000);
+
+    if (radio.begin() == STATUS_CHIP_NOT_FOUND) {
+        Serial.println("Chip not found!");
+        for (;;);
+    }
+
+
+    radio.setModulation(MOD_2FSK);
+    radio.setFrequency(438.8);
+    radio.setDataRate(9.6);
+    radio.setOutputPower(10);
+    radio.setFrequencyDeviation(12.5);
+
+    radio.setPacketLengthMode(PKT_LEN_MODE_VARIABLE);
+    radio.setAddressFilteringMode(ADDR_FILTER_MODE_NONE);
+    radio.setPreambleLength(64);
+    radio.setSyncWord(0x1234);
+    radio.setSyncMode(SYNC_MODE_16_16);
+    radio.setCrc(true);
+
+
+
+
+    xTaskCreate(loop_task, "loop_task", 2048, NULL, 5, NULL);
+}

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