DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build and update the robot firmware from source with Groki Bot

Compile the CoreS3 firmware yourself and push updates over Wi-Fi with on-device OTA.

Who it is forA firmware developer or maker who wants to change the robot's behavior, not only use the default build.

The problemUsing the prebuilt firmware limits what you can change, and reflashing by cable every time slows down testing.

The outcomeYou have a firmware build from this repository, flashed once and then updated over Wi-Fi through on-device OTA.

What you need first

  • M5Stack CoreS3 with a Stack-chan base
  • A Mac for the computer-side gateway (native voice is macOS)
  • Desktop Chrome or Edge for the web flasher
  • The Grok Bot desktop app, signed in on the Mac
  • A Wi-Fi network for the robot

Steps

  1. Clone the repository with git clone https://github.com/JosssphZhou/groki-bot.git and open it. (inferred, check the README)
  2. Read docs/build.md for the toolchain and build steps, then build the firmware from source.
  3. Flash the first build with the web flasher in desktop Chrome or Edge, or as described in docs/build.md.
  4. Connect the robot to Wi-Fi and use the on-device OTA update to deploy each later build.
  5. Run the robot through one expression cycle to confirm the new firmware works.

Prompt for your agent

In the groki-bot repo, follow docs/build.md to build the CoreS3 firmware from source and list the output artifacts. Verify that the build finishes without errors before any flash step.

Caveat. The README points to docs/build.md for the source build, so the exact toolchain requirements live in that file and were not summarized here.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page