mirror of https://github.com/m5stack/ESP-Claw.git synced 2026-05-20 11:51:49 -07:00

Files

T

History

imliubo fee405adf5 boards: add M5Stack CoreS3 board support

Add a complete board package for the M5Stack CoreS3 under
application/basic_demo/boards/m5stack_cores3/, so basic_demo can be
built and flashed on CoreS3 with:

  idf.py gen-bmgr-config -c ./boards -b m5stack_cores3
  idf.py build flash monitor

Highlights:

* board_info.yaml / board_peripherals.yaml / board_devices.yaml
  describe the CoreS3 hardware for esp_board_manager:
    - I2C0 (SDA=12, SCL=11) for AXP2101, AW9523B, AW88298, ES7210, FT5x06
    - I2S0 48 kHz stereo (MCLK=0, BCLK=34, WS=33, DOUT=13, DIN=14)
    - SPI2 (MOSI=37, MISO=35, SCLK=36) for the ILI9341 LCD
    - GPIO46 for AW88298 PA enable
    - ILI9341 SPI panel (320x240, BGR, big-endian, color inverted)
    - FT5x06 I2C touch
    - AW9523B GPIO expander with the output mask required by CoreS3
      (incl. pin 1 BUS_EN and pin 15 BOOST_EN for the Grove 5V rail)

* power_manager.[ch]: custom AXP2101 power manager that brings up
  SD / Speaker / LCD / Touch / Grove 5V in order, configures the
  AXP rails (ALDO1/2/3/4 and DLDO1 for the LCD backlight), and
  exposes cores3_power_manager_enable() for runtime control.

* setup_device.c: factory entries for the AW9523B expander, the
  ILI9341 LCD panel and the FT5x06 touch panel. The expander setup
  programs GCR=0x10 (P0 push-pull) and LEDMODE0/1=0xFF so every
  P0/P1 pin leaves the power-on LED constant-current mode and acts
  as a real GPIO; without this, set_level(high) only releases the
  current sink and cannot drive enables such as BUS_EN/BOOST_EN, so
  the Grove port stays at 0 V.

* components/esp_io_expander_aw9523b/: minimal AW9523B driver
  (16 IOs, push-pull / LED mode register definitions, raw register
  write helper) used by the board package.

* sdkconfig.defaults.board:
    - 16 MB QIO flash @ 80 MHz
    - 8 MB Quad PSRAM @ 80 MHz with XIP / instr / rodata in PSRAM
      disabled (octal-only on ESP32-S3)
    - CONFIG_FREERTOS_TASK_CREATE_ALLOW_EXT_MEM=n so claw tasks
      tagged CLAW_TASK_STACK_PREFER_PSRAM fall back to internal
      RAM, avoiding the cache-disabled stack-sanity assert that
      Quad PSRAM triggers during SPI flash transactions.

Signed-off-by: imliubo <imliubo@makingfun.xyz>

2026-04-22 12:16:05 +08:00

assets_local

feat(core): Added AP configuration and a guard mechanism

2026-04-19 20:27:55 +08:00

boards

boards: add M5Stack CoreS3 board support

2026-04-22 12:16:05 +08:00

components/display_arbiter

feat(basic_demo): porting components expression

2026-04-18 18:56:19 +08:00

fatfs_image

fix(cap_lua): generalize cap_lua skills

2026-04-20 20:35:37 +08:00

main

refactor(cap_lua): streamline lua script path handling

2026-04-20 19:25:09 +08:00

tools

feat(skills): improve lua path handling and sync

2026-04-19 14:13:53 +08:00

.gitignore

change(skills): move basic demo skills into main

2026-04-12 17:38:22 +08:00

CMakeLists.txt

feat(core): Added AP configuration and a guard mechanism

2026-04-19 20:27:55 +08:00

partitions_8MB.csv

fix(basic-demo): add esp32-s3 breadboard support

2026-04-18 18:56:23 +08:00

partitions_16MB.csv

feat(basic_demo): porting components expression

2026-04-18 18:56:19 +08:00

README.md

fix(docs): update readme.md

2026-04-16 22:32:42 +08:00

sdkconfig.defaults

change: update skill and memory wording

2026-04-19 17:56:57 +08:00

README.md

basic_demo Guide

How It Works

The main entry point is application/basic_demo/main/main.c.

After the device boots, the overall flow is:

Initialize NVS and load device settings
Mount FATFS at /fatfs
Initialize Wi-Fi and the local HTTP configuration service
Enter app_claw_start()
Initialize the event router, memory, skills, and capabilities
Initialize and start claw_core
Start the CLI and begin handling requests and events

The current runtime depends on the following local directories:

/fatfs/sessions: session history
/fatfs/memory/MEMORY.md: long-term memory
/fatfs/skills: skill documents and manifest
/fatfs/scripts: Lua scripts
/fatfs/router_rules/router_rules.json: automation rules
/fatfs/inbox: message attachment storage

The current basic_demo integrates the following capabilities:

cap_im_qq
cap_im_tg
cap_files
cap_lua
cap_mcp_client
cap_mcp_server
cap_skill_mgr
cap_time
cap_llm_inspect
cap_web_search

Quick Start

Prerequisites

ESP-IDF is installed and exported
ESP-IDF v5.5.4 is recommended

. <your-esp-idf-path>/export.sh

Configuration

To make esp-board-manager easier to use, first install the helper package with pip install esp-bmgr-assist. You only need to do this once in a given ESP-IDF environment.

Generate board support files:

cd application/basic_demo
idf.py gen-bmgr-config -c ./boards -b esp32_S3_DevKitC_1

idf.py gen-bmgr-config -c ./boards -b <board_name> generates the configuration for the specified board. Available board names can be found in the boards directory.

Configure Wi-Fi, LLM, IM, search engine, and related parameters:

The key demo settings include:

Wi-Fi SSID / Password
LLM API Key / Provider / Model
QQ App ID / App Secret
Telegram Bot Token
Brave / Tavily Search Key
Timezone

Key Notes:

IM bot token: available from Telegram @BotFather or QQ Bot
LLM API key: available from Anthropic Console, OpenAI Platform, or Alibaba Cloud Bailian

You can adjust compile-time default values through menuconfig:

idf.py menuconfig

Build and flash:

idf.py build
idf.py flash monitor