Remove basic firmware profile, overlays, CI builds, and doc references

paxx12 · paxx12 · commit 4095a0c94150 · 2026-03-23T17:26:59.000+01:00
diff --git a/.github/workflows/pre_release.yaml b/.github/workflows/pre_release.yaml
@@ -55,9 +55,6 @@ jobs:
     - name: Download firmware
       run: ./dev.sh make firmware
 
-    - name: Build with Basic firmware
-      run: ./dev.sh make build PROFILE=basic OUTPUT_FILE=U1_basic_${{ env.GIT_VERSION }}_upgrade.bin
-
     - name: Build with Extended Fluidd firmware
       run: ./dev.sh make build PROFILE=extended OUTPUT_FILE=U1_extended_${{ env.GIT_VERSION }}_upgrade.bin
 
diff --git a/.github/workflows/pull_request.yaml b/.github/workflows/pull_request.yaml
@@ -94,33 +94,17 @@ jobs:
     - name: Download firmware
       run: ./dev.sh make firmware
 
-    - name: Build with Basic firmware
-      run: ./dev.sh make build PROFILE=basic OUTPUT_FILE=U1_basic_${{ env.GIT_VERSION }}_upgrade.bin
-
     - name: Build with Extended Fluidd firmware
       run: ./dev.sh make build PROFILE=extended OUTPUT_FILE=U1_extended_${{ env.GIT_VERSION }}_upgrade.bin
 
-    - name: Build DEVEL version of Basic firmware
-      run: ./dev.sh make build PROFILE=basic-devel OUTPUT_FILE=U1_basic_${{ env.GIT_VERSION }}_devel.bin
-
     - name: Build DEVEL version of Extended Fluidd firmware
       run: ./dev.sh make build PROFILE=extended-devel OUTPUT_FILE=U1_extended_${{ env.GIT_VERSION }}_devel.bin
 
-    - uses: actions/upload-artifact@v4
-      with:
-        name: basic-build
-        path: U1_basic_*_upgrade.bin
-
     - uses: actions/upload-artifact@v4
       with:
         name: extended-build
         path: U1_extended_*_upgrade.bin
 
-    - uses: actions/upload-artifact@v4
-      with:
-        name: basic-devel-build
-        path: U1_basic_*_devel.bin
-
     - uses: actions/upload-artifact@v4
       with:
         name: extended-devel-build
@@ -137,9 +121,7 @@ jobs:
         echo "${{ env.GIT_VERSION }}" > pr-info/version
         echo "${{ env.JOB_START }}" > pr-info/job_start
         echo "$(date +%s)" > pr-info/job_end
-        echo basic-build >> pr-info/artifacts
         echo extended-build >> pr-info/artifacts
-        echo basic-devel-build >> pr-info/artifacts
         echo extended-devel-build >> pr-info/artifacts
 
     - name: Upload PR info
diff --git a/docs/camera_support.md b/docs/camera_support.md
@@ -4,7 +4,6 @@ title: Camera Support
 
 # Camera Support
 
-**Available in: Extended firmware only**
 
 The extended firmware includes hardware-accelerated camera support with WebRTC streaming.
 
diff --git a/docs/cloud.md b/docs/cloud.md
@@ -4,7 +4,6 @@ title: Cloud Remote Access (Experimental)
 
 # Cloud Remote Access (Experimental)
 
-**Available in: Extended firmware only**
 
 Control your printer remotely using cloud-based remote access providers.
 
diff --git a/docs/data_persistence.md b/docs/data_persistence.md
@@ -4,8 +4,6 @@ title: Data Persistence
 
 # Data Persistence
 
-**Available in: Basic and Extended firmware**
-
 By default, Snapmaker firmware resets all system changes on reboot for stability.
 
 ## Enable System Persistence
diff --git a/docs/development.md b/docs/development.md
@@ -15,7 +15,6 @@ The custom firmware uses an overlay system to modify the base Snapmaker firmware
 
 Each overlay is self-contained and numbered to control application order. This modular approach makes it easy to:
 - Enable/disable features by including/excluding overlays
-- Maintain different firmware profiles (basic vs extended)
 - Add custom modifications without conflicts
 
 For external third-party components, see [Third-Party Integrations](design/third_party.md).
@@ -54,12 +53,6 @@ Build tools and download firmware:
 ./dev.sh make firmware
 ```
 
-Build basic firmware:
-
-```bash
-./dev.sh make build PROFILE=basic OUTPUT_FILE=firmware/U1_basic.bin
-```
-
 Build extended firmware:
 
 ```bash
@@ -74,26 +67,22 @@ Open a shell in the development environment:
 
 ## Profiles
 
