initial commit

src/content/docs/0_overview/index.md

@@ -0,0 +1,8 @@
+---
+title: Introduction
+description: An introduction for the project.
+---
+
+## Used Hardware
+
+- [Seeed XIAO BLE](https://www.seeedstudio.com/Seeed-XIAO-BLE-nRF52840-p-5201.html)

src/content/docs/1_record_app/0_index.mdx

@@ -0,0 +1,129 @@
+---
+title: Requirements & Setup
+description: A reference page in my new Starlight docs site.
+---
+
+import { Steps, Tabs, TabItem } from "@astrojs/starlight/components";
+
+## Flutter Installation
+
+<Tabs>
+  <TabItem label="Windows">
+  <Steps>
+1. Flutter requires [git](https://git-scm.com) which can be installed at [https://git-scm.com/download/win](https://git-scm.com/download/win)
+
+1. Install Puro with the following command:
+
+   ```bash
+   Invoke-WebRequest -Uri "https://puro.dev/builds/1.4.8/windows-x64/puro.exe" -OutFile "$env:temp\puro.exe"; &"$env:temp\puro.exe" install-puro --promote
+   ```
+
+1. After installing Puro reload your shell and make sure the `puro` command is accessible.
+
+1. Initialize Puro with the latest stable Flutter version:
+
+   ```bash
+    puro flutter
+   ```
+
+1. Now the commands `flutter` and `dart` should be accessible in your shell. You are all set up with the latest stable Flutter and Dart version! For more infos check out [https://puro.dev/](https://puro.dev/).
+
+</Steps>
+  </TabItem>
+  <TabItem label="macOS">
+    <Steps>
+
+1. Flutter requires [git](https://git-scm.com) which can be installed with [Homebrew](https://brew.sh) for macOS:
+
+   ```bash
+   brew install git
+   ```
+
+1. Install Puro with the following command:
+
+   ```bash
+   curl -o- https://puro.dev/install.sh | PURO_VERSION="1.4.8" bash
+   ```
+
+1. After installing Puro reload your shell and make sure the `puro` command is accessible.
+
+1. Initialize Puro with the latest stable Flutter version:
+
+   ```bash
+    puro flutter
+   ```
+
+1. Now the commands `flutter` and `dart` should be accessible in your shell. You are all set up with the latest stable Flutter and Dart version! For more infos check out [https://puro.dev/](https://puro.dev/).
+
+</Steps>
+  </TabItem>
+  <TabItem label="Linux">
+    <Steps>
+
+1. Flutter requires [git](https://git-scm.com) which can be installed with most package managers e.g. apt:
+
+   ```bash
+   sudo apt install git
+   ```
+
+1. Install Puro with the following command:
+
+   ```bash
+   curl -o- https://puro.dev/install.sh | PURO_VERSION="1.4.8" bash
+   ```
+
+1. After installing Puro reload your shell and make sure the `puro` command is accessible.
+
+1. Initialize Puro with the latest stable Flutter version:
+
+   ```bash
+    puro flutter
+   ```
+
+1. Now the commands `flutter` and `dart` should be accessible in your shell. You are all set up with the latest stable Flutter and Dart version! For more infos check out [https://puro.dev/](https://puro.dev/).
+
+</Steps>
+  </TabItem>
+</Tabs>
+
+## TinyGO Installation
+
+<Tabs>
+  <TabItem label="Windows">
+  <Steps>
+
+1.  It is recommended to use [Scoop](https://scoop.sh) to install TinyGo and it's dependencies on Windows:
+
+    ```bash
+    scoop install go
+    ```
+
+    Followed by:
+
+    ```bash
+    scoop install tinygo
+    ```
+
+</Steps>
+
+</TabItem>
+
+<TabItem label="macOS">
+<Steps>
+
+1.  Use [Homebrew](https://brew.sh) to install TinyGo:
+    ```bash
+    brew tap tinygo-org/tools
+    brew install tinygo
+    ```
+
+</Steps>
+  </TabItem>
+  <TabItem label="Linux">
+    <Steps>
+    
+1. The Linux installation can change depending on the latest TinyGo version and the used distro, check out the installation guide [here](https://tinygo.org/getting-started/install/linux/).
+
+</Steps>
+  </TabItem>
+</Tabs>

src/content/docs/1_record_app/1_tinygo_code.md

@@ -0,0 +1,58 @@
+---
+title: TinyGo Code
+description: A reference page in my new Starlight docs site.
+hero:
+  title: "TinyGo Code"
+  tagline: A Go Compiler For Small Places.
+  image:
+    alt: A glittering, brightly colored logo
+    file: ../../../assets/tinygo-logo.webp
+---
+
+[TinyGo](https://tinygo.org/) is a custom Go compiler for embedded systems and WebAssembly. It was used
+to write the microcontroller code for recording the gyro data via Bluetooth.
+
+## Setup
+
+Grab the project files:
+
+```bash
+git clone https://avoid.sh/PetActivityMonitor/pet_activity_recorder_tinygo.git
+```
+
+And follow the information in the `README.md` file of the project.
+
+## Usage
+
+Only connect one microcontroller at the same time!
+
+- Flash the code to the connected microcontroller.
+
+```bash
+make flash
+```
+
+- Flash the code in production mode (deactivated serial).
+
+```bash
+make production
+```
+
+- Flash the code in testing mode (enhanced optimisations that need more testing)
+
+```bash
+make testing
+```
+
+To set the microcontroller into a flashable state manually the project also includes a
+`flashing_time.py` python script.
+
+The script requires `pyserial`:
+
+```bash
+python -m pip install pyserial
+```
+
+When running the code with `./flashing_time` or `make prepare` (inside of the project directory) the microcontroller will be put in a flashable state.
+
+This state can also be activated manually by tapping the reset button on the microcontroller twice in a short time.

src/content/docs/1_record_app/2_flutter_code.mdx

@@ -0,0 +1,64 @@
+---
+title: Flutter Code
+description: A reference page in my new Starlight docs site.
+hero:
+  title: "Flutter Code"
+  tagline: Build apps for any screen.
+  image:
+    alt: A glittering, brightly colored logo
+    file: ../../../assets/come_to_the_dartside.webp
+---
+
+import { Steps } from "@astrojs/starlight/components";
+
+The app for receiving and storing the data from the microcontroller was written in
+[Flutter](https://flutter.dev/) with the [Dart](https://dart.dev/) programming language.
+
+The app has support for:
+
+- Windows
+- macOS
+- Linux
+- Android
+- iOS
+
+## Setup
+
+<Steps>
+
+1. Grab the project files:
+
+   ```bash
+   git clone https://avoid.sh/PetActivityMonitor/xiao_pet_tracker.git
+   ```
+
+2. Run `flutter pub get` to load the dependencies.
+
+3. The project contains 3 flavors:
+
+   - development
+   - staging
+   - production
+
+   To run the desired flavor either use the launch configuration in VSCode/Android Studio or use the following commands:
+
+   ```sh
+   # Development
+   $ flutter run --flavor development --target lib/main_development.dart
+
+   # Staging
+   $ flutter run --flavor staging --target lib/main_staging.dart
+
+   # Production
+   $ flutter run --flavor production --target lib/main_production.dart
+   ```
+
+   The `development` flavor is used for developing, it includes Dart's Hot Reload feature where you
+   can make live changes to the code and immediately use these changes in the running app without restarting it.
+
+   When using the app the `production` flavor is recommended. This will compile the app natively with
+   much deeper optimizations.
+
+   The `staging` flavor is not needed to be used in the current state of the app.
+
+</Steps>

src/content/docs/1_record_app/3_record_app.mdx

@@ -0,0 +1,49 @@
+---
+title: App Usage
+description: A reference on how to use the app.
+---
+
+import PhotoSwipe from "../../../components/PhotoSwipe.astro";
+import { Steps } from "@astrojs/starlight/components";
+
+Here's a short usage guide on the recording app. This uses the iOS version of the app, but it works similiar
+for Android, Linux, macOS and Windows.
+
+<Steps>
+
+1.  When you open the app you will be greeted with the `Xiao Connector` screen. Tap on `Connect` to connect to the microcontroller.
+
+    <PhotoSwipe imageFolder="xiao_app_screenshots" image="IMG_0377.PNG" />
+
+2.  To conserve power, the microcontroller enters a low-power mode upon Bluetooth connection, preventing automatic
+    acceleration data recording. To access a live feed, manually activate it by tapping on `Open Live Feed`.
+
+    <PhotoSwipe imageFolder="xiao_app_screenshots" image="IMG_0376.PNG" />
+
+3.  This is what the feed looks like when you are connected.
+
+    <PhotoSwipe imageFolder="xiao_app_screenshots" image="IMG_0378.PNG" />
+
+    A tap on `Sync Clocks` can be used to manually sync the clocks between the recording device and the microcontroller.
+
+    To start recording, enter a name and then tap on the start button at the bottom of the screen.
+
+    <PhotoSwipe imageFolder="xiao_app_screenshots" image="IMG_0379.PNG" />
+
+    To stop the recording, tap on the button at the bottom of the screen again.
+
+4.  Now you can switch to the `Recordings` screen by tapping on the `Recordings` icon in the navbar.
+    You'll see your newly created recording that was stored on your device.
+
+    <PhotoSwipe imageFolder="xiao_app_screenshots" image="IMG_0380.PNG" />
+
+    Tap on it to see the details of the recording and to access the `Export` functionality.
+
+    <PhotoSwipe imageFolder="xiao_app_screenshots" image="IMG_0381.PNG" />
+
+5.  The exported files will be stored in the documents of your device. Here we used an iPhone and we can
+    find the exported recording data as a CSV file in the app's folder in Files.
+
+    <PhotoSwipe imageFolder="xiao_app_screenshots" image="IMG_0382.PNG" />
+
+</Steps>

src/content/docs/2_analysis/0_index.mdx

@@ -0,0 +1,43 @@
+---
+title: Requirements & Setup
+description: A reference page in my new Starlight docs site.
+---
+
+import { Steps, Tabs, TabItem } from "@astrojs/starlight/components";
+
+## Rust Installation
+
+If your using Windows, check out the guide [here](https://rustup.rs/#).
+Otherwise:
+
+<Steps>
+
+1.  Run the following in your terminal, then follow the onscreen instructions.
+
+    ```bash
+    curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
+    ```
+
+1.  Get the `adafruit-nrfutil` from [here](https://learn.adafruit.com/introducing-the-adafruit-nrf52840-feather/update-bootloader-use-command-line). Follow the installation guide on their website.
+
+1.  Install `arm-none-eabi-objcopy` on your device.
+
+    On macOS you can get it from Homebrew:
+
+    ```bash
+    brew install arm-none-eabi-gcc
+    ```
+
+    On Ubuntu install it with apt:
+
+    ```bash
+    sudo apt install gcc-arm-none-eabi
+    ```
+
+    Use scoop on Windows:
+
+    ```bash
+    scoop install gcc-arm-none-eabi
+    ```
+
+</Steps>

src/content/docs/2_analysis/1_rust_code.mdx

@@ -0,0 +1,62 @@
+---
+title: Rust Code
+description: A reference page in my new Starlight docs site.
+hero:
+  title: "Seeed XIAO nRF52840 with Rust"
+  tagline: Blazingly fast on-device inference.
+  image:
+    alt: A glittering, brightly colored logo
+    file: ../../../assets/ferris_embedded.webp
+---
+
+import { Steps, Tabs, TabItem } from "@astrojs/starlight/components";
+
+The analysis of the acceleration and rotation data on-device requires us to run a TinyML model on the microcontroller in an efficient manner.
+TinyGo unfortunately does not have any support for running TinyML models at the moment
+and we had to switch to Rust.
+
+## Why Rust?
+
+The decision to adopt Rust was driven by several key factors,
+particularly its suitability for resource-constrained embedded environments.
+
+- **[MicroFlow](https://github.com/matteocarnelos/microflow-rs) integration**: Developed by Matteo Carnelos, MicroFlow excels in deploying machine learning models on embedded systems. Its compiler-based architecture, consisting of the microflow-macros and microflow crates, allows for efficient model parsing, preprocessing, and runtime execution.
+- **[Embassy](https://embassy.dev) for Asynchronous Programming**: Rust's embassy framework provided us with a robust and user-friendly solution for asynchronous programming. This was essential for managing concurrent tasks and optimizing performance on the microcontroller. Embassy greatly simplifies the development of responsive and efficient embedded applications.
+- **Performance and Memory Efficiency**: Rust's focus on performance and memory safety aligns perfectly with the requirements of TinyML. Its zero-cost abstractions and control over memory management enable us to optimize our model execution for minimal resource consumption.
+- **Memory Safety**: In embedded systems, memory errors can lead to unpredictable behavior and system crashes. Rust's strong memory safety guarantees, enforced at compile time, prevent common errors like buffer overflows, dangling pointers, and data races. This is crucial for ensuring the reliability and stability of our on-device TinyML implementation.
+
+## Rust Support for the Xiao Seeed BLE
+
+There was no full implementation for the Xiao Seeed BLE microcontroller available anywhere online in Rust. The embassy library has support for the `nrf52840` SoC, but we
+had to write custom drivers to access the acceleration and rotation data from the `lsm6ds3tr` IMU.
+
+These driver are available [here](https://avoid.sh/PetActivityMonitor/lsm6ds3tr).
+
+## Usage
+
+<Steps>
+
+1. Get the Rust project files:
+
+   ```bash
+   git clone https://avoid.sh/PetActivityMonitor/xiao_pet_tracker_rust.git
+   ```
+
+   The project contains multiple Rust projects separated into folders.
+
+1. The project contains a `build_and_flash.sh` script to easily build the project and flash it to the microcontroller. Put the microcontroller into DFU mode and run the script with the folder name of the project as secondary parameter.
+
+   ```bash
+   # flash the lsm6ds3tr demo
+   ./build_and_flash.sh lsm6ds3tr_demo
+   # flash the tflite demo
+   ./build_and_flash.sh tflite_demo
+   ```
+
+   Make sure to edit the `COM_PORT` variable accordingly to your connected controller. You can use `tinygo ports` from the commandline to check the ports.
+
+</Steps>
+
+## Issues
+
+After flashing the microcontroller with the Rust project, the DFU mode can only be entered manually by clicking the reset button twice in a short time. It is currently not possible to send a signal to the device to enter the DFU mode.

src/content/docs/faq.md

@@ -0,0 +1,7 @@
+---
+title: FAQ
+description: A guide in my new Starlight docs site.
+---
+
+Guides lead a user through a specific task they want to accomplish, often with a sequence of steps.
+Writing a good guide requires thinking about what your users are trying to do.

src/content/docs/index.mdx

@@ -0,0 +1,19 @@
+---
+title: Welcome to the Pet Activity Monitor Project!
+description: Tracking pet activity with microcontrollers and machine learning.
+template: splash
+hero:
+  tagline: Tracking pet activity with microcontrollers and machine learning.
+  image:
+    file: ../../assets/logo.webp
+  actions:
+    - text: Let's go!
+      link: /0_overview/
+      icon: right-arrow
+    - text: Check out the source code.
+      link: https://avoid.sh/PetActivityMonitor
+      icon: external
+      variant: minimal
+---
+
+import { Card, CardGrid } from "@astrojs/starlight/components";