Trying to Fix CI

Author: Mikefly123

.github/workflows/ci.yaml

@@ -14,17 +14,83 @@ jobs:
       - name: Lint
         run: |
           make fmt
+
   build:
     runs-on: ubuntu-latest
+
     steps:
-      - uses: actions/checkout@v4
-      - name: Build
-        run: |
-          make build
-      - name: Archive
-        uses: actions/upload-artifact@v4
-        with:
-          name: artifacts
-          path: |
-            build-artifacts/zephyr.uf2
-            build-artifacts/zephyr/fprime-zephyr-deployment/dict/ReferenceDeploymentTopologyDictionary.json
+    - name: Checkout repository
+      uses: actions/checkout@v4
+      with:
+        submodules: recursive
+        fetch-depth: 0
+
+    - name: Install system dependencies
+      run: |
+        sudo apt-get update
+        sudo apt-get install -y \
+          git cmake ninja-build gperf ccache dfu-util \
+          device-tree-compiler wget xz-utils file make gcc \
+          gcc-multilib g++-multilib libsdl2-dev libmagic1
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: '3.11'
+        cache: 'pip'
+
+    - name: Cache Zephyr workspace
+      id: cache-zephyr
+      uses: actions/cache@v4
+      with:
+        path: |
+          lib/zephyr-workspace
+          ~/zephyr-sdk-0.17.2
+        key: zephyr-minimal-${{ hashFiles('west.yml') }}-${{ runner.os }}
+        restore-keys: |
+          zephyr-minimal-${{ hashFiles('west.yml') }}-
+          zephyr-minimal-
+
+    - name: Setup minimal Zephyr environment
+      run: |
+        make zephyr-setup
+      env:
+        # Speed up pip installs
+        PIP_DISABLE_PIP_VERSION_CHECK: 1
+        PIP_NO_COMPILE: 1
+
+    - name: Display setup statistics
+      run: |
+        echo "=== Zephyr Setup Statistics ==="
+        echo "Workspace size: $(du -sh lib/zephyr-workspace 2>/dev/null || echo 'N/A')"
+        echo "SDK size: $(du -sh ~/zephyr-sdk-0.17.2 2>/dev/null || echo 'N/A')"
+        echo "Modules installed:"
+        west list 2>/dev/null || echo "West not initialized"
+
+    - name: Build for PROVES Flight Control Board v5c
+      run: |
+        make build
+
+    - name: Upload build artifacts
+      uses: actions/upload-artifact@v4
+      with:
+        name: firmware-v5c
+        path: |
+          build-artifacts/zephyr.uf2
+          build-artifacts/zephyr.elf
+          build-artifacts/zephyr.hex
+          build-artifacts/zephyr.bin
+        retention-days: 30
+
+    - name: Display build statistics
+      if: success()
+      run: |
+        echo "=== Build Statistics ==="
+        if [ -f build-artifacts/zephyr.uf2 ]; then
+          echo "Firmware size: $(ls -lh build-artifacts/zephyr.uf2 | awk '{print $5}')"
+        fi
+        if [ -f build-fprime-automatic-zephyr/zephyr/zephyr.stat ]; then
+          echo ""
+          echo "Memory usage:"
+          cat build-fprime-automatic-zephyr/zephyr/zephyr.stat || true
+        fi

Makefile

@@ -27,6 +27,10 @@ zephyr-setup: fprime-venv ## Set up Zephyr environment (minimal RP2040/RP2350 on
 		echo "Setting up minimal Zephyr environment (RP2040/RP2350 only)..."; \
 		echo "  - Using minimal module set (~80% disk space reduction)"; \
 		echo "  - Installing ARM toolchain only (~92% SDK reduction)"; \
+		if [ ! -f .west/config ] && [ ! -f ../.west/config ]; then \
+			echo "  - Initializing West workspace..."; \
+			$(UVX) west init -l .; \
+		fi && \
 		$(UVX) west update && \
 		$(UVX) west zephyr-export && \
 		$(UV) run west packages pip --install && \

docs/additional-resources/west-manifest-setup.md

@@ -28,11 +28,13 @@ Use the convenience script that handles everything:
 ```
 
 This script will:
-1. Initialize the West workspace
+1. Initialize the West workspace (if not already initialized)
 2. Download only the minimal modules
 3. Export the Zephyr CMake package
 4. Install only the ARM toolchain (~95 MB instead of ~1.2 GB)
 
+**Note**: The script automatically detects if you're in a fresh clone (like in CI/CD) and initializes West workspace accordingly.
+
 ### Option B: Manual Setup
 
 If you prefer to run the commands manually:
@@ -180,8 +182,69 @@ west list
 west build -b proves_flight_control_board_v5c FprimeZephyrReference/ReferenceDeployment
 ```
 
+## CI/CD Setup
+
+The minimal setup works great in CI/CD environments like GitHub Actions. Here's an example workflow:
+
+```yaml
+name: Build
+
+on: [push, pull_request]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          submodules: recursive
+
+      - name: Setup Zephyr (Minimal)
+        run: |
+          make zephyr-setup
+
+      - name: Build
+        run: |
+          make build
+```
+
+### Benefits in CI/CD
+- **Faster builds**: 3-7 min setup vs 40-60 min
+- **Lower costs**: Less compute time
+- **Better caching**: Smaller artifacts to cache
+- **Reliable**: Deterministic module versions
+
+### Caching Strategy
+
+For even faster CI/CD, cache the Zephyr workspace:
+
+```yaml
+- name: Cache Zephyr Workspace
+  uses: actions/cache@v3
+  with:
+    path: |
+      lib/zephyr-workspace
+      ~/zephyr-sdk-0.17.2
+    key: zephyr-${{ hashFiles('west.yml') }}
+
+- name: Setup Zephyr (if cache miss)
+  run: |
+    if [ ! -d "lib/zephyr-workspace/modules" ]; then
+      make zephyr-setup
+    fi
+```
+
 ## Troubleshooting
 
+### "no west workspace found" error in CI/CD
+
+If you see this error:
+```
+FATAL ERROR: no west workspace found
+```
+
+**Solution**: The Makefile now automatically runs `west init -l .` when needed. Make sure you're using the updated `Makefile` from this project.
+
 ### "Module not found" errors during build
 
 If you encounter errors about missing modules during build, you may need to add that specific module to `west.yml`. Check the error message for the module name and add it following the pattern in the manifest.