I spent the past two months building a a flock detecting app, and I want to validate it and make sure it passes mustard for stability and detections. I'm looking for some beta testers with a Cardputer Adv who would be willing to test for a couple of weeks and provide feedback.

https://docs.google.com/forms/d/e/1FAIpQLSfz659YKAjOyWrIjDiOtE0WjXWej5nbaYPZ6tfx2nWoCId2Ng/viewform?usp=header

I'd love to get 10 people to test this to start, and I'll subsequently update this post (and send those people the bin file). I'll also be deleting these emails once we get done with this (and will update this post to tell you when I have my 10 so no one else fills it out).

Latest Changelog -> 2.6.8:

• Increased Gamestation Partitions sizes.
• Added option to erase App Partition
• Added option to always boot into Launcher
• Added "APP" menu item to reboot into the last installed firmware
• Enhanced NVS partition and partition schemes for UiFlow2
• Fix M5Stack Tab5 Wifi scan and WebUI in AP mode.
• New Device: Lilygo T-Watch-S3
• New Device: Lilygo T-Watch-Ultra
• New Device: Lilygo E-Paper S3 Pro H752-x .

Support the project

Website and Flasher Buy me a Coffee BTC: bc1q6m5sks6vhl38g8xyuzuazdv3wffsk58ffxk8rg

I’ve been working on custom firmware for StackChan.

The idea is to give an LLM a small, funny physical body.

I don’t want to move away from “cute face connected to an LLM”. That part is exactly what I like. I just want the cute face to have memory, skills, tools, smart home control, and enough context to feel less like a fresh chatbot session every time.

The main conversation runs through Gemini Live. StackChan handles the body: face, speaker, microphone, servos, camera, touch/tap behavior, and local timing. Around that, I added memory, skills, tools, Home Assistant control, and local scheduled tasks that the model can use during the conversation.

Some of the parts I’m most happy with:

• Persistent memory and recent context. StackChan can remember useful information across conversations and keep recent dialogue context, so I do not have to remind it what we talked about an hour ago.
• Compact memory summaries. Longer interactions can be summarized into a more compact form instead of dumping the entire chat history into every prompt.
• Memory search / lightweight RAG-like recall. The robot can search its own memory when it needs something, rather than putting every stored fact into the model context all the time.
• Separate sensitive storage. Some information can live in a separate storage/tool layer and only be opened when needed, instead of being constantly sent to the model.
• Learnable skills. I can teach StackChan new routines as instruction sets. It can store them, search for them later, and reuse them when relevant. Skills can also include tool usage, including camera actions.
• Tool use during live conversation. The LLM can call tools exposed through the firmware/gateway: memory, skills, camera, gestures, Home Assistant, search, and other robot-side actions.
• Home Assistant control. StackChan can see what devices are available in Home Assistant and control them by voice: turn lights or switches on/off, check device state, and use smart home actions as part of a conversation.
• Local timers and scheduled tasks. I added a scheduling system where the robot can create reminders/timers/tasks during conversation. These are stored and checked on the robot side, so it can trigger something later instead of just answering once and forgetting.
• Camera and look-around behavior. StackChan can use its camera with different look directions instead of just taking one static picture. This makes camera-based skills feel more like the robot is actually looking around.
• Optional local Hermes integration. It can talk to my local Hermes assistant on the same network, but that is optional. I do not want the robot to depend on outsourcing everything to a bigger assistant.

A lot of the work has been less about “can I connect an LLM to a robot?” and more about making the loop feel usable on a tiny physical device.

Some problems I ran into:

• audio feedback, where the robot hears itself speaking
• microphone gain and noise tuning
• keeping voice, sound effects, and listening state from stepping on each other
• slow tool calls during a live conversation
• limited RAM and timing issues on the ESP32 side
• camera initialization/release stability
• deciding what should run on the robot, what should run through the gateway, and what should stay local/private
• making memory useful without turning every prompt into a giant context dump
• making scheduled tasks reliable without relying on an external server for every reminder

It is still experimental, but it is already fun to use) I can talk to StackChan naturally, teach it little routines, have it remember things, control smart home devices, create timers, ask it to use tools, make it look around with the camera, and let it pull relevant context back into the conversation when needed.

I'm struggling to mount/write to the SDCard, can anyone help?

PaperWeb v1.3.0 - text browser for M5Cardputer

