Merge branch 'main' into clang-format

Fix for mf static nested key recovery

.clang-format

@@ -0,0 +1,5 @@
+BreakBeforeBinaryOperators: All
+ColumnLimit: 120
+BasedOnStyle: Google
+BreakBeforeBraces: Stroustrup
+IndentWidth: 4

.github/workflows/build_client.yml

@@ -19,36 +19,56 @@ jobs:
             pre_command: |
               ? .
             bundle_command: |
-              Compress-Archive -Path software\* -DestinationPath client-windows.zip
+              Compress-Archive -Path software\dist\* -DestinationPath client-windows.zip
           - name: linux
             os: ubuntu-latest
             pre_command: |
               true
             bundle_command: |
-              (cd software && zip -r "$OLDPWD/client-linux.zip" .)
+              (cd software/dist && zip -r "$OLDPWD/client-linux.zip" .)
           - name: macos
             os: macos-latest
             pre_command: |
               true
             bundle_command: |
-              (cd software && zip -r "$OLDPWD/client-macos.zip" .)
+              (cd software/dist && zip -r "$OLDPWD/client-macos.zip" .)
     runs-on: ${{ matrix.os }}
     steps:
       - name: Check out the repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           ref: ${{ inputs.checkout-sha == null && github.sha || inputs.checkout-sha }}
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - name: Install PyInstaller and client dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pyinstaller
+          pip install -r software/script/requirements.txt
       - name: Run OS specific setup
         run: ${{ matrix.pre_command }}
