差别
这里会显示出您选择的修订版和当前版本之间的差别。
两侧同时换到之前的修订记录 前一修订版 | |||
developmentboard:esp32-s3_lcd [2024/09/15 06:39] – admin | developmentboard:esp32-s3_lcd [2024/09/15 06:39] (当前版本) – admin | ||
---|---|---|---|
行 1: | 行 1: | ||
ESP32-S3-CORE | ESP32-S3-CORE | ||
- | ===== = ESP32S3-Luatos-Core ====== | + | ===== = ESP32S3-Luatos-Core ===== |
- | ===== Overview[[https:// | + | The ESP32S3-Luatos-Core development board is a compact board based on Espressif ESP32-S3. The board comes equipped with a 2.4GHz antenna and supports both Wi-Fi and Bluetooth functionalities. |
- | + | ||
- | The ESP32S3-Luatos-Core development board is a compact board based on Espressif ESP32-S3. The board comes equipped with a 2.4GHz antenna and supports both Wi-Fi and Bluetooth functionalities. | + | |
{{https:// | {{https:// | ||
- | ===== Hardware | + | |
+ | ===== Hardware ===== | ||
ESP32-S3 is a low-power MCU-based system on a chip (SoC) with integrated 2.4 GHz Wi-Fi and Bluetooth® Low Energy (Bluetooth LE). It consists of high-performance dual-core microprocessor (Xtensa® 32-bit LX7), a low power coprocessor, | ESP32-S3 is a low-power MCU-based system on a chip (SoC) with integrated 2.4 GHz Wi-Fi and Bluetooth® Low Energy (Bluetooth LE). It consists of high-performance dual-core microprocessor (Xtensa® 32-bit LX7), a low power coprocessor, | ||
行 159: | 行 158: | ||
{{https:// | {{https:// | ||
- | ==== Supported Features | + | |
+ | ==== Supported Features ==== | ||
Current Zephyr’s ESP32S3-Luatos-Core board supports the following features: | Current Zephyr’s ESP32S3-Luatos-Core board supports the following features: | ||
- | ^ \\ Interface | + | ^ \\ Interface^ \\ Controller^ \\ Driver/ |
- | | \\ UART \\ | \\ on-chip | + | | \\ UART| \\ on-chip| \\ serial port| |
- | | \\ GPIO \\ | \\ on-chip | + | | \\ GPIO| \\ on-chip| \\ gpio| |
- | | \\ PINMUX | + | | \\ PINMUX| \\ on-chip| \\ pinmux| |
- | | \\ USB-JTAG | + | | \\ USB-JTAG| \\ on-chip| \\ hardware interface| |
- | | \\ SPI Master | + | | \\ SPI Master| \\ on-chip| \\ spi| |
- | | \\ TWAI/ | + | | \\ TWAI/CAN| \\ on-chip| \\ can| |
- | | \\ Timers | + | | \\ Timers| \\ on-chip| \\ counter| |
- | | \\ Watchdog | + | | \\ Watchdog| \\ on-chip| \\ watchdog| |
- | | \\ TRNG \\ | \\ on-chip | + | | \\ TRNG| \\ on-chip| \\ entropy| |
- | | \\ LEDC \\ | \\ on-chip | + | | \\ LEDC| \\ on-chip| \\ pwm| |
- | | \\ MCPWM \\ | \\ on-chip | + | | \\ MCPWM| \\ on-chip| \\ pwm| |
- | | \\ PCNT \\ | \\ on-chip | + | | \\ PCNT| \\ on-chip| \\ qdec| |
- | | \\ GDMA \\ | \\ on-chip | + | | \\ GDMA| \\ on-chip| \\ dma| |
- | | \\ USB-CDC | + | | \\ USB-CDC| \\ on-chip| \\ serial| |
- | === Prerequisites | + | === Prerequisites === |
Espressif HAL requires WiFi and Bluetooth binary blobs in order work. Run the command below to retrieve those files. | Espressif HAL requires WiFi and Bluetooth binary blobs in order work. Run the command below to retrieve those files. | ||
< | < | ||
- | west blobs fetch hal_espressif | ||
+ | west blobs fetch hal_espressif | ||
</ | </ | ||
行 192: | 行 192: | ||
It is recommended running the command above after '' | It is recommended running the command above after '' | ||
- | ==== = Building & Flashing ===== | + | ==== = Building & Flashing ==== |
- | ==== Simple boot[[https:// | + | ==== 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. | 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. | ||
行 202: | 行 202: | ||
Simple boot does not provide any security features nor OTA updates. | Simple boot does not provide any security features nor OTA updates. | ||
- | ==== MCUboot bootloader | + | ==== MCUboot bootloader ==== |
User may choose to use MCUboot bootloader instead. In that case the bootloader must be built (and flashed) at least once. | User may choose to use MCUboot bootloader instead. In that case the bootloader must be built (and flashed) at least once. | ||
行 219: | 行 219: | ||
User can select the MCUboot bootloader by adding the following line to the board default configuration file. | User can select the MCUboot bootloader by adding the following line to the board default configuration file. | ||
+ | |||
< | < | ||
CONFIG_BOOTLOADER_MCUBOOT=y | CONFIG_BOOTLOADER_MCUBOOT=y | ||
- | |||
</ | </ | ||
- | ==== Sysbuild | + | |
+ | ==== Sysbuild ==== | ||
The sysbuild makes possible to build and flash all necessary images needed to bootstrap the board with the ESP32 SoC. | The sysbuild makes possible to build and flash all necessary images needed to bootstrap the board with the ESP32 SoC. | ||
行 230: | 行 231: | ||
To build the sample application using sysbuild use the command: | To build the sample application using sysbuild use the command: | ||
- | < | + | < |
+ | west build -b esp32s3_luatos_core --sysbuild samples/ | ||
</ | </ | ||
行 239: | 行 240: | ||
Build directory structure created by sysbuild is different from traditional Zephyr build. Output is structured by the domain subdirectories: | Build directory structure created by sysbuild is different from traditional Zephyr build. Output is structured by the domain subdirectories: | ||
- | < | + | < |
+ | build/ | ||
├── hello_world | ├── hello_world | ||
│ | │ | ||
行 249: | 行 251: | ||
│ | │ | ||
└── domains.yaml | └── domains.yaml | ||
- | |||
</ | </ | ||
行 255: | 行 256: | ||
Note | Note | ||
- | With '' | + | With '' |
For more information about the system build please read the [[https:// | For more information about the system build please read the [[https:// | ||
- | ==== Manual build | + | ==== 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. | 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. | ||
行 271: | 行 272: | ||
Build and flash applications as usual (see [[https:// | Build and flash applications as usual (see [[https:// | ||
< | < | ||
+ | |||
# From the root of the zephyr repository | # From the root of the zephyr repository | ||
west build -b esp32s3_luatos_core/ | west build -b esp32s3_luatos_core/ | ||
- | |||
</ | </ | ||
行 279: | 行 280: | ||
If CH343 chip is disabled, You need use the following command to build: | If CH343 chip is disabled, You need use the following command to build: | ||
- | < | + | < |
+ | # From the root of the zephyr repository | ||
west build -b esp32s3_luatos_core/ | west build -b esp32s3_luatos_core/ | ||
- | |||
</ | </ | ||
- | The usual '' | + | The usual '' |
< | < | ||
+ | |||
# From the root of the zephyr repository | # From the root of the zephyr repository | ||
west build -b esp32s3_luatos_core/ | west build -b esp32s3_luatos_core/ | ||
west flash | west flash | ||
- | |||
</ | </ | ||
行 296: | 行 297: | ||
Open the serial monitor using the following command: | Open the serial monitor using the following command: | ||
- | < | + | < |
+ | west espressif monitor | ||
</ | </ | ||
行 303: | 行 304: | ||
After the board has automatically reset and booted, you should see the following message in the 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! esp32s3_luatos_core | Hello World! esp32s3_luatos_core | ||
- | |||
</ | </ | ||
- | ===== Debugging | + | |
+ | ===== Debugging ===== | ||
ESP32-S3 support on OpenOCD is available at [[https:// | ESP32-S3 support on OpenOCD is available at [[https:// | ||
行 318: | 行 320: | ||
Here is an example for building the [[https:// | Here is an example for building the [[https:// | ||
< | < | ||
+ | |||
# From the root of the zephyr repository | # From the root of the zephyr repository | ||
west build -b esp32s3_luatos_core/ | west build -b esp32s3_luatos_core/ | ||
west flash | west flash | ||
- | |||
</ | </ | ||
行 327: | 行 329: | ||
You can debug an application in the usual way. Here is an example for the [[https:// | You can debug an application in the usual way. Here is an example for the [[https:// | ||
< | < | ||
+ | |||
# From the root of the zephyr repository | # From the root of the zephyr repository | ||
west build -b esp32s3_luatos_core/ | west build -b esp32s3_luatos_core/ | ||
west debug | west debug | ||
- | |||
</ | </ | ||
- | ===== References | + | |
+ | ===== References ===== | ||
{{ : | {{ : |