Time to teach your buddy some new tricks! Flash the latest firmware directly from your browser.
Hold Your Critters! 🐴 Before clicking Flash, please read all instructions for your system below (use the buttons!). Important steps ensure a smooth pupdate for your pal.
Note: This tool uses WebUSB, which requires either Google Chrome or Chromium as a web browser. WebUSB is not supported on iOS devices (iPhone/iPad).
Get your Critter into Bootloader mode (Step 1 below!) & follow the prompts here!
Initializing...
Version: Loading...
Date: Loading...
Based on commit: ...
Super Important! Your μCritter needs to be in its special update mode. Pick ONE way to get there. You'll know it worked when the screen shows:
~CAT BOOTLOADER MODE~
Connect to a computer over USB
to download new firmware.
Power → Sleep. Let it snooze, then use the "Sleepy Wake-up" method above.Bootloader screen showing? Awesome! Now plug your Critter into your computer/phone with its USB cable. On to Step 2!
Why the refreshes later? Your Critter uses a super-safe two-stage update process (called MCUBOOT). Your browser talks to both stages, and sometimes needs a page refresh to switch between them. Just follow the messages next to the big Flash button!
Mac pals, just follow the messages next to the Flash button over there 👈. It's a simple connect-refresh-connect routine!
MCUBOOT and click Connect.
CAT PROTOTYPE? Whoops! Your Critter isn't in Bootloader mode. Go back to Step 1 and try again!MCUBOOT again.Did it work? 🎉 Keep an eye on the progress log. "Pupdate Complete!" means success! Your Critter will restart with its new tricks.
Howdy, Windows user! Because Windows needs a little extra help recognizing your Critter during the update, we need to use a tool called Zadig to install the right drivers and perform a specific restart sequence. This is a one-time setup per computer. Please follow these steps exactly!
Options -> check ✅ List All Devices.MCUBOOT from the dropdown list (it should have USB ID 2FE3 0100).
Interface Check: Zadig usually shows multiple "Interfaces" for MCUBOOT in this first stage (e.g., Interface 0, Interface 2). You need to select the one used for firmware updates, which is Interface 2. Make sure the entry you select in the dropdown specifically mentions Interface 2.
Do NOT change the driver for Interface 0 (the Serial/CDC interface).
🐾 Seeing CAT PROTOTYPE instead of MCUBOOT? Whoops! Wrong mode. Go back to Step 1, get the right screen, then re-open Zadig.
WinUSB for the selected Interface 2.MCUBOOT and click the Connect button in the pop-up.Options -> check ✅ List All Devices again.MCUBOOT again from the dropdown.
MCUBOOT device (the USB ID might be 2FE3 FFFF or stay 2FE3 0100). Select this single entry.WinUSB is selected next to the green arrow.MCUBOOT in the browser pop-up when asked. The app will automatically figure out if it's Stage 1 or Stage 2 this time.MCUBOOT if asked).MCUBOOT if asked).Watch the progress log. "Pupdate Complete!" = Success! 🎉 Your Critter will restart automatically.
Hey Linux friend! We need to give your browser permission to chat with the Critter. This is usually a quick, one-time setup per computer using a udev rule.
You only need to do this once per computer.
sudo nano /etc/udev/rules.d/51-mcuboot.rulesSUBSYSTEM=="usb", ATTR{idVendor}=="2fe3", ATTR{idProduct}=="0100", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2fe3", ATTR{idProduct}=="ffff", MODE="0666", GROUP="plugdev"
groups and press Enter. Check if plugdev is listed.plugdev was NOT listed, run: sudo usermod -aG plugdev $USER sudo udevadm control --reload-rules && sudo udevadm triggerplugdev group in step 6, you MUST log out completely from your Linux session and log back in for the group change to take effect! Restarting the browser is not enough.This single command does the same thing as the manual steps (creates file, adds user, reloads rules). Copy/paste into your terminal:
echo -e 'SUBSYSTEM=="usb", ATTR{idVendor}=="2fe3", ATTR{idProduct}=="0100", MODE="0666", GROUP="plugdev"\nSUBSYSTEM=="usb", ATTR{idVendor}=="2fe3", ATTR{idProduct}=="ffff", MODE="0666", GROUP="plugdev"' | sudo tee /etc/udev/rules.d/51-mcuboot.rules > /dev/null && sudo usermod -aG plugdev $USER && sudo udevadm control --reload-rules && sudo udevadm trigger && echo "Rule created/updated. Log out/in if you weren't in plugdev group before running this."
Log Out Required? If this command added you to the plugdev group (check with groups), you MUST log out completely and log back in for permissions to work correctly!
Access Denied Error with Chromium from Snap/Flatpak If you installed Chromium/Chrome via Snap (common on Ubuntu), you may receive an Access Denied error. You might need to grant it explicit USB access by running: sudo snap connect chromium:raw-usb
(Replace `chromium` if needed for Chrome). Restart the browser afterwards. If you use Flatpak, check its permissions (e.g., using Flatseal). Sometimes, installing Chrome directly from Google (as a `.deb` package) avoids these sandboxing issues.
MCUBOOT and click Connect.
CAT PROTOTYPE? Whoops! Bootloader mode needed (Step 1).MCUBOOT if prompted.MCUBOOT if prompted. Flashing starts!Watch the progress log. "Pupdate Complete!" = Success! 🎉 Your Critter will reboot.
Hey Android adventurer! Let's get your phone ready to give your Critter its Pupdate.
Ready? Using Chrome, follow the messages next to the Flash button over there 👈:
MCUBOOT and tap Connect.
CAT PROTOTYPE? Whoops! Your Critter isn't in Bootloader mode. Go back to Step 1 and try again!MCUBOOT if the pop-up appears.Did it work? 🎉 Keep an eye on the progress log. "Pupdate Complete!" means your Critter is ready to reboot and show off!