It's still just a text browser. Because why not.
Changes since v1.2.0:
- Heavy pages (Wikipedia) load and scroll faster.
- Removed script buffer, reduced memory junk.
- Only visible lines are drawn now.
- Search still uses Google (other engines block ESP32).

All previous features: offline saving to SD, file manager, bookmarks, screenshots, zoom.

Install: download .bin from GitHub releases, flash with M5Burner, insert SD card, connect WiFi with TAB.

Full controls and source:
https://github.com/Artem76228/PaperWeb

I really hope that's true, a Tab5 with Raspberry Pi zero CMO comming one day.

WARNING! After updating, you cant downgrade to prior versions without data loss. This update moves all M5Gotchi related files into its own folder, also encrypting some config values. If you decided to downgrade, all your data will be lost forever.

Changes:

• Completely changed the implementation of auto mode - it is now 200% more efficient compared to v0.6
• Keyboard now works in auto mode and allows to see exactly what the M5Gotchi is doing in auto mode and state of attack in new "Debug view" option in menu as well as disable it at any time
• Added auto screen dim
• Changed the way in which wpa-sec results are displayed
• Added new personality options and removed old ones
• Improved auto mode + wardrive
• Some changes to wardriver and its logic
• Fix: Fixed bug that caused wardriving files to not count in wigle.net stats
• All captured handshakes will now be converted to hashcat format upon capture. Old handshakes or from different firmware's can be converted by using new converter tool from tools menu
• Added ability to crack handshakes by wordlist brute force
• Added ability to check if any .pcap file has a valid handshake
• PMKID grabber is now not experimental and can be used by everyone
• Achievements menu - now you can grind for them and even try to unlock some secret ones
• StickS3: Added ability to customize the button A hold on home screen - you can choose to either dim your screen or toggle auto mode
• New icons for grid menu
• All M5Gotchi related files will be now stored in "M5Gotchi" folder in sd card or littleFS
• Added [REDACTED]
• Fix: Fixed web ui file upload to folders
• Small ui changes and hint additions
• Overall performance improvements

