1 × M5Stack Core2 (v1.0)
Requiredboard
Main board or device for this build.
Build: M5Stack Core2 (v1.0)
About 30-45 minutes · needs a Mac or PC and a USB-C data cable · some Terminal, or let your agent do it
Intermediate · extra stepsBack up the 16 MB flash first, flash at 230400 baud, and check it's a v1.0.A working Muse Gadgets: ESP32 Device SDK (Full UI) build on M5Stack Core2 (v1.0), paired to your Muse account and ready for first prompts.
Screen and voice
1
Get the parts
You need the board and any build-specific accessories before flashing or pairing.
Find on ebay.com
1 × USB-C data cable
Requiredpart
Must carry data, not just charge. Most flashing problems are charge-only cables. This Adafruit cable is USB-C on both ends with all data pins connected ($9.95 on 2026-10-05). If your computer has USB-A ports, the Seeed USB-C to USB-A cable works too.
1 × USB-C power adapter (5 V / 2 A or more)
Optionalpart
Optional. Runs the gadget from a wall outlet instead of your computer. A phone charger that supplies 5 V / 2 A or more works.
Hackshop never buys for you. Links open the store.
2
Get your Muse SDK token
Muse gadgets pair with your account by using a private SDK token.
Create a token at gadgets.muse.ai > Account > SDK tokens (https://gadgets.muse.ai/settings/sdk-tokens). It starts with mgst_. For this ESP32 build, set CONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN" in build-muse-m5stack-core2/sdkconfig after the board build command has created that file, then run the build command again. idf.py menuconfig > ESP32 Device SDK > Muse Gadgets SDK token is the interactive alternative. Never commit the real token or paste it anywhere public.
3
Flash the firmware
The board needs the Muse ESP32 firmware configured with your SDK token.
Read this first: flashing this board
- Port: Its USB-UART bridge is a CP2104 on early units and a CH9102F on later ones; tools/muse/board.sh flash core2 uses 230400 baud, which both take.
- Keep any esptool command you run by hand at -b 230400.
- Before the first flash, back up the full 16 MB flash:
python -m esptool --chip esp32 -p PORT -b 230400 read-flash 0 0x1000000 core2.bin. Keepcore2.binsafe, outside Git. - To go back, write the backup with the same chip, port and baud:
python -m esptool --chip esp32 -p PORT -b 230400 write-flash 0 core2.bin.
Source: https://github.com/facebookincubator/muse-gadget-sdk/blob/main/esp32/devices/README.md
Let your agent do it
Give your coding agent the build brief at https://www.hackshop.dev/build/m5stack-core2-v1-0/build.md. Tell it to keep the token private, use mgst_YOUR_TOKEN as the placeholder, and find the serial port before flashing. On macOS it should run ls /dev/cu.usbmodem* /dev/cu.usbserial*; on Linux, ls /dev/ttyACM* /dev/ttyUSB*; on Windows, use Device Manager to find the COM port, then run commands in the ESP-IDF shell. Before the first flash, it must back up the full 16 MB flash.
Do it yourself
Install ESP-IDF v6.0.1 and only the esp32 target for this board. Muse's ESP32 README verifies macOS and Linux. Windows is not documented by the Muse SDK; if you use it, install ESP-IDF v6.0.1 with Espressif's Windows installer and run commands in the ESP-IDF shell. Clone the Muse Gadget SDK, run tools/muse/board.sh build core2 once to create build-muse-m5stack-core2/sdkconfig, set CONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN" in that file, run tools/muse/board.sh build core2 again, then flash. If flashing cannot connect, hold BOOT, tap RESET, then release BOOT.
git clone -b v6.0.1 --recursive https://github.com/espressif/esp-idf.git ~/esp/esp-idf-v6
~/esp/esp-idf-v6/install.sh esp32
. ~/esp/esp-idf-v6/export.sh
git clone https://github.com/facebookincubator/muse-gadget-sdk
cd muse-gadget-sdk/esp32
tools/muse/board.sh build core2
printf '\nCONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN"\n' >> build-muse-m5stack-core2/sdkconfig
tools/muse/board.sh build core2
ls /dev/cu.usbmodem* /dev/cu.usbserial* 2>/dev/null || ls /dev/ttyACM* /dev/ttyUSB* 2>/dev/null
python -m esptool --chip esp32 -p PORT -b 230400 read-flash 0 0x1000000 core2.bin
tools/muse/board.sh flash core2 PORT4
Pair it with the Muse app
Pairing links the freshly flashed board to your Muse account.
In the Muse app, turn on Settings > Devices > Developer mode, then Settings > Devices > Add Device (+). Pick MuseGadget-XXXXXX and press the middle touch zone when the screen or edge status breathes blue. Green means connected. Status meanings: orange = ready for setup, blue breathing = press the button, blue = joining Wi-Fi and connecting, green = connected, yellow blinking = reconnecting, purple = unpaired, red blinking = error. Hold the button for 5 seconds to reset pairing.
5
Put it together
A physical agent body needs to sit safely, keep the cable clear and leave controls reachable.
Put the board in its stand, case or a stable spot on the desk. Route the cable through the slot or open edge, power it, and check that the buttons and display are reachable.
6
Try it
A first prompt proves the device is paired, reachable, and useful for the project.
“(Hold the middle touch zone) What's on my calendar tomorrow?”“Show me the image you just found.”
Hand it to your agent
# Build: M5Stack Core2 (v1.0) as a Muse gadget
Difficulty: Intermediate (extra steps). Back up the 16 MB flash first, flash at 230400 baud, and check it's a v1.0.
## Goal
A working Muse Gadgets: ESP32 Device SDK (Full UI) build on M5Stack Core2 (v1.0), paired to your Muse account and ready for first prompts.
## Warnings (read before flashing)
- M5Stack Core2: only v1.0 (AXP192) is supported; v1.1 (AXP2101) isn't. Check the back sticker or PCB, and back up the 16 MB flash before the first flash.
## Hardware
- [M5Stack Core2 (v1.0)](https://www.ebay.com/sch/i.html?_nkw=M5Stack%20Core2%20(v1.0)) x1 (required, board): Main board or device for this build.
- [USB-C data cable](https://www.adafruit.com/product/4199) x1 (required, part): Must carry data, not just charge. Most flashing problems are charge-only cables. This Adafruit cable is USB-C on both ends with all data pins connected ($9.95 on 2026-10-05). If your computer has USB-A ports, the Seeed USB-C to USB-A cable works too.Caveats + terms
Personal, non-commercial use with your own Muse account. A token can be linked to at most 50 devices. You may not put it in any device you sell, advertise, or list publicly or in a marketplace or app store; other distribution needs Meta's written permission. Provided as-is; Meta can change, withdraw or revoke access at any time. Read terms.
- The home-network tunnel lets Muse reach devices on your LAN that expose a local HTTP API. Treat it like giving the agent a foothold on your network.
- Pairing has no manufacturer verification and can't prevent an active man-in-the-middle attack.
- Builds are signed with the included development key and never enable Secure Boot. Enable NVS encryption (CONFIG_HOMEHUB_NVS_ENCRYPTION).
- Custom ESP32 commands are not a documented API yet: the command set (display.draw_url, sensors.read, camera.capture, ...) is hardcoded in main/app.c.