first commit

.github/workflows/build.yml

@@ -0,0 +1,24 @@
+name: PlatformIO CI
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/cache@v3
+        with:
+          path: |
+            ~/.cache/pip
+            ~/.platformio/.cache
+          key: ${{ runner.os }}-pio
+      - uses: actions/setup-python@v4
+        with:
+          python-version: '3.9'
+      - name: Install PlatformIO Core
+        run: pip install --upgrade platformio
+
+      - name: Build PlatformIO Project
+        run: pio run

.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,9 @@
+{
+    "files.associations": {
+        "*.c": "c",
+        "cal_buffer.h": "c",
+        "string.h": "c",
+        "atca_host_config_check.h": "c",
+        "cryptoauthlib.h": "c"
+    }
+}

ATECC608a_ESP8266-main.code-workspace

@@ -0,0 +1,16 @@
+{
+	"folders": [
+		{
+			"path": "."
+		}
+	],
+	"settings": {
+		"files.associations": {
+			"*.c": "c",
+			"cal_buffer.h": "c",
+			"string.h": "c",
+			"atca_host_config_check.h": "c",
+			"cryptoauthlib.h": "c"
+		}
+	}
+}

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

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

lib/cryptoauthlib-3.7.0/.gitattributes

@@ -0,0 +1 @@
+*.pdf filter=lfs diff=lfs merge=lfs -text

lib/cryptoauthlib-3.7.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,28 @@
+---
+name: Bug report
+about: Create a report to help us improve this library
+
+---
+
+<!--- Caution: Product datasheets are provided under NDA (non-disclosure
+agreement) and it is up to you to abide by the terms of it. Only use this
+form to report issues with the library itself and not issues related to
+specific device behavior. Use Microchip's support portal to ask about or
+report any device related issues: https://microchipsupport.force.com/s/
+--->
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Additional context**
+Add any other context about the problem here.

lib/cryptoauthlib-3.7.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Microchip Support Portal
+    url: https://microchipsupport.force.com/s/
+    about: Submit technical support requests to Microchip's team of product experts
+  - name: Microchip PSIRT Security Reporting
+    url: https://www.microchip.com/design-centers/embedded-security/how-to-report-potential-product-security-vulnerabilities
+    about: How to report security vunerabilities through Microchip's PSIRT Process

lib/cryptoauthlib-3.7.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+<!--- Caution: Product datasheets are provided under NDA (non-disclosure
+agreement) and it is up to you to abide by the terms of it. Only use this
+form to report issues with the library itself and not issues related to
+specific device behavior. Use Microchip's support portal to ask about or
+report any device related issues: https://microchipsupport.force.com/s/
+--->
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

lib/cryptoauthlib-3.7.0/.github/ISSUE_TEMPLATE/product-support.md

