App Manager¶
Manage RP2350 apps on your TBD-16 directly from the browser. Install apps to the Pico SD card, choose a boot mode, and flash firmware — no card reader or terminal commands needed.
Browse the App Catalog for all available apps.
How it Works
Step 1 — Mount SD Card: Flash the USB Mass Storage firmware to the RP2350 so the Pico SD card appears as a removable drive.
Step 2 — Manage Apps:
Open the mounted SD card, browse the app catalog, and install
or remove apps. Apps are stored in the tbd-apps/ folder.
Step 3 — Choose Boot Mode: Eject the SD card, put the RP2350 back in BOOTSEL mode, and flash the firmware you want:
Bootloader — Boot menu that lets you switch between installed apps using the front-panel controls.
Groovebox Only — Flash the groovebox directly for single-app operation (no boot menu).
Flash Nuke — Erase the RP2350 flash completely. Use this to factory-reset or recover from a broken state.
Hardware setup:
Back USB-C Port #2 (closest to the edge) → RP2350 BOOTSEL + SD card
Back USB-C Port #1 → power (keep connected)
Browser: Chrome, Edge or Opera required (WebUSB + File System Access).
Time: 5–10 minutes
Put the RP2350 in BOOTSEL mode (hold BOOTSEL + press RESET on the front panel), then click Connect.
Click Open SD Card to select the mounted drive, then install or remove apps.
Then put the RP2350 in BOOTSEL mode again (hold BOOTSEL + press RESET).
🔀 Boot Menu (Bootloader)
Flash the custom bootloader. On startup, use the front-panel controls to choose which app to run from the SD card. Recommended when you have multiple apps installed.
🎹 Groovebox Only
Flash the groovebox directly — single-app mode with no boot menu. The device boots straight into the sequencer.
💥 Factory Reset (Flash Nuke)
Erase the RP2350 flash completely. Use this to recover from a broken state or remove the bootloader. After nuking, flash the groovebox or bootloader to restore operation.
✓ App Manager Complete
Your TBD-16 RP2350 apps are set up.
Disconnect USB cables, wait 3 seconds, then reconnect via back Port #1.
Having trouble? See the Troubleshooting page.