Fire
Overview
M5Stack Fire is an ESP32-based development board from M5Stack.
Hardware
M5Stack Fire features the following integrated components:
ESP32-D0WDQ6 chip (240MHz dual core, 600 DMIPS, 520KB SRAM, Wi-Fi)
PSRAM 8MB
Flash 16MB
LCD IPS TFT 2”, 320x240 px screen (ILI9342C)
Charger IP5306
Audio NS4148 amplifier (1W-092 speaker)
USB CH9102F
SD-Card slot
Grove connector
IMO 6-axis IMU MPU6886
MIC BSE3729
Battery 500mAh 3,7V
Three physical buttons
LED strips
ESP32 Features
Dual core Xtensa microprocessor (LX6), running at 160 or 240MHz
520KB of SRAM
802.11b/g/n/e/i
Bluetooth v4.2 BR/EDR and BLE
Various peripherals:
12-bit ADC with up to 18 channels
2x 8-bit DACs
10x touch sensors
4x SPI
2x I2S
2x I2C
3x UART
SD/SDIO/MMC host
Slave (SDIO/SPI)
Ethernet MAC
CAN bus 2.0
IR (RX/TX)
Motor PWM
LED PWM with up to 16 channels
Hall effect sensor
Temperature sensor
Cryptographic hardware acceleration (RNG, ECC, RSA, SHA-2, AES)
5uA deep sleep current
Asymmetric Multiprocessing (AMP)
Boards featuring the ESP32 and ESP32-S3 SoC allows 2 different applications to be executed. Due to its dual-core architecture, each core can be enabled to execute customized tasks in stand-alone mode and/or exchanging data over OpenAMP framework. See Inter-Processor Communication (IPC) folder as code reference.
Note
** AMP and serial output support **
In the current Zephyr ESP32 implementation, access to Zephyr-managed serial
drivers (such as printk(), logging, or the console UART) is not yet
implemented for applications running on the APPCPU. As a result, serial
output APIs provided by Zephyr are only available on the PROCPU.
As a mitigation, applications running on the APPCPU may use ESP32 ROM
functions such as ets_printf() to emit diagnostic or debug output.
For more information, check the ESP32 Datasheet [1] or the ESP32 Technical Reference Manual [2].
Supported Features
The m5stack_fire board supports the hardware features listed below.
- on-chip / on-board
- Feature integrated in the SoC / present on the board.
- 2 / 2
-
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files. -
vnd,foo -
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.
Functional Description
The following table below describes the key components, interfaces, and controls of the M5Stack Core2 board.
Key Component |
Description |
Status |
|---|---|---|
ESP32-D0WDQ6-V2 module |
This MPU-ESP32 [3] module provides complete Wi-Fi and Bluetooth functionalities and integrates a 16-MB SPI flash. |
supported |
USB Port |
USB interface. Power supply for the board as well as the communication interface between a computer and the board. |
supported |
Power Switch |
Power on/off button. |
supported |
General purpose buttons |
Three buttons on the front face of the device accessible using the GPIO interface. |
supported |
LCD screen |
Built-in LCD TFT display (LCD-ILI9342C [5], 2”, 320x240 px) controlled via SPI interface |
supported |
SD-Card slot |
SD-Card connection via SPI-mode. |
supported |
6-axis IMU MPU6886 |
The MPU-6886 [4] is a 6-axis motion tracker (6DOF IMU) device that combines a 3-axis gyroscope and a 3-axis accelerometer. |
supported |
Grove port |
Used to interface with the many available modules and sensors. |
supported |
Built-in speaker |
1W speaker for analog audio output. |
supported |
Built-in microphone |
The BSE3729 analog microphone. |
todo |
LED strip |
LED strips on the side of the device. |
todo |
Battery-support |
Charging is supported automatically via the IP5306 [6]. But there is no possibility to query current battery status. |
todo |
System Requirements
Binary Blobs
Espressif HAL requires RF binary blobs in order work. Run the command below to retrieve those files.
west blobs fetch hal_espressif
Note
It is recommended running the command above after west update.
Programming and Debugging
The m5stack_fire board supports the runners and associated west commands listed below.
| flash | debug |
|---|
Simple Boot
The board could be loaded using the single binary image, without 2nd stage bootloader. It is the default option when building the application without additional configuration.
Note
Simple boot does not provide any security features nor OTA updates.
MCUboot Bootloader
User may choose to use MCUboot bootloader instead. In that case the bootloader must be built (and flashed) at least once.
There are two options to be used when building an application:
Sysbuild
Manual build
Note
User can select the MCUboot bootloader by adding the following line to the board default configuration file.
CONFIG_BOOTLOADER_MCUBOOT=y
Sysbuild
The sysbuild makes possible to build and flash all necessary images needed to bootstrap the board with the ESP32 SoC.
To build the sample application using sysbuild use the command:
west build -b <board> --sysbuild samples/hello_world
By default, the ESP32 sysbuild creates bootloader (MCUboot) and application images. But it can be configured to create other kind of images.
Build directory structure created by sysbuild is different from traditional Zephyr build. Output is structured by the domain subdirectories:
build/
├── hello_world
│ └── zephyr
│ ├── zephyr.elf
│ └── zephyr.bin
├── mcuboot
│ └── zephyr
│ ├── zephyr.elf
│ └── zephyr.bin
└── domains.yaml
Note
With --sysbuild option the bootloader will be re-build and re-flash
every time the pristine build is used.
For more information about the system build please read the Sysbuild (System build) documentation.
Manual Build
During the development cycle, it is intended to build & flash as quickly possible. For that reason, images can be built one at a time using traditional build.
The instructions following are relevant for both manual build and sysbuild. The only difference is the structure of the build directory.
Note
Remember that bootloader (MCUboot) needs to be flash at least once.
Build and flash applications as usual (see Building an Application and Run an Application for more details).
# From the root of the zephyr repository
west build -b <board> samples/hello_world
The usual flash target will work with the board configuration.
Here is an example for the Hello World
application.
# From the root of the zephyr repository
west build -b <board> samples/hello_world
west flash
Open the serial monitor using the following command:
west espressif monitor
After the board has automatically reset and booted, you should see the following message in the monitor:
***** Booting Zephyr OS vx.x.x-xxx-gxxxxxxxxxxxx *****
Hello World! <board>
Board variants using Snippets
ESP32 boards can be assembled with different modules using multiple combinations of SPI flash sizes, PSRAM sizes and PSRAM modes.
The snippets under snippets/espressif provide a modular way to apply these variations at build time without duplicating board definitions.
The following snippet-based variants are supported:
Snippet name |
Description |
|---|---|
Flash memory size |
|
|
Board with 4MB of flash |
|
Board with 8MB of flash |
|
Board with 16MB of flash |
|
Board with 32MB of flash |
|
Board with 64MB of flash |
|
Board with 128MB of flash |
PSRAM memory size |
|
|
Board with 2MB of PSRAM |
|
Board with 4MB of PSRAM |
|
Board with 8MB of PSRAM |
PSRAM utilization |
|
|
Relocate flash to PSRAM |
|
Wi-Fi buffers in PSRAM |
To apply a board variant, use the -S flag with west build:
west build -b <board> -S espressif-flash-32M -S espressif-psram-4M samples/hello_world
Note
These snippets are only applicable to boards with compatible hardware support for the selected flash/PSRAM configuration.
If no FLASH snippet is used, the board default flash size will be used.
If no PSRAM snippet is used, the board default psram size will be used.
Debugging
M5Stack Fire debugging is not supported due to pinout limitations.