@@ -0,0 +1,9 @@
+---
+name: Product Support
+about: Questions on product or library configuration and usage
+
+---
+
+For product support please submit a request through the [mySupport portal](https://microchipsupport.force.com/s/) where Microchip's global team of FAEs can work on your use case and questions.
+
+For details on the mySupport Portal or how to use it please see the [instructions for using the mySupport portal](https://microchipsupport.force.com/s/article/How-to-submit-a-case)

lib/cryptoauthlib-3.7.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,6 @@
+# Please describe the purpose of this pull request
+
+
+
+# Checklist
+* [ ] I have reviewed the [CONTRIBUTING.md](https://github.com/MicrochipTech/cryptoauthlib/blob/main/CONTRIBUTING.md) and agree to it's terms

lib/cryptoauthlib-3.7.0/.github/workflows/build.yml

@@ -0,0 +1,117 @@
+name: Build and deploy wheels to pypi
+
+on:
+  push:
+    branches:
+      - main
+    tags:
+      - 20*
+
+jobs:
+  build_wheels:
+    name: Build wheels on ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Describe Tag & Branch Name
+        if:  github.event_name == 'push' && startsWith(github.ref, 'refs/tags/20')
+        id: build_names
+        shell: bash
+        run: |
+          cd python
+          echo ${GITHUB_REF#refs/tags/} >VERSION
+
+      - name: Configure Environment
+        shell: bash
+        run: |
+          cd python
+          cp ../release_notes.md .
+          cp -r ../lib .
+          cp -r ../third_party .
+          mkdir app
+          cp -r ../app/tng app
+
+      - name: Build wheels
+        uses: pypa/[email protected]
+        with:
+          package-dir: python 
+        env:
+          CIBW_SKIP: "cp27-* cp36-* cp37-* pp37-* *-musllinux* pp*-macosx*"
+          CIBW_MANYLINUX_X86_64_IMAGE: "manylinux_2_28"
+          CIBW_BEFORE_BUILD_LINUX: "yum update -y && yum install -y libusb-devel"
+          CIBW_BUILD_VERBOSITY: 3
+          CIBW_ARCHS_LINUX: "x86_64"
+          CIBW_ARCHS_MACOS: "x86_64 arm64"
+          # Skip trying to test arm64 builds on Intel Macs
+          CIBW_TEST_SKIP: "*-macosx_arm64 *-macosx_universal2:arm64"
+          CMAKE_OSX_ARCHITECTURES: "arm64;x86_64"
+
+      - uses: actions/upload-artifact@v3
+        with:
+          path: wheelhouse/*.whl
+
+  build_sdist:
+    name: Build source distribution
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+
+      - uses: actions/setup-python@v2
+        name: Install Python
+        with:
+          python-version: '3.7'
+
+      - name: Describe Tag & Branch Name
+        id: build_names
+        run: |
+          echo ::set-output name=TAG_NAME::${GITHUB_REF#refs/tags/}
+
+      - name: Build sdist
+        run: |
+          echo $TAG_NAME
+          cd python
+          echo $TAG_NAME >VERSION
+          cp -r ../lib .
+          cp -r ../third_party .
+          mkdir app
+          cp -r ../app/tng app
+          python setup.py sdist
+        env:
+          TAG_NAME: ${{ steps.build_names.outputs.TAG_NAME }}
+
+      - uses: actions/upload-artifact@v2
+        with:
+          path: python/dist/*.tar.gz
+
+  upload_pypi:
+    if:  github.event_name == 'push' && startsWith(github.ref, 'refs/tags/20')
+    needs: [build_wheels, build_sdist]
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/download-artifact@v2
+        with:
+          name: artifact
+          path: dist
+
+      - name: Production Release
+        if: startsWith(github.repository, 'MicrochipTech')
+        uses: pypa/gh-action-pypi-publish@release/v1.5
+        with:
+          user: ${{ secrets.pypi_username }}
+          password: ${{ secrets.pypi_password }}
+          skip_existing: true
+
+      - name: Test Release
+        if: ${{ !startsWith(github.repository, 'MicrochipTech') }}
+        uses: pypa/gh-action-pypi-publish@release/v1.5
+        with:
+          user: ${{ secrets.pypi_username }}
+          password: ${{ secrets.pypi_password }}
+          repository_url: https://test.pypi.org/legacy/
+          skip_existing: true

lib/cryptoauthlib-3.7.0/.github/workflows/stale.yml

@@ -0,0 +1,29 @@
+# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
+#
+# You can adjust the behavior by modifying this file.
+# For more information, see:
+# https://github.com/actions/stale
+name: Mark stale issues and pull requests
+
+on:
+  schedule:
+  - cron: '35 20 * * *'
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+    - uses: actions/stale@v5
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-issue-message: 'This issue has been marked as stale - please confirm the issue still exists with the latest version of the library and update the issue if it remains'
+        stale-pr-message: 'This PR has been marked as stale and will be automatically closed in 7 days.'
+        remove-stale-when-updated: true
+        exempt-issue-labels: 'bug,enhancement,investigation,help wanted'
+        exempt-pr-labels: 'bug,enhancement,investigation,help wanted'
+