Update from ui, Github or M5Burner, or via attached files. (Also if you're on latest non-beta version you can't update from ui as github cert expired and I couldn't update them until now :/ )

If you enjoy my work, please consider donating: https://ko-fi.com/Devsur

Msx ADV Emulators v0.6.114 for M5Stack Cardputer: MSX/MSX2 support, ROM/CAS/DSK, save states, VDP tuning.

Full-flash release

Hi everyone,

After three weeks of micro optimization, I've just released Msx ADV Emulators v0.6.114 for the M5Stack Cardputer.

The MSX2 emulation work was only possible thanks to the suggestions & encouragement from u/geo_tp. Huge thanks for helping push this beyond the original MSX1-focused scope.

This is an MSX-focused firmware build with support for both MSX1 and MSX2, running on the ESP32-S3 without PSRAM. It supports launching:

• .rom cartridges
• .cas cassette images
• .dsk disk images

Main Features

• MSX1/MSX2 runtime
• MSX2 BIOS cache stored in a dedicated flash partition
• C-BIOS fallback for MSX1
• ROM, CAS, and DSK workflows
• CAS menu with RUN"CAS:", BLOAD"CAS:",R, and tape change
• DSK change support
• Save states with selectable slots
• Quick save/load shortcuts
• Runtime config menu
• Configurable controls
• Virtual key picker
• Internal LCD and external SPI TFT support
• Internal display optimized for 60 fps
• External TFT support, with some external speed sacrificed to keep the internal display fast
• View modes: CROP, WIDE, WIDE+, 1:1, FAST, FAST+
• Internal zoom, manual pan, and zoom follow
• Performance tuning presets: NORMAL, FAST, SCLINE, CUSTOM
• VDP tuning options for MSX2 rendering
• Virtual SCC/SCC-I support with SCC audio controls
• Region selection: Auto, World, Japan

Known Limitations

• MSX-AUDIO is not emulated yet
• FM audio in general is not emulated yet
• FM-PAC/YM2413 synthesis is disabled in this build
• This is focused on practical Cardputer playability, not perfect desktop-class MSX emulation

Please carefully read the Readme for detailed instructions on how to use and install Bioses.

Download

Full-flash release image:

https://github.com/mariovirgili/CardputerGBC-Dual/releases/download/Msx_v0.6/MsxADV-Emulators-v0.6.114-r476-8c267f6-m5stack-stamps3-max-spiffs-msx2-flash-full-flash.bin

GitHub branch: https://github.com/mariovirgili/CardputerGBC-Dual/tree/MsxOnly

Vibe coded using Codex 5.5, Gemini pro 3.1 and minimally Opus 4.7.

I already have my setup running on a Pi Zero 2 W and a custom firmware on Cardputer ADV that controls it.

So I decided to merge everything into a single device.

I designed and 3D printed an extension piece that sits between the Cardputer and its original back cover, I want to keep the stock shell on the outside for a cleaner finish instead of a fully printed case.

Current plan

• Fit Raspberry Pi Zero 2 W + battery + power module inside the extension
• Keep Cardputer fully functional (screen/keyboard/UI)
• Use Cardputer as a terminal/controller for the Pi

Power architecture

• 1x LiPo battery (limited to ~80x30x6mm -> probably ~1800–3000mAh)
• 1x power module (IP5306 or similar)

Wiring:

Battery → power module → 5V rail
                        ├── Pi (direct 5V)
                        └── Cardputer (5V0 pin)

• Cardputer internal battery stays
• External 5V acts like “always plugged in”

Communication

UART via Grove:

Cardputer TX → Pi RX (GPIO15 / pin 10)
Cardputer RX → Pi TX (GPIO14 / pin 8)
GND shared

Hardware mods

Raspberry Pi

• Remove bulky connectors (USB + HDMI) to save space

• Power Pi via test pads:

  5V → PP1 GND → PP6

(no USB needed at all)

Cardputer

• Inject 5V internally:

  5V → 5V0 (or 5V1) pin GND → GND

• Grove used only for UART

Goal

• One device
• One charging port
• No external cables
• Instant-on terminal for my Pi control center

Next steps

• Find largest LiPo that fits (80x30x6mm constraint)
• Pick stable 5V boost/charge module (IP5306?)
• Finalize internal wiring layout
• Clean enclosure routing (battery + Pi stacking)

If anyone has:

• better power module suggestions (compact, stable under Pi load)
• experience running Pi Zero from small LiPo setups
• cleaner way to inject power into Cardputer

I’d love feedback before I lock the design.

p.s. once cardputer zero comes out I will use this as a backup device

Hi, I’m Bobby, I’m 14 and am creating my own firmware called Killer Adv. it’s currently in beta (v0.2) and not really usable. I’m working really hard on this and putting all the time I have into it, so I hope you all like it. For now, there’s isn’t a ton to do with it. But I’m implementing more features ASAP. Thanks so much guys!
(Not yet released until I can be bothered compiling/merging into one .bin lol)

I think I will call it a project here (when it comes to hardware)
I’ve been messing around with the Cardputer (v1 and ADV) for some time and I knew and I felt like it could be something more practical, and since I had lot of stuff going on my raspberry's I decided to turn ADV into control device for pi and put all together and to push it a bit and see where it goes.

I made a 3D printed adapter so everything sits inside the case without completely ruining the original look and to be reversable at any point. It’s not perfect (fit could be tighter, screws are a bit off), but it holds together well and actually looks like a single device now.

The Pi is running a small system I’ve been building:
https://github.com/rimedag/VaultPi-Control-Center

It’s basically a lightweight control center where I can run scripts, trigger things, manage small workflows, repo's, etc. Running it inside the browser is much nicer and better looking but with custom cardputer firmware I can access it via cardputer, It’s very terminal-first, nothing fancy visually (on cardputer), but it fits the screen and the whole concept pretty well.

I also added a few things that made it feel way more “real” than I expected.

For example, I put a w3m browser on the Pi and integrated it into the firmware, so you can actually browse the internet from this thing. It’s obviously minimal, but it works. There’s also a terminal exposed so you can directly access the Pi, not just go through menus.

The GO button on top is now used for lock/unlock, and I added an optional PIN if you want some basic safety. There’s also a small thing like keeping the screen on while charging, which sounds minor but makes a big difference in usability (When it sits on my desk and I can with glance of my eye see if my websites and services are running or if anything is down).

Communication between the Cardputer and the Pi is currently pretty simple, they talk over the same network. The control center listens on a port and the Cardputer connects to it with a password. It works reliably enough for now.

I did think about going lower level. Those two unused data wires (from grove) are basically just sitting there and could be wired directly to the Pi’s GPIO, which would allow full control even without network. That was the original idea.

But I stopped myself there.

I know how that goes, one more layer, then another, then suddenly it’s a never-ending project. So I left that as a “maybe later” and kept this version focused and working.

Power-wise, same story. I originally wanted to go all-in with a second battery and extra modules to properly power the Pi. I even got advice to do that. But again, I simplified it.

Right now I’m powering the Pi through Grove. For normal use it works fine. It’s not meant for heavy loads, but for what this is, it’s stable enough. I’ll test battery life properly and share results once I have something real.

Where it stands right now is somewhere between prototype and usable device. It works, I actually use it, but it’s not polished. Things that could be better:

• smaller screws
• tighter 3D print
• cleaner internal layout
• Additional battery and modules for having pi with its own powersupply (but then it needs switch bla bla bla too much hustle + not intuitive)

Firmware also isn’t “clean” yet. It works, but there are hiccups. I’ll make that repo public once I fix the obvious stuff. The Pi side is already up if anyone wants to try it.

I had plans to go much deeper with this, more integration, maybe push it towards a small OS-like system, but I intentionally stopped before it turns into something I never finish.

So this is it for now. Not perfect, but real and working.

Lets call it a v1

Curious what people think, if you are inpatient to get your hands on CP Zero this might be worth a try, even having raspberry separated from cardputer is good idea, since they have to be on the same network raspberry could sit somewhere in the house while you access it and manipulate it via cardputer

For those wanting to have raspberry on keychain I have modified 3d print in github repo beside the app

Oh I almost forgot, 3d model of this adapter can be found here
https://www.printables.com/model/1711895-cardputer-adv-adapter
(with ender 3v3 and basic PLA I found it best when printing on 75% speed, nozzle temp 212 bed temp 63)

Firmware for cardputer can be found here
https://github.com/rimedag/Vaultpi-Cardputer

But as of now it is buggy and probably not gonna work properly (there is source code and firmware builded for you to put on SD card and install)
I am giving link just if you want to bookmark it or save for later

Lets have fun

Evil-Cardputer v1.5.3 - TagTinker ESL Integration

v1.5.3 brings full Pricer Electronic Shelf Label control via infrared! Push images, text and commands to store price tags from your Cardputer.

---

TagTinker ESL - IR Price Tag Control

Full Pricer ESL IR protocol integration (PP4, 1.255MHz, GPIO bit-bang):

• Push text & images to individual tags or ALL saved tags at once (~10s for 7 tags)
• 8 fonts, 38 tag models supported, tag management on SD
• Full Web UI at /tt with Evil theme - image prep (5 dithers, crop, zoom, gamma, edge detect), text with live preview, LED control, 8 online plugins (Crypto, Weather, ISS, GitHub...), barcode scanner (Quagga JS offline), NFC decoder
• NFC tag decoder — paste esl.nu URL to get barcode + PLID instantly

---

Serial Commands

tag textall message    — push to ALL tags at once
tag text BC msg        — push to one tag
tag led BC [DUR]       — targeted LED
tag blink/debug/page N — broadcast commands
tag list               — saved tags
tag rawsend N HH HH.. — raw IR frame

---

Setup

Copy webui.html + quagga.min.js and BMP images to /evil/esl/ on SD card.

Binary: Evil-Cardputer-v1-5-3.bin

Already on M5Burner!

---

> Use only on devices you own or have authorization to test.

A big thanks to u/i12bp8 for the work on the Flipper app!

i got the cc1101 and the nrf24 module is it worth it?

if there's not already a good discord server for the stick plus 2 should I make one?

I think I’ve reinvented the keyboard. At least, I haven’t seen anyone else do anything like this.
The B button is used for erasing, and the power button switches between CAPS mode.

And now you can switch between the keyboard and the air mouse without losing the connection, allowing for almost full control of your PC.

A Bluetooth connection indicator has also been added, which will remain visible as long as your stick is connected to a device.

List of changes:

• bluetooth scan
• bluetooth device info + device finder
• bluetooth keyboard with gyro mode support
• bluetooth keyboard gyro mode setting
• bluetooth indicator in status bar

https://github.com/Dlazder/m5stick_crystal_firmware

what should i do when it gets here like what firmwares should i add