-The build system supports two profiles:
-
-- `basic` - simple modifications not changing key components of the firmware
-- `extended` - extensive modifications changing key components of the firmware
+The build system supports the `extended` profile with extensive modifications to the firmware.
 
 ## Overlays
 
 Overlays are organized into categories based on their scope and build profile. Each overlay is numbered to indicate its application order within its category.
 
 ### Overlay Categories
 
-- **common/** - Core modifications applied to all firmware profiles (basic and extended)
-- **firmware-basic/** - Modifications specific to the basic firmware profile
+- **common/** - Core modifications applied to all firmware profiles
 - **firmware-extended/** - Modifications specific to the extended firmware profile
 - **devel/** - Development tools and utilities (only included with DEVEL=1 flag)
 - **staging/** - Disabled overlays kept for potential future use
 
 ## Build Options
 
-- `basic-devel` or `extended-devel` - Add development overlays from `overlays/devel/` to the selected profile
+- `extended-devel` - Add development overlays from `overlays/devel/`
   - e.g. `./dev.sh make build PROFILE=extended DEVEL=1`
 
 ### Devel Profile Features
@@ -232,7 +221,7 @@ PASSWORD=mypassword ./dev.sh ./scripts/dev/upgrade-firmware.sh root@192.168.1.10
 The project uses GitHub Actions for automated releases:
 
 1. Changes pushed to `main` trigger a pre-release build
-2. Both basic and extended firmwares are built
+2. Extended firmware is built
 3. Version is auto-incremented using `scripts/next_version.sh`
 4. Release artifacts are published to GitHub Releases
 
diff --git a/docs/firmware_config.md b/docs/firmware_config.md
@@ -4,7 +4,6 @@ title: Firmware Configuration
 
 # Firmware Configuration
 
-**Available in: Extended firmware**
 
 > **Note for users upgrading to v1.1.0:** The configuration file has been renamed from `extended.cfg` to `extended2.cfg`. During the first boot after upgrading a new `extended2.cfg` will be created with default settings. You will need to migrate your custom settings from `extended.cfg` to `extended2.cfg` manually or use `http://IP/firmware-config`
 
diff --git a/docs/index.md b/docs/index.md
@@ -37,21 +37,9 @@ For developers who want to build custom firmware, see [Building from Source](dev
 
 Join the [Snapmaker Discord](https://discord.com/invite/snapmaker-official-1086575708903571536) and visit the **#u1-printer** channel to connect with other users using the custom firmware, share experiences, and get help.
 
-## Firmware Variants
+## Features
 
-### Basic Firmware
-
-Stock firmware with SSH access and minimal debugging features:
-
-- [SSH Access](ssh_access.md) - Remote shell access with `root/snapmaker` and `lava/snapmaker`
-- [Firmware Configuration](firmware_config.md) - Web-based system administration and firmware upgrades
-- [Data Persistence](data_persistence.md) - Persistent storage configuration across firmware updates
-- USB Ethernet Adapters - Hot-plug support with automatic DHCP configuration
-- Fluidd web interface with basic camera support
-
-### Extended Firmware
-
-Heavily expanded firmware with extensive features and customization. Includes all basic features plus:
+Heavily expanded firmware with extensive features and customization:
 
 **Web & Configuration:**
 
diff --git a/docs/install.md b/docs/install.md
@@ -19,9 +19,6 @@ This guide covers installing custom firmware on your Snapmaker U1 3D printer.
 
 1. **Download Firmware**
    - Get the latest `.bin` file from the [Releases page](https://github.com/paxx12/SnapmakerU1/releases)
-   - Choose between Basic or Extended firmware:
-     - **Basic** - Stock firmware with SSH access and minimal debugging features
-     - **Extended** - Heavily expanded with hardware accelerated camera (WebRTC), RFID support, remote screen, monitoring, and extensive customization
 
 2. **Prepare USB Drive**
    - Format a USB drive as FAT32
diff --git a/docs/klipper_includes.md b/docs/klipper_includes.md
@@ -4,7 +4,6 @@ title: Klipper and Moonraker Custom Includes
 
 # Klipper and Moonraker Custom Includes
 
-**Available in: Extended firmware**
 
 Add custom Klipper and Moonraker configuration files through the Fluidd/Mainsail web interface.
 
diff --git a/docs/monitoring.md b/docs/monitoring.md
@@ -4,7 +4,6 @@ title: Monitoring
 
 # Monitoring
 
-**Available in: Extended firmware**
 
 Expose printer metrics for integration with monitoring systems like Grafana, Home Assistant, or DataDog. Track print progress, temperatures, and operational data.
 
diff --git a/docs/remote_screen.md b/docs/remote_screen.md
@@ -4,7 +4,6 @@ title: Remote Screen Access
 
 # Remote Screen Access
 
-**Available in: Extended firmware only**
 
 View and control your printer's touchscreen remotely from any web browser.
 
diff --git a/docs/rfid_support.md b/docs/rfid_support.md
@@ -4,12 +4,11 @@ title: RFID Filament Tag Support
 
 # RFID Filament Tag Support
 
-**Available in: All firmware (extended adds OpenSpool support)**
 
 The Snapmaker U1 automatically detects filament properties by reading RFID tags on spools.
 
 **Firmware Support:**
-- **Original & Basic:** Mifare Classic 1K with Snapmaker proprietary format
+- **Original:** Mifare Classic 1K with Snapmaker proprietary format
 - **Extended:** Adds NTAG215/216 support with OpenSpool format
 
 ## Supported Formats
@@ -122,7 +121,6 @@ Use the **NFC Tools** app (iOS/Android) to inspect tags:
 
 ## Alternative Detection Systems
 
-**Available in: Extended firmware only**
 
 The OpenRFID detection system is an alternative to Snapmaker's built-in filament tag detection, based on the [OpenRFID](https://github.com/suchmememanyskill/OpenRFID) project. It adds support for tagged spools from multiple manufacturers.
 
@@ -182,5 +180,5 @@ After editing, restart the printer.
 - Use NTAG tags with OpenSpool format instead
 
 **NTAG tags only work on extended firmware:**
-- Basic and original firmware only support Mifare Classic 1K with Snapmaker proprietary format
+- Original firmware only supports Mifare Classic 1K with Snapmaker proprietary format
 - Extended firmware adds NTAG215/216 support
diff --git a/docs/vpn.md b/docs/vpn.md
@@ -4,8 +4,6 @@ title: VPN Remote Access (Experimental)
 
 # VPN Remote Access (Experimental)
 
-**Available in: Extended firmware only**
-
 Control your printer remotely using a VPN provider.
 
 > **Note**: VPN providers are downloaded on-demand when enabled by the user. See [third-party integration design](design/third_party.md) for details on how external components are managed.
diff --git a/overlays/firmware-basic/01-enable-native-camera-fluidd/patches/04-enable-moonraker-camera.patch b/overlays/firmware-basic/01-enable-native-camera-fluidd/patches/04-enable-moonraker-camera.patch
diff --git a/overlays/firmware-basic/01-enable-native-camera-fluidd/root/etc/init.d/S99fluidd_camera b/overlays/firmware-basic/01-enable-native-camera-fluidd/root/etc/init.d/S99fluidd_camera

Original file line number	Diff line number	Diff line change
`@@ -4,7 +4,6 @@ title: Camera Support`
`4`	`4`
`5`	`5`	`# Camera Support`
`6`	`6`
`7`		`-Available in: Extended firmware only`
`8`	`7`
`9`	`8`	`The extended firmware includes hardware-accelerated camera support with WebRTC streaming.`
`10`	`9`
Original file line number	Diff line number	Diff line change
`@@ -4,7 +4,6 @@ title: Cloud Remote Access (Experimental)`
`4`	`4`
`5`	`5`	`# Cloud Remote Access (Experimental)`
`6`	`6`
`7`		`-Available in: Extended firmware only`
`8`	`7`
`9`	`8`	`Control your printer remotely using cloud-based remote access providers.`
`10`	`9`
Original file line number	Diff line number	Diff line change
`@@ -4,7 +4,6 @@ title: Firmware Configuration`
`4`	`4`
`5`	`5`	`# Firmware Configuration`
`6`	`6`
`7`		`-Available in: Extended firmware`
`8`	`7`
`9`	`8`	> Note for users upgrading to v1.1.0: The configuration file has been renamed from `extended.cfg` to `extended2.cfg`. During the first boot after upgrading a new `extended2.cfg` will be created with default settings. You will need to migrate your custom settings from `extended.cfg` to `extended2.cfg` manually or use `http://IP/firmware-config`
`10`	`9`
Original file line number	Diff line number	Diff line change
`@@ -4,7 +4,6 @@ title: Klipper and Moonraker Custom Includes`
`4`	`4`
`5`	`5`	`# Klipper and Moonraker Custom Includes`
`6`	`6`
`7`		`-Available in: Extended firmware`
`8`	`7`
`9`	`8`	`Add custom Klipper and Moonraker configuration files through the Fluidd/Mainsail web interface.`
`10`	`9`