mirror of
https://github.com/m5stack/CoreS3-Box.git
synced 2026-05-20 10:59:43 -07:00
docs:add repository readme
This commit is contained in:
Li Bo
Zhe
@@ -1,57 +1,89 @@
|
||||
# Espressif HMI Development Framework
|
||||
* [中文版](./README_cn.md)
|
||||
|
||||
* [中文版](./docs/README_cn.md)
|
||||
# ESP-BOX Developer Guide
|
||||
|
||||
Espressif Systems HMI Development Framework (ESP-HMI) is the official HMI development framework for the [ESP32](https://espressif.com/en/products/hardware/esp32/overview), [ESP32-S2](https://www.espressif.com/en/products/socs/esp32-s2), [ESP32-S3](https://www.espressif.com/en/products/socs/esp32-s3) and [ESP32-C3](https://www.espressif.com/en/products/socs/esp32-c3) SoCs.
|
||||
ESP-BOX is a new generation AIoT application development kits released by Espressif Systems, powered by Espressif ESP32-S3 SoC, supporting AI acceleration and Wi-Fi + Bluetooth 5 (LE) wireless functions. ESP-BOX has a built-in 2.4-inch LCD capacitive touch screen, dual microphones, a speaker, and dual Pmod™ compatible expansion interfaces. With the out-of-the-box voice wake-up and voice recognition functions, as well as Espressif's open-source development framework and examples, developers can create various interesting AIoT applications better and faster.
|
||||
|
||||
## Overview
|
||||
## Hardware Overview
|
||||
|
||||
ESP-HMI supports development of HMI applications for the Espressif Systems SoCs in the most comprehensive way. With ESP-HMI, you can easily add features, develop HMI applications from simple to complex:
|
||||
|
||||
|
||||
- Light up LCD and change pixels of it.
|
||||
- Display image on LCD from Flash RO-data, SPIFFS, SD card, host via JTAG or network.
|
||||
- Using TTF/OTF fonts to display CJK fonts or change it's size as you wish.
|
||||
- Develop fancy GUI demo.
|
||||
|
||||
## Framework
|
||||
|
||||
ESP-HMI contains
|
||||
|
||||
## Development with ESP-HMI
|
||||
|
||||
### Setting Up ESP-IDF
|
||||
|
||||
See https://idf.espressif.com/ for links to detailed instructions on how to set up the ESP-IDF depending on chip you use.
|
||||
|
||||
**Note:** Each SoC series and each ESP-IDF release has its own documentation. Please see Section [Versions](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/versions.html) on how to find documentation and how to checkout specific release of ESP-IDF.
|
||||
|
||||
> **Non-GitHub forks**
|
||||
>
|
||||
> ESP-IDF uses relative locations as its submodules URLs ([.gitmodules](https://github.com/espressif/esp-idf/blob/master/.gitmodules)). So they link to GitHub. If ESP-IDF is forked to a Git repository which is not on GitHub, you will need to run the script [tools/set-submodules-to-github.sh](https://github.com/espressif/esp-idf/blob/master/tools/set-submodules-to-github.sh) after git clone. The script sets absolute URLs for all submodules, allowing `git submodule update --init --recursive` to complete. If cloning ESP-IDF from GitHub, this step is not needed.
|
||||
|
||||
### Get ESP-HMI
|
||||
|
||||
### Update Sub-modules
|
||||
|
||||
It is not necessary for you to update sub-modules if you used recursive clone.
|
||||
* [ESP-BOX Mainboard Schematic](./docs/hardware/schematic/SCH_ESP32-S3-BOX_V2.5.pdf)
|
||||
* [ESP-BOX Mainboard PCB](./docs/hardware/pcb/PCB_ESP32-S3-BOX_V2.4.pdf)
|
||||
|
||||
|
||||
### Specifications:
|
||||
|
||||
You can run `git submodule update --init --recursive` to checkout all sub-modules.
|
||||
|
||||
|
||||
## Examples
|
||||
### Ports:
|
||||
|
||||
- Get-Started
|
||||
- Basic LCD operation and input
|
||||
- Image display with raw LCD APIs
|
||||
- An camera receiver
|
||||
- LVGL Examples
|
||||
- Demos provided by LVGL
|
||||
- Project template
|
||||
- Display image using official image display repos
|
||||
- Vector font render with FreeType
|
||||
- A GUI provision demo
|
||||
- Audio Examples
|
||||
- A simple music player
|
||||
- A simple recorder
|
||||
|
||||
|
||||
* [Digilent Pmod™ Interface Specification](https://digilent.com/reference/_media/reference/pmod/pmod-interface-specification-1_3_1.pdf)
|
||||
|
||||
## Technical Architecture
|
||||
|
||||
The ESP-BOX development framework includes three main layers: system layer, framework layer, and application layer:
|
||||
|
||||
|
||||
|
||||
### System Layer
|
||||
|
||||
ESP-IDF is the open-source development framework for Espressif SoCs including ESP32、ESP32-S and ESP32-C series. It integrates a large number of system-level basic components, a set of development tools for code compilation and debugging, and detailed development guidance documents:
|
||||
|
||||
1. System-level basic components, mainly including multi-tasking, multi-core support based on FreeRTOS, and memory heap allocator with external expansion of PSRAM; a uniform operation interface support for LL, HAL, Driver, and VFS layers of multiple ESP chips; multiple standard network protocol stacks like TCP/IP, HTTP, MQTT, WebSocket, etc.
|
||||
2. Set of development tools, mainly including GCC cross-toolchain for code building, JTAG debugging tool based on OpenOCD, real-time tracking based on Segger SystemView, Flash and eFuse programmers, etc.
|
||||
3. Development guidance documents, API references, guidelines, and notes of Espressif’s various chip platforms and software versions. Developers can view these documents [Online](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/) or [Download](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/esp-idf-en-v4.4-dev-3540-g4e03a9c-esp32.pdf).
|
||||
|
||||
### Framework Layer
|
||||
|
||||
In addition to system-level support, ESP-BOX also integrates several excellent solution frameworks for typical problems in different scenarios. Including the speech recognition framework ESP-SR, the human-computer interaction framework ESP-HMI, and the end-to-end IoT development framework ESP-RainMaker. The functions and customization methods of these solution frameworks will be briefly introduced as follows:
|
||||
|
||||
**ESP-SR**
|
||||
|
||||
ESP-SR is a speech recognition framework developed by Espressif for the field of intelligent speech. ESP-SR can provide high-performance and high-reliability speech recognition functions for developers by using ESP32-S3 AI extension instructions. Now, this framework has three modules:
|
||||
|
||||
1. Espressif's acoustic algorithm ([Audio Front-End, AFE](https://github.com/espressif/esp-sr/tree/master/acoustic_algorithm)) , which is specially designed to improve speech recognition performance in far-field or noisy environments to enable developers to obtain high-quality and stable audio data. It mainly includes AEC (Acoustic Echo Cancellation) , BSS (Blind Source Separation), NS (Noise Suppression). ESP-SR encapsulates the above algorithms into simple APIs. Without undersatanding details of these algorithms, developers only need to arrange and combine the algorithms that need to be used for specific application scenarios, and input the voice data to be processed according to the API format requirements and can get the results.
|
||||
2. Espressif wake word engine ([WakeNet](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/README.md)), which is used to monitor specific language fragments in real-time in a continuous audio stream, and wake up the smart device from the standby state to the voice interaction state. WakeNet uses MFC (Mel-Frequency Cepstrum) to obtain the features of the input audio clip , and classifies the characteristic signals by the neural network algorithm optimized for ESP32-S3. It can trigger the wake-up signal when monitor the command word, and the [Effective recognition rate](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/README.md#performance-test) is not less than 80% in noisy environment. ESP-BOX provides different offline wake words like “Xiao Ai Tong Xue” “Hi, Lexin” etc. and also allows [customized wake word](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/ESP_Wake_Words_Customization.md).
|
||||
3. Espressif wake-up word engine ([WakeNet](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/README.md)), which is used to monitor specific language fragments in real-time in a continuous audio stream, and wake up the smart device from the standby state to the voice interaction state. WakeNet uses MFC (Mel-frequency Cepstrum) to obtain the features of the input audio clip, then classifies the characteristic signals by the neural network algorithm optimized for ESP32-S3. That can trigger the wake-up signal when analyzed the command word, and the [Effective recognition rate](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/README.md#performance-test) is more than 80% in a noisy environment. ESP-BOX provides different offline wake words like “Hi, ESP” and “Hi, Lexin”. And also allows [customized wake word](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/ESP_Wake_Words_Customization.md).
|
||||
|
||||
**ESP-HMI**
|
||||
|
||||
ESP-HMI is a human-computer interaction solution designed by Espressif based on the open-source GUI framework LVGL. With the powerful computing and peripheral resources in ESP32-S3, it can achieve excellent data visualization, touch control, and other functions:
|
||||
|
||||
1. Screen driver library: compatible with a variety of mainstream 8080, SPI, I2C interface color screens, monochrome screens, touch screens, and provide a uniform display driver interface. Developers can directly use the adapted screen controller or add their screens according to the display driver interface. And the UI interface can be deployed to a variety of screens.
|
||||
2. Open source UI templates: Espressif has designed multiple open source UI templates suitable for IoT control panels, multimedia players, voice assistants, and other different IoT scenarios, which can help developers carry out more professional secondary development.
|
||||
3. Hardware design reference: Espressif provides hardware reference designs, circuit schematics, and development guides related to screen applications to help developers quickly complete hardware designs.
|
||||
|
||||
**ESP-RainMaker**
|
||||
|
||||
[ESP-RainMaker](https://rainmaker.espressif.com/docs/get-started.html) is a complete system for IoT development, and it can As an end-to-end platform, it can provide developers with one-stop IoT product functions and examples such as device distribution, cloud connection, and OTA, it contains the following functions:
|
||||
|
||||
1. Device-side SDK, developers can use Espressif chips to define their IoT products by designing device parameters and attributes, and complete device-side firmware development quickly.
|
||||
2. Secure cloud middleware, developers do not need to manage device certificates and cloud infrastructure. They can directly use Espressif chips to quickly establish a secure communication link with the cloud.
|
||||
3. iOS / Android APP, which integrates the necessary functions such as device discovery, Wi-Fi provisioning, user login, device association and control, and developers do not need to carry out additional code development work.
|
||||
|
||||
**AI Instructions and Libraries**
|
||||
|
||||
With the help of ESP32-S3 Xtensa® 32bit LX7 dual-core CPU and AI / DSP extended instruction set, ESP32-S3 can efficiently complete vector operations, complex number operations, FFT and other operations, which can accelerate neural network calculations and digital signal processing calculation capabilities. AI developers can implement high-performance image recognition, voice wake-up and recognition with Espressif's open source software library based on the AI / DSP extended instruction set.
|
||||
|
||||
**Device Drivers**
|
||||
|
||||
TBD:
|
||||
|
||||
### Application Layer
|
||||
|
||||
TBD:
|
||||
|
||||
## Develop Guide
|
||||
|
||||
1. [Setting up development environment]().
|
||||
2. Try out some [examples](./examples).
|
||||
3. Read the [Build System](https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/build-system.html) to see the overview of building process.
|
||||
4. Read the [Application Startup Flow](https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/startup.html) to get a better understanding of the program.
|
||||
5. Read the [Setup Command word]() to redesign your own command words.
|
||||
6. Read the [LVGL Quick overview](https://docs.lvgl.io/latest/en/html/get-started/quick-overview.html) to learn the most importance things to add your favorite GUI.
|
||||
7. Read the [ESP-IDF API Reference](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/index.html) to develop drivers for Pmod interface devices.
|
||||
8. If you have questions please add [GitHub Issues](https://docs.github.com/en/issues) or goto esp32.com forum to get help.
|
||||
9. [Pull Requests](https://docs.github.com/en/github/collaborating-with-pull-requests) is welcome if you're interested in contributing to ESP-Box.
|
||||
|
||||
@@ -0,0 +1,86 @@
|
||||
* [English Version](./README.md)
|
||||
|
||||
# ESP-BOX 开发者指南
|
||||
|
||||
ESP-Box 是乐鑫信息科技发布的新一代 AIoT 应用开发板，搭载乐鑫 ESP32-S3 SoC，支持 AI 加速指令和 Wi-Fi + Bluetooth 5 (LE) 无线功能。ESP-Box 内置 2.4 英寸 LCD 电容式触摸显示屏，双麦克风，扬声器，和两个 Pmod 兼容的多功能扩展接口。配合开箱即用的语音唤醒和识别功能，以及开源开发框架和示例程序，开发者基于 ESP-Box 可以更快更好的构建各种有趣的 AIoT 智能应用。
|
||||
|
||||
## 硬件总览
|
||||
|
||||
|
||||
|
||||
* [ESP-BOX Mainboard Schematic](./docs/hardware/schematic/SCH_ESP32-S3-BOX_V2.5.pdf)
|
||||
* [ESP-BOX Mainboard PCB](./docs/hardware/pcb/PCB_ESP32-S3-BOX_V2.4.pdf)
|
||||
|
||||
|
||||
### 规格参数:
|
||||
|
||||
|
||||
|
||||
### 接口:
|
||||
|
||||
|
||||
|
||||
* [Digilent Pmod™ Interface Specification](https://digilent.com/reference/_media/reference/pmod/pmod-interface-specification-1_3_1.pdf)
|
||||
|
||||
## 技术架构
|
||||
|
||||
ESP-BOX 开发框架包括系统层、框架层、应用层三个主要层级：
|
||||
|
||||
|
||||
|
||||
### 系统层 System Layer
|
||||
|
||||
ESP-IDF 是乐鑫官方开源操作系统框架，同时兼容 ESP32、ESP32-S 和 ESP32-C 系列 SoC，完成一次开发即可在多芯片平台部署。它集成了大量的系统级基础组件，用于代码编译和调试的开发工具集，以及详尽的开发指导文档，具体包括：
|
||||
1. 系统级基础组件，主要包括基于 FreeRTOS 的多任务、多核支持，可外扩 PSRAM 的内存堆分配器；多款 ESP 芯片的 LL、HAL、Driver、VFS 层支持，将不同芯片功能抽象为统一操作接口；多个标准网络协议栈 TCP/IP、HTTP、MQTT、WebSocket 等等；
|
||||
2. 开发工具集，主要包含用于代码编译的 GCC 交叉工具链、基于 OpenOCD 的 JTAG 调试工具、基于 Segger SystemView 的实时跟踪、Flash 和 eFuse 编程器等；
|
||||
3. 开发指导文档，详尽的说明了乐鑫各个芯片平台、各个软件版本下的 API 参考，使用指引和注意事项等，开发者可[在线浏览](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/)也可[下载到本地](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/esp-idf-en-v4.4-dev-3540-g4e03a9c-esp32.pdf)查看。
|
||||
|
||||
### 框架层 Framework Layer
|
||||
|
||||
除了系统层支持外，ESP-BOX 还集成了多个出色的解决方案框架，分别处理不同功能场景下的典型问题。包括用于处理语音唤醒词和命令词的语音识别框架 ESP-SR，处理显示和触摸交互功能的人机交互框架 ESP-HMI，和处理物联网功能的端到端物联网开发框架 ESP-RainMaker，接下来将简要介绍这些解决方案框架的功能和定制化方法：
|
||||
|
||||
**ESP-SR**
|
||||
|
||||
ESP-SR 是乐鑫面向智能语音领域开发的语音识别框架，该框架可利用 ESP32-S3 AI 扩展指令进行运算加速，为开发者提供开箱即用的高性能、高可靠性的语音识别功能，它包括：
|
||||
|
||||
1. 声学前端（[Audio Front-End, AFE](https://github.com/espressif/esp-sr/tree/master/acoustic_algorithm)）算法集，用于提升智能语音设备在远场噪声环境中的交互能力，使开发者获得高质量且稳定的音频数据。它主要包括可以有效滤除扬声器回声的回声消除算法（Acoustic Echo Cancellation，AEC）, 用于强化麦克风阵列方向性的盲源分离算法（Blind Source Separation，BSS），和用于处理环境噪声的噪声抑制算法（Noise Suppression，NS）。ESP-SR 将以上算法封装成简单的 API，开发者无需关心这些算法的具体细节，只需要针对具体的应用场景，对需要使用的算法排列组合，并按照 API 的格式要求输入待处理的语音数据，即可得到声学前端算法的处理结果。
|
||||
2. 唤醒词识别模型（[WakeNet](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/README.md)），用于在连续的音频流中实时监测出特定的语言片段，将智能设备从待机状态唤醒至语音交互状态。WakeNet 通过计算音频片段的梅尔倒频谱（Mel-Frequency Cepstrum, MFC）作为输入特征，使用针对 ESP32-S3 优化的神经网络算法对特征信号进行分类，在监测到命令词时触发唤醒信号，可在噪声环境下获得不小于 80% 的[有效识别率](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/README.md#performance-test)。ESP-BOX 提供了开箱即用的离线唤醒词 “Hi, ESP” 和 “Hi, 乐鑫”，开发者无需额外的开发工作即可使用，同时乐鑫也支持为开发者[定制独特的唤醒词](https://github.com/espressif/esp-sr/blob/master/wake_word_engine/ESP_Wake_Words_Customization.md)。
|
||||
3. 命令词识别模型（[MultiNet](https://github.com/espressif/esp-sr/blob/master/speech_command_recognition/README.md)），用于在设备唤醒后，识别用户特定的中英文语音命令，例如 “Turn on the air conditioner”，“关闭电灯” 等。MultiNet 通过基于 CRNN 和 CTC 的卷积循环神经网络，对输入音频片段进行多命令词识别，可同时支持最多 100 个离线命令词。 开发者不需要了解识别模型细节，也无需重新进行模型训练，通过简单配置[中文拼音字符串](https://github.com/espressif/esp-sr/blob/master/speech_command_recognition/README.md#chinese-speech-command-recognition)或[英文音标字符串](https://github.com/espressif/esp-sr/blob/master/speech_command_recognition/README.md#english-speech-command-recognition)以及对应 ID，即可添加或修改命令词，模型在识别到语音命令词后将触发包含 ID 信息的事件。
|
||||
|
||||
**ESP-HMI**
|
||||
|
||||
ESP-HMI 是乐鑫基于开源 GUI 框架 LVGL 设计的人机交互方案，借助 ESP32-S3 强大的计算能力和外设资源，可以实现出色的数据可视化、触摸控制等功能，它包括：
|
||||
1. 屏幕驱动库：兼容多款主流 8080、SPI、I2C 接口彩色屏幕、单色屏、触摸屏，提供统一的显示驱动接口。开发者可以直接使用已适配的屏幕控制器，也可根据显示驱动接口添加自己的屏幕，UI 界面开发完成可无缝部署到多种屏幕。
|
||||
2. 开源 UI 模板：乐鑫设计了适用于物联网控制面板、多媒体播放器、语音助手等不同物联网场景的多套开源 UI 模板，帮助开发者进行更专业的二次开发。
|
||||
3. 硬件参考设计：提供屏幕应用相关的硬件参考设计、电路原理图和开发指南，帮助开发者快速完成硬件设计。
|
||||
|
||||
**ESP-RainMaker**
|
||||
|
||||
[ESP-RainMaker](https://rainmaker.espressif.com/docs/get-started.html) 是一个完整的物联网开发框架，作为一个端到端平台，可以为开发者提供设备配网、连云、OTA 等一站式的物联网产品功能和示例。它包含：
|
||||
1. 设备端 SDK，开发者通过设计设备参数和属性，即可使用乐鑫芯片定义自己的物联网产品，快速完成设备端固件开发;
|
||||
2. 透明的云中间件，开发者无需管理设备证书和云端基础设施，直接使用乐鑫芯片即可快速建立与云端的建立安全的通信链接；
|
||||
3. iOS / Android 平台 APP，集成了设备发现，Wi-Fi 配网，用户登录，设备关联和控制等必要功能，开发者无需进行额外的代码开发工作。
|
||||
|
||||
**AI 指令集和库**
|
||||
|
||||
借助 ESP32-S3 Xtensa® 32bit LX7 双核 CPU 和 AI / DSP 扩展指令集，ESP32-S3 可高效完成向量运算、复数运算、FFT 等运算，加速神经网络计算和数字信号处理计算能力。AI 开发者们可以基于乐鑫开源的基于 AI / DSP 扩展指令集的软件库，实现高性能的图像识别、语音唤醒与识别等应用。
|
||||
|
||||
**设备驱动 Device Drivers**
|
||||
|
||||
TBD:
|
||||
|
||||
### 应用层 Application Layer
|
||||
|
||||
TBD:
|
||||
|
||||
## 开发指引
|
||||
|
||||
1. [搭建开发环境]()；
|
||||
2. 尝试编译几个[示例程序](./examples)；
|
||||
3. 查阅 [编译系统](https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/build-system.html) 可以进一步理解程序的编译链接过程；
|
||||
4. 查阅 [应用程序启动流程](https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/startup.html) 可以更好的理解 ESP 固件程序的运行流程；
|
||||
5. 查阅 [配置命令词]() 定义自己的专属命令词；
|
||||
6. 查阅 [LVGL 快速总览](https://docs.lvgl.io/latest/en/html/get-started/quick-overview.html) 学习如何添加一个喜爱的 GUI；
|
||||
7. 查阅 [ESP-IDF API 参考手册](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/index.html) 为 Pmod 外接设备开发驱动；
|
||||
8. 如果你有问题，可添加 [GitHub Issues](https://docs.github.com/en/issues) 或者到 esp32.com 论坛寻求帮助；
|
||||
9. 如果你对 ESP-BOX 项目感兴趣，欢迎贡献代码 [Pull Requests](https://docs.github.com/en/github/collaborating-with-pull-requests)。
|
||||
+4
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 30 KiB |
+1
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 63 KiB |
@@ -0,0 +1,37 @@
|
||||
<style type="text/css">
|
||||
.tg {border-collapse:collapse;border-spacing:0;}
|
||||
.tg td{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px;
|
||||
overflow:hidden;padding:10px 5px;word-break:normal;}
|
||||
.tg th{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px;
|
||||
font-weight:normal;overflow:hidden;padding:10px 5px;word-break:normal;}
|
||||
.tg .tg-cly1{text-align:left;vertical-align:middle}
|
||||
.tg .tg-wa1i{font-weight:bold;text-align:center;vertical-align:middle}
|
||||
.tg .tg-f189{background-color:#dae8fc;text-align:center;vertical-align:middle}
|
||||
</style>
|
||||
<table class="tg">
|
||||
<thead>
|
||||
<tr>
|
||||
<th class="tg-f189" colspan="4">Ports</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td class="tg-wa1i">Type</td>
|
||||
<td class="tg-wa1i">Number</td>
|
||||
<td class="tg-wa1i">Details</td>
|
||||
<td class="tg-wa1i">Usage</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-cly1">Pmod™ Compatible</td>
|
||||
<td class="tg-cly1">2</td>
|
||||
<td class="tg-cly1">8 IO, 3.3 V Power output</td>
|
||||
<td class="tg-cly1">GPIO, I2C, SPI, UART, RMT, LEDC, etc.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-cly1">USB Type-C</td>
|
||||
<td class="tg-cly1">1</td>
|
||||
<td class="tg-cly1">5 V Power Input, USB D+, D-.</td>
|
||||
<td class="tg-cly1">USB download, USB JTAG debug, general USB functions</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
@@ -0,0 +1,165 @@
|
||||
<style type="text/css">
|
||||
.tg {border-collapse:collapse;border-spacing:0;}
|
||||
.tg td{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px;
|
||||
overflow:hidden;padding:6px 4px;word-break:normal;}
|
||||
.tg th{border-color:black;border-style:solid;border-width:1px;font-family:Arial, sans-serif;font-size:14px;
|
||||
font-weight:normal;overflow:hidden;padding:6px 4px;word-break:normal;}
|
||||
.tg .tg-ycr8{background-color:#ffffff;text-align:left;vertical-align:top}
|
||||
.tg .tg-3wa1{background-color:#ECF4FF;font-weight:bold;text-align:center;vertical-align:middle}
|
||||
.tg .tg-zr06{background-color:#FFF;text-align:left;vertical-align:middle}
|
||||
.tg .tg-o2c7{background-color:#ECF4FF;font-weight:bold;text-align:center;vertical-align:top}
|
||||
.tg .tg-0lax{text-align:left;vertical-align:top}
|
||||
</style>
|
||||
<table class="tg" style="undefined;table-layout: fixed; width: 781px">
|
||||
<colgroup>
|
||||
<col style="width: 146px">
|
||||
<col style="width: 227px">
|
||||
<col style="width: 156px">
|
||||
<col style="width: 252px">
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr>
|
||||
<th class="tg-3wa1" colspan="4">SoC</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td class="tg-zr06">SoC Type:</td>
|
||||
<td class="tg-zr06">ESP32-S3</td>
|
||||
<td class="tg-zr06">SoC Details:</td>
|
||||
<td class="tg-zr06">Dual-Core, 2.4 GHz Wi-Fi and Bluetooth® 5 LE</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-o2c7" colspan="4"><span style="font-weight:bold">CPU / Memory</span></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">CPU Type:</td>
|
||||
<td class="tg-zr06">Dual-Core Xtensa® 32bit LX7</td>
|
||||
<td class="tg-zr06">CPU Speed:</td>
|
||||
<td class="tg-zr06">240 MHz</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Flash Type:</td>
|
||||
<td class="tg-zr06">Quad SPI</td>
|
||||
<td class="tg-zr06">Flash Size:</td>
|
||||
<td class="tg-zr06">16 MB</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Flash Speed:</td>
|
||||
<td class="tg-zr06">120 MHz</td>
|
||||
<td class="tg-zr06">SRAM Size</td>
|
||||
<td class="tg-zr06">512 KB</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">PSRAM Type:</td>
|
||||
<td class="tg-zr06">Octal SPI</td>
|
||||
<td class="tg-zr06">PSRAM Size:</td>
|
||||
<td class="tg-zr06">8 MB</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-ycr8">PSRAM Speed:</td>
|
||||
<td class="tg-ycr8">120 MHz</td>
|
||||
<td class="tg-ycr8"></td>
|
||||
<td class="tg-ycr8"></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-3wa1" colspan="4">AI Ability</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">AI Algorithm</td>
|
||||
<td class="tg-zr06">Neural Network, Acoustic algorithm, etc.</td>
|
||||
<td class="tg-zr06">Computing Acceleration</td>
|
||||
<td class="tg-zr06">Vector, Complex number, FFT, etc.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-3wa1" colspan="4">Wireless</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Wi-Fi:</td>
|
||||
<td class="tg-zr06">IEEE 802.11b/g/n</td>
|
||||
<td class="tg-zr06">Bluetooth® LE:</td>
|
||||
<td class="tg-zr06">Bluetooth® 5 and Bluetooth® mesh</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-o2c7" colspan="4"><span style="font-weight:bold">Display</span></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Display Type:</td>
|
||||
<td class="tg-zr06">2.4‑inch LCD</td>
|
||||
<td class="tg-zr06">Display Resolution:</td>
|
||||
<td class="tg-zr06">240 x 320</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Display Interface:</td>
|
||||
<td class="tg-zr06">SPI</td>
|
||||
<td class="tg-zr06">Interface Speed:</td>
|
||||
<td class="tg-zr06">40 MHz</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Touch Type:</td>
|
||||
<td class="tg-zr06">Capacitive</td>
|
||||
<td class="tg-zr06">Touch Points:</td>
|
||||
<td class="tg-zr06">10</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-o2c7" colspan="4"><span style="font-weight:bold">Microphone</span></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Microphone Type:</td>
|
||||
<td class="tg-zr06">Dual Mic</td>
|
||||
<td class="tg-zr06">ADC Model:</td>
|
||||
<td class="tg-zr06">ES7210</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Mute:</td>
|
||||
<td class="tg-zr06">Supported</td>
|
||||
<td class="tg-0lax"></td>
|
||||
<td class="tg-0lax"></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-o2c7" colspan="4"><span style="font-weight:bold">Speaker</span></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Codec Model:</td>
|
||||
<td class="tg-zr06">ES8311</td>
|
||||
<td class="tg-zr06">PA Model:</td>
|
||||
<td class="tg-zr06">NS4150</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-3wa1" colspan="4">Sensors</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Sensor Type:</td>
|
||||
<td class="tg-zr06">3‑axis Gyroscope, 3‑axis Accelerometer</td>
|
||||
<td class="tg-zr06">Sensor Model:</td>
|
||||
<td class="tg-zr06">ICM-42607-P</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-3wa1" colspan="4">OS / SDK</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Original OS:</td>
|
||||
<td class="tg-zr06">FreeRTOS</td>
|
||||
<td class="tg-zr06">SDK:</td>
|
||||
<td class="tg-zr06">ESP-IDF</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-3wa1" colspan="4">Outline</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">Dimensions:</td>
|
||||
<td class="tg-zr06">66.1 x 61.2 x 17.6 mm</td>
|
||||
<td class="tg-zr06">Weight:</td>
|
||||
<td class="tg-zr06">TBD</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-3wa1" colspan="4">Power</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td class="tg-zr06">USB-C Power:</td>
|
||||
<td class="tg-zr06">5 V - 2.0 A Input</td>
|
||||
<td class="tg-zr06">Battery:</td>
|
||||
<td class="tg-zr06">N/A</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 113 KiB |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Reference in New Issue
Block a user