Merge pull request #2 from rosflight/old-workflows-and-files

Old workflows and files

.github/workflows/build_pixracer_pro.yml

@@ -0,0 +1,17 @@
+name: Build Pixracer Pro
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: install toolchain
+      run: sudo apt -y install gcc-arm-none-eabi
+    - name: check toolchain
+      run: arm-none-eabi-gcc --version
+    - name: build
+      run: cd pixracer_pro && mkdir build && cd build && cmake .. && make

.github/workflows/build_varmint_10X.yml

@@ -0,0 +1,17 @@
+name: Build Varmint 10X
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: install toolchain
+      run: sudo apt -y install gcc-arm-none-eabi
+    - name: check toolchain
+      run: arm-none-eabi-gcc --version
+    - name: build
+      run: cd varmint_10X && mkdir build && cd build && cmake .. && make

.gitignore

@@ -0,0 +1 @@
+build/

LICENSE

@@ -0,0 +1,28 @@
+BSD 3-Clause License
+
+Copyright (c) 2024, AeroVironment Inc.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

README.md

@@ -1 +1,9 @@
-Board Support for a couple of STM32H7x3 based flight controllers
+[![Build Varmint 10X](https://github.com/rosflight/varmint_h7/actions/workflows/build_varmint_10X.yml/badge.svg)](https://github.com/rosflight/varmint_h7/actions/workflows/build_varmint_10X.yml) [![Build Pixracer Pro](https://github.com/rosflight/varmint_h7/actions/workflows/build_pixracer_pro.yml/badge.svg)](https://github.com/rosflight/varmint_h7/actions/workflows/build_pixracer_pro.yml)
+
+# Varmint H7
+
+This repository contains a board implementation of the [ROSflight firmware](https://github.com/rosflight/rosflight_firmware) for AeroVironment's Varmint FCU package, a STM32H753 based flight controller with a NVIDIA Jetson Orin NX on board. It also has an implementation for 3DR's [PixRacer Pro](https://docs.3dr.com/autopilots/pixracer-pro/#downloads) autopilot, which has a very similar configuration to the Varmint board.
+
+This code is based off of a [STM32cubeMX](https://www.st.com/en/development-tools/stm32cubemx.html) project, which enables quick configuration of the H7 processor. STM32cubeMX works by generating code for the configuration specified by the STM32cubeMX software. The generated code contains sections of "BEGIN USER CODE" and "END USER CODE" that the developer can then add their code inside. User code inside of these sections will persist between reconfigurations of the H7, while anything outside will be overwritten.
+
+This repository can be compiled as a standalone project or as a submodule of the firmware. Standalone compilation is only used for testing, as none of the ROSflight firmware functionality is included. When compiling with the firmware repository, use the CMakeLists.txt file found in the root of the firmware repo.