+      - name: Compile native code
+        run: |
+          cd software/src
+          mkdir out
+          cd out
+          cmake ..
+          cmake --build . --config Release
+      - name: Run PyInstaller
+        run: |
+          cd software
+          pyinstaller pyinstaller.spec
       - name: Upload built client
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: client-${{ matrix.name }}
-          path: software/*
+          path: software/dist/*
       - name: Zip up client for release
         run: ${{ matrix.bundle_command }}
       - name: Upload release artifacts
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
-          name: release-artifacts
+          name: release-artifacts-${{ matrix.name }}
           path: client-${{ matrix.name }}.zip

.github/workflows/build_firmware.yml

@@ -20,7 +20,7 @@ jobs:
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v2
       - name: Check out the repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           ref: ${{ inputs.checkout-sha == null && github.sha || inputs.checkout-sha }}
           fetch-depth: 0
@@ -54,7 +54,7 @@ jobs:
         device_type: [ultra, lite]
     steps:
       - name: Check out the repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           ref: ${{ inputs.checkout-sha == null && github.sha || inputs.checkout-sha }}
           fetch-depth: 0
@@ -64,7 +64,7 @@ jobs:
         run: |
           docker run --rm -v ${PWD}:/workdir -e CURRENT_DEVICE_TYPE=${{ matrix.device_type }} ghcr.io/${repo,,}-fw-builder@${{ needs.build_fw_builder.outputs.image_hash }} firmware/build.sh
       - name: Upload built binaries
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: ${{ matrix.device_type }}-firmware
           path: firmware/objects/*.hex
@@ -76,17 +76,17 @@ jobs:
           unzip firmware/objects/${{ matrix.device_type }}-dfu-app.zip -d firmware/objects/${{ matrix.device_type }}-dfu-app
           unzip firmware/objects/${{ matrix.device_type }}-dfu-full.zip -d firmware/objects/${{ matrix.device_type }}-dfu-full
       - name: Upload dfu app image
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: ${{ matrix.device_type }}-dfu-app
           path: firmware/objects/${{ matrix.device_type }}-dfu-app/*
       - name: Upload dfu full image
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: ${{ matrix.device_type }}-dfu-full
           path: firmware/objects/${{ matrix.device_type }}-dfu-full/*
       - name: Upload release artifacts
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
-          name: release-artifacts
+          name: release-artifacts-${{ matrix.device_type }}
           path: firmware/objects/*.zip

.github/workflows/c-checks.yml

@@ -0,0 +1,35 @@
+name: clang-format Check
+on:
+  pull_request_target:
+    paths:
+      - '**.c'
+      - '**.h'
+      - '**.cpp'
+  workflow_dispatch:
+
+jobs:
+  check-format:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+
+    - name: Install clang-format
+      run: sudo apt install -y clang-format
+
+    - name: Get files and check format
+      run: |
+        exit_code=0
+        while IFS= read -r -d '' f; do
+          if ! diff -u "$f" <(clang-format "$f"); then
+            echo "Formatting issue in $f"
+            exit_code=1
+          fi
+        done < <(find . -type f \( -name '*.c' -o -name '*.h' \) ! -path './firmware/nrf52_sdk/*' ! -path './firmware/nrf52_sdk/**' -print0)
+
+        if [ $exit_code -ne 0 ]; then
+          echo "Clang-format check failed."
+          exit 1
+        else
+          echo "All files are properly formatted."
+        fi

.github/workflows/deploy_wiki_to_pages.yml

@@ -0,0 +1,49 @@
+name: Deploy wiki to GitHub Pages with Jekyll
+
+on:
+  push:
+    branches: ["main"]
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          repository: ${{ github.repository }}.wiki
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+      - name: Build with Jekyll
+        uses: actions/jekyll-build-pages@v1
+        with:
+          source: ./
+          destination: ./_site
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/on_pr.yml

@@ -10,12 +10,12 @@ jobs:
       contents: read
     uses: ./.github/workflows/build_firmware.yml
     with:
-      checkout-sha: "${{ github.event.pull_request.merge_commit_sha }}"
+      checkout-sha: "${{ github.event.pull_request.head.sha }}"
   client_pipeline:
     name: Build Firmware
     uses: ./.github/workflows/build_client.yml
     with:
-      checkout-sha: "${{ github.event.pull_request.merge_commit_sha }}"
+      checkout-sha: "${{ github.event.pull_request.head.sha }}"
   comment:
     runs-on: ubuntu-latest
     name: Comment on PR

.github/workflows/on_push.yml

@@ -24,11 +24,12 @@ jobs:
       - client_pipeline
     steps:
       - name: Check out the repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Download release artifacts
-        uses: actions/download-artifact@v3
+        uses: actions/download-artifact@v4
         with:
-          name: release-artifacts
+          pattern: release-artifacts-*
+          merge-multiple: true
           path: release-artifacts
       - name: Upload to dev release
         uses: softprops/action-gh-release@v1
@@ -60,11 +61,12 @@ jobs:
       - client_pipeline
     steps:
       - name: Check out the repo
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: Download release artifacts
-        uses: actions/download-artifact@v3
+        uses: actions/download-artifact@v4
         with:
-          name: release-artifacts
+          pattern: release-artifacts-*
+          merge-multiple: true
           path: release-artifacts
       - name: Upload to tagged release
         uses: softprops/action-gh-release@v1

.github/workflows/python-checks.yml

@@ -0,0 +1,57 @@
+name: Lint (pyrefly + ruff)
+
+on:
+  pull_request_target:
+    paths:
+      - "software/**"
+      - ".github/workflows/**"
+      - "**.py"
+  workflow_dispatch:
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        shell: bash
+        working-directory: software
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+          cache: "pip"
+          cache-dependency-path: |
+            software/pyproject.toml
+            software/uv.lock
+            software/script/requirements.txt
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v6
+
+      - name: Install dependencies with uv (if lockfile present)
+        if: ${{ hashFiles('software/uv.lock') != '' }}
+        run: uv sync --dev
+
+      - name: Install tools with pip (fallback)
+        if: ${{ hashFiles('software/uv.lock') == '' }}
+        run: |
+          python -m pip install --upgrade pip
+          # Try project requirements if present
+          if [ -f script/requirements.txt ]; then pip install -r script/requirements.txt || true; fi
+          # Ensure ruff and pyrefly are available
+          pip install ruff pyrefly
+
+      - name: Ruff check
+        run: |
+          set -e
+          (uv run ruff --version && uv run ruff check .) || ruff check .
+
+      - name: Pyrefly check
+        run: |
+          set -e
+          (uv run pyrefly --help >/dev/null 2>&1 && uv run pyrefly check) || pyrefly check

CHANGELOG.md

@@ -3,8 +3,51 @@ All notable changes to this project will be documented in this file.
 This project uses the changelog in accordance with [keepchangelog](http://keepachangelog.com/). Please use this to write notable changes, which is not the same as git commit log...
 
 ## [unreleased][unreleased]
+ - Added clang formatter (@GameTec-live)
+ - Fix for static nested key recovery (@jekkos)
+
+## [v2.1.0][2025-09-02]
+ - Added UV, formatter and linter. Contribution guidelines. (@GameTec-live)
+ - Extend max packet data size from 512 to 4096 bytes (@Foxushka)
+ - HID Prox support (@TeCHiScy)
+ - `hf mf elog --decrypt` skip records with found keys (@taichunmin)
+ - Added cmd for fetching all slots nicks (@Foxushka)
+ - Added `hf mf senested` for recovering keys from static encrypted cards via backdoor (https://eprint.iacr.org/2024/1275) (@Foxushka)
+ - Added cmd for faster bulk key checking on one block (~33 keys per second) (@Foxushka, @taichunmin)
+ - Added cmd to acquire nonces for static encrypted cards via backdoor (@Foxushka) 
+ - Added `firmware/docker-compose.yml` to build firmware in local docker (@taichunmin)
+ - Added cmd to acquire nonces for hardnested(Protocol doc need update) (@xianglin1998)
+ - Added command to check keys of multiple sectors at once (@taichunmin)
+ - Fixed unused target key type parameter for nested (@petepriority)
+ - Skip already used items `hf mf elog --decrypt` (@p-l-)
+ - Parallelize mfkey32v2 processes called from CLI (@p-l-)
+ - Added support for mifare classic value block operations (@taichunmin)
+ - Added regression tests (@doegox)
+ - Changed git version to version tag instead of dev tag (@taichunmin)
+ - Fixed 14A emulate bug and MF1 emulate bug (@spp2000 and @xianglin1998)
+ - Fixed `hf 14a raw` command raising `AttributeError` (@augustozanellato)
+ - Fixed ATS handling in tags that NAK RATS (@augustozanellato)
+ - Changed battery level curves based on experimental measures (@spp2000)
+ - Added multithreading on Nested and StaticNested (@xianglin1998)
+ - Fixed factory reset hanging (@augustozanellato)
+ - Changed fds_write_sync to take length in bytes instead of next multiple of 4 (@doegox)
+ - Fixed field LED when LF reading and HF cloning (@doegox)
+ - Added renaming of slot into "cloned" when having cloned an ID/UID with a button (@doegox)
+ - Fixed spurious LED in battery level, assigned battery level to long press B (@doegox)
+ - Changed `hw slot list` to display LF ID & HF anticol data, and names in the --short version too (@doegox)
+ - Added colors to CLI help (@doegox)
+ - Changed massively CLI, cf https://github.com/RfidResearchGroup/ChameleonUltra/issues/164#issue-1930580576 (@doegox)
+ - Changed CLI help: lists display and now all commands support `-h` (@doegox)
+ - Added button action to show battery level (@doegox)
+ - Added GUI Page docs (@GameTec-live)
+ - Changed CLI threads polling into blocking reads, to reduce CPU usage (@doegox)
+ - Added support for timestamped comments in CLI via `rem`, `;`, `%` or `#` (@doegox)
+ - Fixed watchdog trigger during `hw factory_reset` (@doegox)
+ - Added PyInstaller support for CLI client (@augustozanellato)
+ - Added proper Mifare Ultralight (original, C, EV1) / NTAG (213, 215, 216) emulation (@turbocooler).
 
 ## [v2.0.0][2023-09-26]
+ - Added `hw slot nick delete` and DELETE_SLOT_TAG_NICK (@doegox)
  - Changed APP_FW_VER now deduced from git tag vx.y.z (@doegox)
  - Changed initial button wakeup from 4 to 8 seconds (@aramova)
  - Added MIFARE Ultralight reading features (@FlUxIuS & @doegox)

CONTRIBUTING.md

@@ -0,0 +1,21 @@
+# Chameleon Ultra Contribution guidelines
+
+Any and all contributions are welcome!
+
+Heres a bit of info and a few guidelines to get you started:
+
+- General
+    - Avoid force pushes. Force pushes and "one commit" PRs not only make reviewing more annoying but also erase a significant part of the git history. This, among other things, makes future debugging and bisection a lot harder.
+    - Conventional commits. It is recommended to follow the [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/) pattern when it comes to commit messages. While this is not strictly enforced, its highly recommended and a good habbit.
+    - Atomic PRs. To help keep an overview and avoid conflicts, it is highly encouraged to file Atomic PRs. Atomic PRs are:
+        - Focused Scope: It targets a single, well-defined change, making it easier to understand and review.
+        - Minimal Size: It contains only the necessary code modifications to achieve its goal, avoiding unrelated changes.
+        - Independent: It should be able to stand on its own without depending on other unmerged PRs, reviewed, and merged independently.
+        - Self-Tested: each PR should include an appropriate set of unit tests that tests the changes. (optional but highly appreciated)
+    - Atomic Commits. Similar thing as atomic PRs. When you are done with a feature, commit. Made a working change? commit. Git commits are basically free. Doing frequent commits at sensible points throughout development not only helps you keep track of progress but also saves progress and changes so you can revert when something goes wrong. It also helps when debugging and bisecting as more granular commits allow for easier issue location.
+
+- CLI
+    - The recommended packagemanager is [UV](https://docs.astral.sh/uv/) (from astralsh). You may use the manager of your choice, but when adding new dependencies they must be added to the UV lock file and pyproject toml as well.
+    - Type safety is important. The CLI should be typesafe. Python 3.9+ offer a wide variety of type declarations. Metas [pyrefly](https://pyrefly.org/) is used to do type validation. It is recommended to install the appropriate vscode extension and check your types before opening a PR.
+    - Formatting matters. Mostly. While pixelpeeping and exact rules are annoying and unnescesary, format your code in a readable and logical way. [Ruff](https://docs.astral.sh/ruff/) is used to enforce various formatting rules. You may install the Ruff vscode extension or use the CLI to format before opening a PR.
+    - Avoid extra packages. Almost everyone knows the "meme" of the javascript ["is-even"](https://www.npmjs.com/package/is-even) package. While it is encouraged and makes sense to use packages where appropriate, just installing packages for the hell of it even if its a 2 liner is not sensible.

README.md

@@ -4,19 +4,28 @@
 
 # ChameleonUltra Authorized Distributors
 
-Europe: [Lab401](https://lab401.com/)
+Lyon, France: [Lab401](https://lab401.com/)
 
-United States: [Hackerwarehouse](https://hackerwarehouse.com/)
+Santa Ana, United States: [Hackerwarehouse](https://hackerwarehouse.com/)
 
-Anywhere else: [Sneaktechnology](https://sneaktechnology.com) / [Aliexpress by RRG](https://proxgrind.aliexpress.com/store/1101312023)
+Hastings, UK: [KSEC](https://labs.ksec.co.uk/product/proxgrind-chameleon-ultra/)
+
+Montreal, Canada: [TechSecurityTools](https://techsecuritytools.com/product/chameleon-ultra/)
+
+Shenzhen, China: [Sneaktechnology](https://sneaktechnology.com)
+
+Guangdong, China: [MTools Tec](https://shop.mtoolstec.com/)
+
+Lazada One, Singapore: [Aliexpress by RRG](https://proxgrind.aliexpress.com/store/1101312023)
 
 # What is it and how to use ?
 
-Read the [available documentation](docs/README.md).
+Read the [available documentation](https://github.com/RfidResearchGroup/ChameleonUltra/wiki).
 
 # Compatible applications
 
 * [ChameleonUltraGUI](https://github.com/GameTec-live/ChameleonUltraGUI)
+* [MTools BLE](https://github.com/RfidResearchGroup/ChameleonUltra/wiki/mtoolsble)
 
 # Videos
 
@@ -24,12 +33,16 @@ Read the [available documentation](docs/README.md).
 
 * [Downloading and compiling the official CLI](https://www.youtube.com/watch?v=VGpAeitNXH0)
 * [Downloading ChameleonUltraGUI](https://www.youtube.com/watch?v=rHH7iqbX3nY)
-* [ChameleonGUI features overview](https://www.youtube.com/watch?v=YqE8wyVSse4)
+* [ChameleonUltraGUI features overview](https://www.youtube.com/watch?v=YqE8wyVSse4)
+* [Using ChameleonUltraGUI and the Chameleon Ultra](https://www.youtube.com/watch?v=9jtKNJ5-kVY)
+* [MTools BLE - How to clone a card with ChameleonUltra](https://youtu.be/IvH-xtdW1Wk?si=4exqgAAeJ-kxU3aN)
 
 # Official channels
 
 Where do you find the community?
-
 * [RFID Hacking community discord server](https://t.ly/d4_C)
   * Software/chameleon-dev for firmware and clients development discussions
   * Devices/chameleon-ultra for usage discussions
+* [GameTec_live discord server](https://discord.gg/DJ2A4wxncK)
+
+###### Searching for the docs repo? Find it [here](https://github.com/RfidResearchGroup/ChameleonUltraDocs)

docs/README.md

@@ -1,37 +1,3 @@
 # Chameleon Ultra Guide
 
-This guide goal is to guide you through setting up and using your Chameleon Ultra and Lite.
-
-This Guide is split up into multiple "subguides":
-
-### About the device
-
-- [Whitepaper](./technical_whitepaper.md): Discover what the Chameleon Ultra is capable of.
-
-- [Hardware](./hardware.md): Learn to know the hardware of your Chameleon.
-
-- [Firmware](./firmware.md): Your Chameleon runs a firmware, learn what it can do and how to use it.
-
-### Interacting with the device
-
-- [Quickstart](./quickstart.md): For the impatient people to just get you up and running with anything.
-
-- [CLI](./cli.md): The official way to control your Chameleon is via the **C**ommand **L**ine **I**nterface (CLI). Learn how to install and master the CLI.
-
-- [GUIs](./gui.md): Some people also develop **G**raphical **U**ser **I**nterfaces (GUIs), these may be a good start for people that do not want to deal with a CLI.
-
-- [Troubleshooting](./troubleshooting.md): For when things go wrong, here are some common tips to maybe fix whatever issue you might have.
-
-### For developers
-
-- [Development](./development.md): For all developers. This covers how to build firmware from source and set up a development environment.
-
-- [SDKs](./sdk.md): SDKs for Chameleon, useful if you want to develop your own application to control Chameleon.
-
-- [Protocol](./protocol.md): The gory details of the communication protocol, useful if you want to develop your own client.
-
-### Miscellaneous 
-
-- [Modding](./modding.md): Third party moddings worth mentioning.
-
-- [FAQ](./faq.md): **F**requently **A**sked **Q**uestions, if you have a question, it might already be answered here.
+The docs have moved! [Wiki](https://github.com/RfidResearchGroup/ChameleonUltra/wiki)

docs/chameleonultragui.md

@@ -1,15 +0,0 @@
-## Get ChameleonUltraGUI
-
-- [on Google Play](https://play.google.com/store/apps/details?id=io.chameleon.ultra) / [APK](https://nightly.link/GameTec-live/ChameleonUltraGUI/workflows/buildapp/main/apk.zip)
-- [on iOS](https://apps.apple.com/dk/app/chameleon-ultra-gui/id6462919364)
-- [on Windows](https://nightly.link/GameTec-live/ChameleonUltraGUI/workflows/buildapp/main/windows-installer.zip) ([or without installer](https://nightly.link/GameTec-live/ChameleonUltraGUI/workflows/buildapp/main/windows.zip))
-- [on Linux](https://nightly.link/GameTec-live/ChameleonUltraGUI/workflows/buildapp/main/linux.zip)
-- [on macOS](https://apps.apple.com/app/chameleon-ultra-gui/id6462919364)
-
-
-## How to use MFKEY32
-
-- set slot to mifare classic (by uploading an empty dump)
-- enable mfkey32 for that slot (toggle in slot settings)
-- select slot and present ultra repeatedly to the reader in order to collect nonces
-- after collecting some nonces, go back into slot settings and click recover keys

docs/cli.md

@@ -1,160 +0,0 @@
-# CLI
-
-The CLI (**C**ommand **L**ine **I**nterface) is the official way to control your Chameleon.
-
-It requires at least **Python 3.9** version.
-
-## Installing
-
-There are multiple ways to install the CLI, depending on your OS.
-
-### Windows
-
-Windows users have the choice of 4 options:
-
-#### ProxSpace
-
-Using ProxSpace to build the CLI is the easiest and most comfortable way to get started.
-
-1. Download ProxSpace from the [official GitHub](https://github.com/Gator96100/ProxSpace/releases/latest)
-
-2. [Download 7zip](https://www.7-zip.org/) to extract the archive
-
-3. Install 7zip by double clicking the Installer and clicking `Install`
-
-4. Right-click on the downloaded archive and select `7zip -> Unpack to "ProxSpace"`
-
-5. Open a terminal in the proxspace folder. If you are on a new Windows install, you should be able to just right-click and select `Open in Terminal`. If that option is not visible and the ProxSpace folder is still in your downloads folder, press `win+r` and type `powershell` followed by enter. In Powershell now type `cd ~/Downloads/ProxSpace`
-
-6. Run the command `.\runme64.bat`. After successful completion, you should be dropped to the `pm3 ~ $` shell.
-
-7. Clone the Repository by typing `git clone https://github.com/RfidResearchGroup/ChameleonUltra.git`
-
-8. Now go into the newly created folder with `cd ChameleonUltra/software/src`
-
-9. Prepare for package installation with `pacman-key --init; pacman-key --populate; pacman -S msys2-keyring --noconfirm; pacman-key --refresh`
-
-10. Proceed by installing Ninja with `pacman -S ninja --noconfirm`
-
-11. Build the required config by running `cmake .`
-
-12. And the binaries with `cmake --build .`
-
-13. Copy the binaries by running `cp -r ~/ChameleonUltra/software/bin/* ~/ChameleonUltra/software/script/`
-
-14. Go into the script folder with `cd ~/ChameleonUltra/software/script/`
-
-15. Install python requirements with `pip install -r requirements.txt`
-
-16. Finally run the CLI with `python chameleon_cli_main.py`
-
-To use after installing, just do the following:
-
-1. Run `runme64.bat`
-
-2. Go into the script folder with `cd ~/ChameleonUltra/software/script/`
-
-3. Run the CLI with `python chameleon_cli_main.py`
-
-#### WSL2
-
-Coming Soon
-
-#### WSL1
-
-Coming Soon
-
-#### Build Natively
-
-Building natively is a bit more advanced and not recommended for beginners
-
-1. Download and install [Visual Studio Community](https://visualstudio.microsoft.com/de/downloads/)
-
-2. On the workload selection screen, choose the `Desktop development with C++` workload. Click `Download and Install`
-
-3. Download and install [git](https://git-scm.com/download). When asked, add to your path
-
-4. Download and install [cmake](https://cmake.org/download/). Again, when asked, add to your path
-
-5. Download and install [python](https://www.python.org/downloads/). When asked, add to your path (small checkbox in the bottom left)
-
-6. Choose a suitable location and open a terminal. Clone the repository with `git clone https://github.com/RfidResearchGroup/ChameleonUltra.git`
-
-7. Change into the binaries folder with `cd ChameleonUltra/software/src`
-
-8. Build the required config by running `cmake .`
-
-9. And the binaries with `cmake --build .`
-
-10. Copy the binaries by running `cp -r ../bin/Debug/* ../script/`
-
-11. Go into the script folder with `cd ../script/`
-
-12. Create a python virtual environment with `python -m venv venv`
-
-13. Activate it by running `.\venv\Scripts\Activate.ps1`
-
-14. Install python requirements with `pip install -r requirements.txt`
-
-15. Finally run the CLI with `python chameleon_cli_main.py`
-
-To run again after installing, just do the following:
-
-1. Activate venv by running `.\venv\Scripts\Activate.ps1`
-
-2. Run the CLI with `python chameleon_cli_main.py`
-
-### Linux
-
-*Coming Soon*
-
-### MacOS
-
-*Coming Soon*
-
-## Usage
-
-When in the CLI, plug in your Chameleon and connect with `hw connect`. If autodetection fails, get the Serial Port used by your Chameleon and run `hw connect -p COM11` (Replace `COM11` with your serial port, on Linux it may be `/dev/ttyACM0`)
-
-### Common activities
-
-- Connect to the CLI: `hw connect`
-- Change slot: `hw slot change -s [1-8]`
-
-*More examples coming soon*
-
-### MFKEY32v2 walk-through
-Make sure to be in the `software/` directory and run the Python CLI from there.
-
-- Connect to the CLI: `hw connect`
-- Check which slot can be used: `hw slot list`
-- Change the slot type, here using slot 8 for a MFC 1k emulation: `hw slot type -s8 -t3`
-- Init the slot content: `hw slot init -s8 -t3`
-  - or load an existing dump and set UID and anticollision data, cf `hf mf eload -h` and `hf mf sim -h`
-- Enable the slot: `hw slot enable -s8 -e1`
-- Change to the new slot: `hw slot change -s8`
-- Activate the detection: `hf detection enable -e1`
-
-Now disconnect, go to a reader and swipe it a few times
-
-- Come back and connect to the CLI: `hw connect`
-- See if nonces were collected: `hf detection count`
-  - We need 2 nonces per key to recover
-- Recover the key(s) based on the collected nonces: `hf detection decrypt`. Output example:
-```
- - MF1 detection log count = 6, start download.
- - Download done (144bytes), start parse and decrypt
- - Detection log for uid [DEADBEEF]
-  > Block 0 detect log decrypting...
-  > Block 1 detect log decrypting...
-  > Result ---------------------------
-  > Block 0, A key result: ['a0a1a2a3a4a5', 'aabbccddeeff']
-  > Block 1, A key result: ['010203040506']
-
-```
-
-- To clean the logged detection nonces: `hf detection enable -e0` then `hf detection enable -e1`
-
-
-
-*More examples coming soon*

docs/development.md

@@ -1,351 +0,0 @@
-# Development
-
-In this file you can look up how to [install requirements](#Prerequisites-for-compiling), [edit](#Editing-the-code), [compile](#Compiling-the-code) and [debug](#Debugging-the-code) the firmware!
-
-## Prerequisites for compiling
-
-### install a cross-compiler
-
-So far, the following compilers have been reported to work fine.  
-Download one of them and decompress it.  
-Remember the path where you installed it.
-
-- [gcc-arm-none-eabi-10.3-2021.10](https://developer.arm.com/downloads/-/gnu-rm)
-- [arm-gnu-toolchain-12.2.rel1-XXX-arm-none-eabi](https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads), e.g. [arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi.tar.xz](https://developer.arm.com/-/media/Files/downloads/gnu/12.2.rel1/binrel/arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi.tar.xz) for a x86_64 Linux host
-
-Always use the official versions from ARM, *DO NOT* install `gcc-arm-none-eabi` from Debian/Ubuntu.  
-For some unknown reasons, same gcc version from Debian creates a bootloader too large to fit in the allocated flash space.  
-Moreover it does not contain the `gdb` debugger.
-
-### install make
-
-* **Debian/Ubuntu alike**
-  * Open a terminal.
-  * Run the following command to install Make: `sudo apt-get install build-essential`
-* **Windows using Chocolatey:**
-  * Open a PowerShell terminal with administrator privileges.
-  * If not yet installed, run the following command to install Chocolatey:
-    ``` Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1')) ```
-  * In the same PowerShell terminal, run the following command to install Make using Chocolatey: `choco install make`
-* **macOS:**
-  * Open a terminal.
-  * If not yet installed, install Homebrew package manager by running the following command: `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"`
-  * Once Homebrew is installed, run the following command to install Make: `brew install make`
-
-### install nRF tools
-
-- Install nRF Util tool [nrfutil](https://www.nordicsemi.com/Products/Development-tools/nrf-util)
-  - Move it to a known path like `C:\nrfutil\` or `/usr/local/bin/`
-  - Add this path to the `PATH` Environment Variable if not yet there.
-- Install nRF Util packages:
-  - `nrfutil install completion device nrf5sdk-tools trace`
-- Install [nRF Command Line Tools](https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download) to get `nrfjprog`, `mergehex` etc.
-
-### install programmer tools
-
-Depending on the hardware programmer you want to use, additional tools are needed.
-
-- If you are using a J-Link:
-  
-  - Install [Segger J-Link Software](https://www.segger.com/downloads/jlink)
-  - alternatively, you can use openocd as described below
-  - Note: a JLink OB (or a STLink reflashed as a JLink OB) will not work on a nRF.
-
-- If you are using a ST-Link V2:
-  
-  - Install [openocd](https://openocd.org/pages/getting-openocd.html)
-  - If under Windows, install [ST-Link drivers](https://www.st.com/en/development-tools/stsw-link009.html), extract the zip and run `dpinst_amd64.exe`
-
-### configure the project
-
-- Edit `Makefile.defs`:
-  - Change `GNU_INSTALL_ROOT` (path of previously installed Compiler `bin` folder)
-  - Change `GNU_VERSION` (Version of the installed Compiler) (FIXME: is it really used?)
-  - Change the other paths to match your system if needed
-  - Don't forget to remove the `#` in front of the changed lines
-- Alternatively, if you are committing often code, it may be easier to leave `Makefile.defs` intact and to invoke `make` with the desired variables from a script, e.g. `make GNU_INSTALL_ROOT=../../../arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi/bin/`
-
-## Editing the code
-
-You can use [Visual Studio Code](https://code.visualstudio.com/download) to edit this project! Simply download and
-install it!
-
-- Install the [C++ Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools) in VS-Code.
-- Install
-  the [C++ Extension Pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools-extension-pack) in
-  VS-Code.
-- Create a new IntelliSense Configuration:
-  - press F1 in VS-Code and enter `C/C++: Edit Configurations (UI)`
-  - Add a new Configuration and name it
-  - Specify your Compiler path (path of previously installed Compiler `bin` folder)
-  - Change IntelliSense mode to `gcc-arm (legacy)`
-  - Add include path `${workspaceFolder}/**`
-
-## Compiling the code
-
-- Install prerequisites (for instructions have a look at [Prerequisites for compiling](#Prerequisites-for-compiling))
-- Run `build.sh` or try to execute its steps manually if your platform is not yet properly supported. Feedback is always welcome.
-
-The script produces several images in `objects`.
-
-* `fullimage.hex` to be used with a programmer over the SWD pins
-* `dfu-app.zip` and `dfu-full.zip` to be used with DFU mode
-
-## Uploading the code in DFU mode
-
-If the bootloader and the SoftDevice are already properly installed on the Chameleon, you can reflash it directly over DFU.
-
-To set the device in DFU mode:
-
-* you can use the Python client and issue the command `hw dfu`
-* you can use the script `resource/tools/enter_dfu.py` that does exactly the same but may be easier to call from your scripts
-* you can unplug the device, wait for it to sleep, then press the button B and plug it. If the application is bogus, this is the only way.
-
-The LEDs 4 & 5 should blink green when in DFU mode.
-
-To flash only the application (safer):
-
-`nrfutil device program --firmware objects/dfu-app.zip --traits nordicDfu`
-
-To flash everything (be sure to also have a JLink or ST-Link V2 programmer if something goes wrong):
-
-`nrfutil device program --firmware objects/dfu-full.zip --traits nordicDfu`
-
-Under Linux you can use the scripts `flash-dfu-app.sh` and `flash-dfu-full.sh`, they will put the device in DFU mode and flash it.
-
-## Uploading the code with a programmer
-
-Connect pins GND, SWC (swclk) and SWD (swdio) to your programmer.
-
-With a JLink and `nrfjprog`
-
-```
-# application only:
-nrfjprog -f nrf52 --program objects/application.hex --sectorerase --verify --reset
-# full:
-nrfjprog -f nrf52 --program objects/fullimage.hex --sectorerase --verify --reset
-```
-
-With a JLink and `openocd`
-
-```
-# application only:
-openocd -f interface/jlink.cfg -f target/nrf52.cfg -c "program objects/application.hex verify reset ; shutdown"
-# full:
-openocd -f interface/jlink.cfg -f target/nrf52.cfg -c "program objects/fullimage.hex verify reset ; shutdown"
-```
-
-With a ST-Link V2 and `openocd`
-
-```
-# application only:
-openocd -f interface/stlink.cfg -f target/nrf52.cfg -c "program objects/application.hex verify reset ; shutdown"
-# full:
-openocd -f interface/stlink.cfg -f target/nrf52.cfg -c "program objects/fullimage.hex verify reset ; shutdown"
-```
-
-## Uploading the code over BLE
-
-If you are adventurous it is possible to flash the device over BLE (DFU mode).
-
-To put the device in DFU mode
-
-* you can use the Python client and issue the command `hw dfu` **TODO:** this will be possible only when the client will be able to work over BLE...
-* you can use the script `resource/tools/enter_dfu_over_ble.py`
-
-Once in DFU mode, the device will announce itself over BLE as `CU-xxxx` where xxxx are the last 2 bytes of the Device Serial Number.
-
-Then use the official [nRF Device Firmware Update](https://www.nordicsemi.com/Products/Development-tools/nRF-Device-Firmware-Update) mobile application to flash one of the DFU images.
-
-## Debugging the code from VSCode
-
-- Install [Cortex-Debug](https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug) VS-Code Extension
-- Open `app_main.c`
-- Open the extension with `CTRL-SHIFT-D`
-- Klick on `create a launch.json file`
-- Select `Cortex-Debug`
-- Add this in the configuration bracket:
-
-```
-{
-    "cwd": "${workspaceFolder}",
-    "executable": "${workspaceRoot}/firmware/objects/bootloader.out",
-    "name": "Debug with JLink",
-    "request": "launch",
-    "type": "cortex-debug",
-    "runToEntryPoint": "main",
-    "showDevDebugOutput": "none",
-    "servertype": "jlink",
-    "device": "nrf52",
-    "interface": "swd",
-    "svdFile": "${workspaceRoot}/firmware/nrf52_sdk/modules/nrfx/mdk/nrf52.svd",
-}, 
-{
-    "cwd": "${workspaceFolder}",
-    "executable": "${workspaceRoot}/firmware/objects/bootloader.out",
-    "name": "Debug with STLink",
-    "request": "launch",
-    "type": "cortex-debug",
-    "runToEntryPoint": "main",
-    "showDevDebugOutput": "none",
-    "servertype": "openocd",
-    "device": "nrf52",
-    "svdFile": "${workspaceRoot}/firmware/nrf52_sdk/modules/nrfx/mdk/nrf52.svd",
-    "gdbPath": "C:/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10/bin/arm-none-eabi-gdb.exe",
-    "configFiles": [
-        "interface/stlink.cfg",
-        "target/nrf52.cfg"
-    ]
-}
-```
-
-- If you are jlink probe, create `settings.json` in {projectRoot}/.vscode directory.
-
-```
-{
-    "cortex-debug.armToolchainPath": "C:\\UserProgram\\arm_gcc\\none\\bin",
-    "cortex-debug.JLinkGDBServerPath": "C:\\Program Files\\SEGGER\\JLink\\JLinkGDBServerCL.exe",
-}
-```
-
-- To change `executable` target in `launch.json` to `application` or `bootloader`
-- In the debug menu you can select `Debug with JLink` or `Debug with STLink`
-
-## Debugging the code with gdb and openocd
-
-See first if you can execute `arm-none-eabi-gdb` from the installed tools.
-
-* gcc-arm-none-eabi-10.3-2021.10 gdb requires `libncurses5`
-* arm-gnu-toolchain-12.2.rel1 gdb requires Python 3.8
-
-In case Python 3.8 is not available anymore on your distro, to install a local copy you can do
-
-```
-wget https://www.python.org/ftp/python/3.8.17/Python-3.8.17.tgz
-tar zxvf Python-3.8.17.tgz
-cd Python-3.8.17
-./configure --prefix=$HOME/opt/python-3.8.17 --enable-shared
-make
-rm -rf ~/opt/python-3.8.17
-make install
-```
-
-Connect openocd to the device with a JLink or a ST-Link V2
-
-```
-openocd -f interface/jlink.cfg -f target/nrf52.cfg
-```
-
-```
-openocd -f interface/stlink.cfg -f target/nrf52.cfg
-```
-
-Then run gdb as follows
-
-```
-PYTHONHOME=~/opt/python-3.8.17/ arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi/bin/arm-none-eabi-gdb
-```
-
-and tell gdb to connect to openocd
-
-```
-target extended-remote localhost:3333
-```
-
-## BlackMagicProbe with RTT support, out of a ST-Link V2
-
-You can reflash a ST-Link V2 to use it as a BlackMagicProbe, to get support for RTT and see NRF_LOG messages.
-Some clones have only 64kb, this is too short.
-Even 128kb is too small when enabling RTT, but we can comment parts of the BMP source code.
-
-```
-git clone --recursive git@github.com:blackmagic-debug/stlink-tool.git
-( cd stlink-tool && make )
-```
-
-Then put the `stlink-tool` binary in your path.
-
-Get [BMP full sources](https://github.com/blackmagic-debug/blackmagic/releases)
-
-Comment out all probes except Nordic nrf51 in `src/target/cortexm.c` big switch for probes. It should remain
-
-```c
-    switch (t->designer_code) {
-    case JEP106_MANUFACTURER_NORDIC:
-        PROBE(nrf51_probe);
-        break;
-    }
-```
-
-```
-make -j PROBE_HOST=stlink ST_BOOTLOADER=1 ENABLE_RTT=1
-```
-
-Then flash the ST_Link V2
-
-```
-stlink-tool src/blackmagic.bin
-```
-
-See [src/platforms/stlink/README.md](https://github.com/blackmagic-debug/blackmagic/blob/main/src/platforms/stlink/README.md) for more details.
-Unplug/plug.  
-Every time you plug the ST-Link, you have to run `stlink-tool` to enable BMP.  
-Under linux, it is convenient to install [udev rules](https://github.com/blackmagic-debug/blackmagic/blob/main/driver/README.md#99-blackmagic-plugdevrules) to get aliases `/dev/ttyBmpGdb` and `/dev/ttyBmpTarg`.
-
-Note that using a native ST-Link V2 with BlackMagicProbe "hosted" will not allow to see NRF_LOG messages.
-
-## Debugging the code with gdb and BMP with RTT to monitor NRF_LOG
-
-Assuming you have a BlackMagicProbe with RTT support made out of a ST-Link V2.
-
-RTT usage: https://black-magic.org/usage/rtt.html
-
-```
-stlink-tool
-sleep 1
-screen /dev/ttyBmpTarg
-```
-
-In another terminal
-
-```
-$ arm-none-eabi-gdb
-(gdb) target extended-remote /dev/ttyBmpGdb
-(gdb) monitor swdp_scan
- 1      Nordic nRF52 M4
- 2      Nordic nRF52 Access Port.
-(gdb) attach 1
-(gdb) monitor rtt
-```
-
-We are now able to use gdb and see the NRF_LOG messages on the other terminal.
-
-## Using JLink with RTT to monitor NRF_LOG
-
-cf https://embeddedexplorer.com/nrf52-nrf-log-tutorial/
-
-```
-JLinkExe -if SWD -device nrf52 -speed 4000 -autoconnect 1
-```
-
-in a second terminal:
-
-```
-JLinkRTTClient
-```
-
-## Using SWO pin as UART to monitor NRF_LOG
-
-One can set `NRF_LOG_UART_ON_SWO_ENABLED := 1` in `Makefile.defs` to activate this functionality.
-When activated, NRF_LOG will be available if one connects a UART bridge to the SWO pin which will work as a UART TX pin.
-UART works at 115200 bauds. E.g. one can use a FTDI dongle and `screen /dev/ttyUSB0 115200`.
-Contrary to RTT that needs to be activated by a JTAG probe, UART logs are immediately available.
-
-Limitations:
-
-* SWO pin is shared with... SWO so when e.g. reflashing the device, garbage may appear on the monitoring terminal.
-* SWO pin is also shared with the blue channel of the RGB slot LEDs, so faint blue may appear briefly when logs are sent and LED might not work properly when supposed to be blue.
-
-# Resources
-
-* [nRF52840 Objective Product Specification v0.5.1](https://infocenter.nordicsemi.com/pdf/nRF52840_OPS_v0.5.1.pdf)

docs/firmware.md

@@ -1,120 +0,0 @@
-# Firmware
-
-The Chameleon flash contains several parts: the bootloader and its settings, the application, the user data and the SoftDevice.
-
-NOTE: If you are a developer searching for the building instructions, look into [development](./development.md)
-
-## The Bootloader
-
-The bootloader is the lowest-level program running on your Chameleon. It is read-only and provides the DFU (**D**evice **F**irmware **U**pgrade) mode. The bootloader being read-only, it makes it really hard to brick your Chameleon. The flash also contains a special section to store bootloader settings required by the nRF to deal with upgrades. This is only a concern for developers.
-
-
-You enter DFU mode by of the following methods:
-
-1. Physical button
-
-- Disconnect the Chameleon and wait for it to enter sleep mode
-- Hold down the 🅑 button. If you are using Windows you have to wait about ~5s before next step.
-- Plug USB into a PC while still holding the button. If you are using Windows you have to wait about ~10s before next step.
-- Then release the 🅑 button
-
-2. From CLI
-
-- Execute the command `hw dfu`
-
-3. From GUI
-
-- Click on `Enter DFU mode`
-
-4. From Shell
-
-- Execute the script `resource/tools/enter_dfu.py`
-
-The device stays in DFU mode for ~30s.
-While in DFU mode waiting for the update, the LEDs 4 and 5 blink alternatively green 🟢🟢.
-You can then perform firmware upgrades either via a GUI or the command line:
-
-1. Download nRF Util from the [nRF website](https://www.nordicsemi.com/Products/Development-tools/nrf-util)
-
-2. Open a Command Line / Terminal on your PC
-
-3. Install the "device" toolkit by running `nrfutil install device`
-
-4. Download the Chameleon firmware from [GitHub](https://github.com/RfidResearchGroup/ChameleonUltra/releases). At the moment it is better to take the *Development release* but beware bugs can occur. Choose `ultra-dfu-app.zip` for the Ultra or the Devkit, and `lite-dfu-app.zip` for the Lite.
-
-5. Put your Chameleon into DFU mode and install the firmware with the following command: `nrfutil device program --firmware ultra-dfu-app.zip --traits nordicDfu` (keep in mind to change the filename if you are using a Lite).
-
-Step 5: Alternatively you can connect the Chameleon over USB and use the script `firmware/flash-dfu-app.sh` which will take care of flipping it into DFU mode and flashing it with the adequate firmware.
-
-While flashing firmware is in progress, the LEDs 4 and 5 should blink fast blue 🔵🔵 and the firmware update should be finished in a matter of seconds. Using DFU and performing a firmware update also helps recovering from most device-related issues.
-
-If LEDs 4 and 5 are flashing slow red 🔴🔴, it indicates an issue with DFU. Try to unplug and plug again or unplug and wait for it to timeout and try again the whole procedure.
-
-## The Application
-
-The application is the piece of software being loaded by the bootloader. It communicates with the client, emulates, reads and writes cards, drives the LEDs, handles buttons and much more. The application is also writable, it is the piece of software being updated via DFU.
-
-The communication with the application is either done via the CLI or a GUI. Communication can be done over USB or BLE (**B**luetooth **L**ow **E**nergy), although, at time of writing, only GUIs support BLE.
-
-On boot, the application starts in emulation mode, so it can emulate up to 8 HF tags and up to 8 LF tags (one slot can handle both a HF and a LF).
-
-The Chameleon can be awaken:
-
-- by pressing a button
-- when it comes close to a HF or LF field, *only if* a card corresponding to that field (HF/LF) is loaded into the active slot.
-
-The white LED labeled RF lights up when it detects a field, again only if the active slot supports it.
-
-In some situations, it can be cumbersome to wait for the boot-up animation. This is configurable, cf e.g. the CLI command `hw settings animation set -h`.
-
-On a new Chameleon (or after a factory reset), 3 slots are defined, slot 1 holding both a HF and a LF:
-
-- slot 1 LF: a EM4100 with UID `DEADBEEF88`
-- slot 1 HF: a MIFARE Classic 1k with UID `DEADBEEF`
-- slot 2 HF: a MIFARE Classic 1k with UID `DEADBEEF`
-- slot 3 LF: a EM4100 with UID `DEADBEEF88`
-
-When a slot is selected, the LED shows what type of card is loaded with the following color code:
-
-- 🟢 HF card loaded
-- 🔵 LF card loaded
-- 🔴 Both HF and LF loaded
-
-When a dual HF/LF slot is activated by an external field, it will turn green or blue according to the frequency.
-
-The application controls the buttons. The behavior of the buttons is customizable via the CLI or a GUI. The default behavior is the following:
-
-- 🅐 short press: Select previous slot
-
-- 🅑 short press: Select next slot
-
-- 🅐 long press: Copy LF or HF tag UID (only Ultra, not Lite)
-
-- 🅑 long press: Copy LF or HF tag UID (only Ultra, not Lite)
-
-*About UID copy*: the action depends on the current slot support. So to be able to copy an EM4100 LF tag, the slot must be configured firstly to emulate an EM4100 tag. And to be able to copy a HF 14a tag, the slot must be configured for the right type of HF tag. Only the UID will be copied, not the data.
-
-The Chameleon also shows the following LED effects:
-
-- Charging: 4 pulsing green lights
-
-- CLI / GUI connected over USB: Chasing LEDs in the color of the selected slot (left to right for slots 1-4 and right to left for slots 5-8).
-
-The device enters sleep mode after about 5s unless it is plugged in USB or if a client is connected over BLE. You can use the buttons to wake it up again. You can also press quickly a button during the sleep animation to keep the device awake.
-
-## Write Modes
-- **Normal**: Behaves like any normal card
-- **Denied**: Read-only card, send NACK to write attempts
-- **Deceive**: Accepts write commands but don't change any data (reader thinks write was successful but when reading back, nothing changed)
-- **Shadow**: Accepts writes but reverts changes when device goes to sleep (reader can read and write like a normal card but changes are kept in RAM and are lost when the chameleon goes to sleep) 
-
-## The SoftDevice
-
-A [SoftDevice](https://infocenter.nordicsemi.com/index.jsp?topic=%2Fstruct_nrf52%2Fstruct%2Fnrf52_softdevices.html) is a precompiled and linked binary software implementing a wireless protocol developed by Nordic Semiconductor.
-
-We are using the [SoftDevice S140](https://infocenter.nordicsemi.com/index.jsp?topic=%2Fstruct_nrf52%2Fstruct%2Fnrf52_softdevices.html) which implements a BLE Central and Peripheral protocol stack solution.
-
-## The User Data
-
-The Chameleon has a reserved space of memory and flash where it stores application settings, active slot and slots configurations and data. This will not be overwritten by DFU updates and the data will only be reset by either issuing `hw factory_reset --i-know-what-im-doing` in the CLI or clicking `Factory reset` in a GUI.
-*Warning:* Settings and/or data might be reset to defaults if you downgrade the firmware version up to a version not supporting the newer format.

docs/gui.md

@@ -1,8 +0,0 @@
-# GUIs
-
-There are multiple GUIs to control your Chameleon, two are featured in this documentation.
-Note that in spite of what their name may suggest, all GUIs support both the Ultra and the Lite.
-
-- [Chameleon Ultra GUI](./chameleonultragui.md) ([github](https://github.com/GameTec-live/ChameleonUltraGUI))
-
-- [MTools Lite for iOS](https://shop.mtoolstec.com/mifare-classic-tool-for-ios)

docs/hardware.md

@@ -1,51 +0,0 @@
-# Hardware
-
-The Chameleon comes in 3 Hardware variants, the Ultra, the Lite and the Devkit.
-
-## The Ultra
-
-The Chameleon Ultra comes in a black box with gold printing. This box has the following dimensions: 9.5 cm x 5.5 cm x 3.5 cm
-
-![box.png](./images/ultra-box.jpg)
-
-The Box contains a foam pad, a USB cable that has a removable end to convert it to USB-C, a Proxgrind 3.5 hex screwdriver, 2 replacement screws and a keychain and the device itself.
-
-![box-contents.jpg](./images/ultra-box-contents.jpg)
-
-The device itself features 4 screws holding it together, 2 buttons labeled `A` and `B`.  The device consists of 2 PCBs (**P**rinted **C**ircuit **B**oards) and a plastic spacer, one contains the Electronic and the HF (**H**igh **F**requency), 13.56 MHz, antenna as well as the 8 LEDs indicating which slot is currently active and the other board features the Chameleon Ultra text, the screws and the LF (**L**ow **F**requency), 125KHz, antenna. The plastic spacer houses the battery as well as the ferrite pad which enables HF and LF emulation at the same time. It also has has the USB-C charging and data port and a hole for inserting the keychain loop. The Chameleon Ultra dimensions are: 2.4cm x 4cm x 8mm 
-
-![ultra.png](./images/ultra.jpg)
-
-## The Lite
-
-The Chameleon Lite comes in a white box with blue printing. This box has the following dimensions: 9.5 cm x 6 cm x 3.5 cm
-
-![lite-box.jpg](./images/lite-box.jpg)
-
-The Box contains a foam pad, a USB cable that has a removable end to convert it to USB-C and the device itself.
-
-![lite-box.-contents.jpg](./images/lite-box-contents.jpg)
-
-The device itself features 2 buttons labeled with arrows. The device consists of one PCB in a blue plastic housing. This one PCB contains the electronics and the HF antenna as well as the 8 LEDs indicating which slot is currently active, and the USB-C port. The LF antenna is glued onto the back of the PCB and is visible through the housing. The battery is soldered in place and the housing is held together by thin fragile pins which are easy to snap. It is not designed to be disassembled. The keychain loop is also relatively fragile, so be careful. The Chameleon Lites dimensions are: 3.6 cm x 6.1 cm x 0.8 cm
-
-![lite.jpg](./images/lite.jpg)
-
-## The Devkit
-
-Just like the Chameleon Ultra, the Devkit comes in a black box with gold printing. This box has the following dimensions: 12 cm x  8 cm x 3.5 cm
-
-![devkit-box.jpg](./images/devkit-box.jpg)
-
-Again, just like the lite, the box contains a foam pad, a USB cable that has a removable end to convert it to USB-C and the device itself.
-
-![devkit-box-contents.jpg](./images/devkit-box-contents.jpg)
-
-The device itself features 2 buttons labeled `A` and `B`. The device is made of only one PCB without a case. At the bottom of this PCB both the HF and LF coils are found. Because it is a Devkit, this Chameleon has its SWD (**S**ingle **W**ire **D**ebug) port and some testpoints exposed. (In the photos below, a pinheader is already soldered into the SWD port, this is not the case from factory) The Chameleon Devkit dimensions are:  5.3 cm x 8.5 cm x 1.1 cm (including rubber feet, battery and buttons. PCB thickness: 0,16 cm)
-
-![devkit.jpg](./images/devkit.jpg)
-
-## What is the difference between the Lite and the Ultra/DevKit?
-
-The Chameleon Ultra as well as the Devkit contain a second chip called [MFRC522 ](https://www.nxp.com/docs/en/data-sheet/MFRC522.pdf). This chip allows the Chameleon to read and write to HF 14a tags. The Chameleon Lite does not contain this chip and therefore cannot read and write HF tags, it can only simulate some. The Chameleon Lite also swaps the big LIPO (**LI**thium **PO**lymer) battery with a smaller buttoncell. The Devkit is a Chameleon Ultra on a bigger PCB and with a bigger battery and some component differences such as a mechanical relay but which should not make any practical difference.
-
-#