4281f58229
The model ESP32P4 and ESP32C5 was unknown on version command in iperf example
add model ESP32P4 and ESP32C5
which prints out model names now by the knowed model
ESP32P4 = "ESP32-P4"
ESP32C5 = "ESP32-C5"
example app: iperf
before:
iperf> version
IDF Version:v5.4-dev-2744-g59e1838270-dirty
Chip info:
model:Unknown
cores:1
feature:/802.11bgn/BLE/External-Flash:8 MB
revision number:0
iperf>
after this add model is knowed now
iperf> version
IDF Version:v5.4-dev-2744-g59e1838270-dirty
Chip info:
model:ESP32-C5
cores:1
feature:/802.11bgn/BLE/External-Flash:8 MB
revision number:0
iperf>
Merges https://github.com/espressif/esp-idf/pull/14593
Console examples
(See the README.md file in the upper level 'examples' directory for more information about examples.)
Examples in this directory illustrate the usage of the Console Component to create an interactive shell on the ESP chip.
basic example
This example illustrates high-level Read-Eval-Print Loop API (esp_console_repl).
This example can be used with UART, USB_OTG or USB_SERIAL_JTAG peripherals. It works on all ESP chips.
It is the recommended starting point when getting familiar with console component.
advanced example
This example illustrates lower-level APIs for line editing and autocompletion (linenoise), argument parsing (argparse3) and command registration (esp_console).
These APIs allow for a lot of flexibility when building a console application, but require more code to be written.
While these APIs allow for a console to be implemented over various interfaces (UART, USB, TCP), this example can be used with UART, USB_OTG or USB_SERIAL_JTAG peripherals.