mirror of
https://github.com/espressif/esp-idf.git
synced 2026-05-19 23:45:28 +02:00
docs: update getting started and frontpage docs for C6
This commit is contained in:
Marius Vikhammer
@@ -5,7 +5,7 @@ Establish Serial Connection with {IDF_TARGET_NAME}
|
||||
|
||||
.. only:: not SOC_USB_OTG_SUPPORTED and not SOC_USB_SERIAL_JTAG_SUPPORTED
|
||||
|
||||
Establishing a serial connection with the {IDF_TARGET_NAME} target device could be done using a USB-to-UART bridge.
|
||||
Establishing a serial connection with the {IDF_TARGET_NAME} target device could be done using a USB-to-UART bridge.
|
||||
|
||||
.. only:: SOC_USB_OTG_SUPPORTED or SOC_USB_SERIAL_JTAG_SUPPORTED
|
||||
|
||||
@@ -33,7 +33,7 @@ Some development boards have the USB-to-UART bridge installed. If a board does n
|
||||
default_fontsize = 16
|
||||
|
||||
# labels of diagram nodes
|
||||
PC [label="Personal\n Computer"];
|
||||
PC [label="Personal\n Computer"];
|
||||
CHIP [label="{IDF_TARGET_NAME}", width=120];
|
||||
DUMMY [shape=none, width=1]
|
||||
|
||||
@@ -71,8 +71,8 @@ For boards with an installed USB-to-UART bridge, the connection between the pers
|
||||
default_fontsize = 16
|
||||
|
||||
# labels of diagram nodes
|
||||
PC [label="Personal\nComputer"];
|
||||
BRIDGE [label="USB-to-UART\n Bridge"];
|
||||
PC [label="Personal\nComputer"];
|
||||
BRIDGE [label="USB-to-UART\n Bridge"];
|
||||
CHIP [label="{IDF_TARGET_NAME}", width=120];
|
||||
|
||||
# node connections
|
||||
@@ -106,8 +106,8 @@ Sometimes the USB-to-UART bridge is external. This is often used in small develo
|
||||
default_fontsize = 16
|
||||
|
||||
# labels of diagram nodes
|
||||
PC [label="Personal\n Computer"];
|
||||
BRIDGE [label="USB-to-UART\n Bridge", width=180];
|
||||
PC [label="Personal\n Computer"];
|
||||
BRIDGE [label="USB-to-UART\n Bridge", width=180];
|
||||
CHIP [label="{IDF_TARGET_NAME}", width=120];
|
||||
DUMMY [shape=none, width=1]
|
||||
|
||||
@@ -132,18 +132,18 @@ Sometimes the USB-to-UART bridge is external. This is often used in small develo
|
||||
CHIP; DUMMY;
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
|
||||
.. only:: SOC_USB_OTG_SUPPORTED or SOC_USB_SERIAL_JTAG_SUPPORTED
|
||||
|
||||
Flash using USB
|
||||
---------------
|
||||
|
||||
|
||||
For the {IDF_TARGET_NAME}, the USB peripheral is available, allowing you to flash the binaries without the need for an external USB-to-UART bridge.
|
||||
|
||||
{IDF_TARGET_USB_PIN_DM:default="Not Updated!", esp32c3="GPIO18", esp32s3="GPIO19", esp32s2="GPIO19"}
|
||||
{IDF_TARGET_USB_PIN_DP:default="Not Updated!", esp32c3="GPIO19", esp32s3="GPIO20", esp32s2="GPIO20"}
|
||||
|
||||
{IDF_TARGET_USB_PIN_DM:default="Not Updated!", esp32c3="GPIO18", esp32s3="GPIO19", esp32s2="GPIO19", esp32c6="GPIO12"}
|
||||
{IDF_TARGET_USB_PIN_DP:default="Not Updated!", esp32c3="GPIO19", esp32s3="GPIO20", esp32s2="GPIO20", esp32c6="GPIO13"}
|
||||
|
||||
The USB on the {IDF_TARGET_NAME} uses the **{IDF_TARGET_USB_PIN_DP}** for **D+** and **{IDF_TARGET_USB_PIN_DM}** for **D-**.
|
||||
|
||||
.. only:: SOC_USB_SERIAL_JTAG_SUPPORTED
|
||||
@@ -182,7 +182,7 @@ For devices downloaded using a USB-to-UART bridge, you can run the following com
|
||||
You can change the flasher baud rate by replacing ``BAUD`` with the baud rate you need. The default baud rate is ``460800``.
|
||||
|
||||
.. note::
|
||||
|
||||
|
||||
If the device does not support the auto download mode, you need to get into the download mode manually. To do so, press and hold the ``BOOT`` button and then press the ``RESET`` button once. After that release the ``BOOT`` button.
|
||||
|
||||
Check port on Windows
|
||||
|
||||
@@ -6,7 +6,7 @@ Flashing Troubleshooting
|
||||
Failed to Connect
|
||||
-----------------
|
||||
|
||||
{IDF_TARGET_STRAP_GPIO:default="[NEEDS TO BE UPDATED]", esp32="GPIO0", esp32s2="GPIO0", esp32s3="GPIO0", esp32c2="GPIO9", esp32c3="GPIO9"}
|
||||
{IDF_TARGET_STRAP_GPIO:default="[NEEDS TO BE UPDATED]", esp32="GPIO0", esp32s2="GPIO0", esp32s3="GPIO0", esp32c2="GPIO9", esp32c3="GPIO9", esp32c6="GPIO9"}
|
||||
|
||||
If you run the given command and see errors such as "Failed to connect", there might be several reasons for this. One of the reasons might be issues encountered by ``esptool.py``, the utility that is called by the build system to reset the chip, interact with the ROM bootloader, and flash firmware. One simple solution to try is to manually reset as described below. If it does not help, you can find more details about possible issues in the `esptool troubleshooting <https://docs.espressif.com/projects/esptool/en/latest/esp32/troubleshooting.html>`_ page.
|
||||
|
||||
|
||||
@@ -59,6 +59,15 @@ Introduction
|
||||
* Multiple peripherals
|
||||
* Intended for simple, high-volume IoT applications
|
||||
|
||||
.. only:: esp32c6
|
||||
|
||||
* Wi-Fi 6 (2.4 GHz band)
|
||||
* Bluetooth Low Energy
|
||||
* 802.15.4 Thread/Zigbee
|
||||
* High performance 32-bit RISC-V single-core processor
|
||||
* Multiple peripherals
|
||||
* Built-in security hardware
|
||||
|
||||
Powered by 40 nm technology, {IDF_TARGET_NAME} provides a robust, highly integrated platform, which helps meet the continuous demands for efficient power usage, compact design, security, high performance, and reliability.
|
||||
|
||||
Espressif provides basic hardware and software resources to help application developers realize their ideas using the {IDF_TARGET_NAME} series hardware. The software development framework by Espressif is intended for development of Internet-of-Things (IoT) applications with Wi-Fi, Bluetooth, power management and several other system features.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
{IDF_TARGET_CORE_NUM:default="2", esp32s2="1", esp32c3="1", esp32c2="1"}
|
||||
{IDF_TARGET_CORE_NUM:default="2", esp32s2="1", esp32c3="1", esp32c2="1", esp32c6="1"}
|
||||
|
||||
{IDF_TARGET_FEATURES:default="[NEEDS TO BE UPDATED]", esp32="WiFi/BT/BLE, silicon revision 1, 2MB external flash", esp32s2="WiFi, silicon revision 0, 2MB external flash", esp32s3="This is esp32s3 chip with 2 CPU core(s), WiFi/BLE, silicon revision 0, 2MB external flash", esp32c2="WiFi/BLE, silicon revision 0, 2MB external flash", esp32c3="WiFi/BLE, silicon revision 0, 2MB external flash"}
|
||||
{IDF_TARGET_FEATURES:default="[NEEDS TO BE UPDATED]", esp32="WiFi/BT/BLE, silicon revision 1, 2MB external flash", esp32s2="WiFi, silicon revision 0, 2MB external flash", esp32s3="This is esp32s3 chip with 2 CPU core(s), WiFi/BLE, silicon revision 0, 2MB external flash", esp32c2="WiFi/BLE, silicon revision 0, 2MB embedded flash", esp32c3="WiFi/BLE, silicon revision 0, 2MB external flash", esp32c6="WiFi/BLE, silicon revision v0.0, 2MB external flash"}
|
||||
|
||||
{IDF_TARGET_HEAP_SIZE:default="[NEEDS TO BE UPDATED]", esp32="298968", esp32s2="253900", esp32s3="390684", esp32c2="203888", esp32c3="337332"}
|
||||
{IDF_TARGET_HEAP_SIZE:default="[NEEDS TO BE UPDATED]", esp32="298968", esp32s2="253900", esp32s3="390684", esp32c2="203888", esp32c3="337332", esp32c6="337332"}
|
||||
|
||||
Build the Project
|
||||
=================
|
||||
@@ -271,6 +271,57 @@ When flashing, you will see the output log similar to the following:
|
||||
Done
|
||||
|
||||
|
||||
.. only:: esp32c6
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
...
|
||||
esptool esp32c6 -p /dev/ttyUSB0 -b 460800 --before=default_reset --after=hard_reset --no-stub write_flash --flash_mode dio --flash_freq 80m --flash_size 2MB 0x0 bootloader/bootloader.bin 0x10000 hello_world.bin 0x8000 partition_table/partition-table.bin
|
||||
esptool.py v4.3
|
||||
Serial port /dev/ttyUSB0
|
||||
Connecting....
|
||||
Chip is ESP32-C6 (revision v0.0)
|
||||
Features: WiFi 6, BT 5
|
||||
Crystal is 40MHz
|
||||
MAC: 60:55:f9:f6:01:38
|
||||
Changing baud rate to 460800
|
||||
Changed.
|
||||
Enabling default SPI flash mode...
|
||||
Configuring flash size...
|
||||
Flash will be erased from 0x00000000 to 0x00004fff...
|
||||
Flash will be erased from 0x00010000 to 0x00028fff...
|
||||
Flash will be erased from 0x00008000 to 0x00008fff...
|
||||
Erasing flash...
|
||||
Took 0.17s to erase flash block
|
||||
Writing at 0x00000000... (5 %)
|
||||
Writing at 0x00000c00... (23 %)
|
||||
Writing at 0x00001c00... (47 %)
|
||||
Writing at 0x00003000... (76 %)
|
||||
Writing at 0x00004000... (100 %)
|
||||
Wrote 17408 bytes at 0x00000000 in 0.5 seconds (254.6 kbit/s)...
|
||||
Hash of data verified.
|
||||
Erasing flash...
|
||||
Took 0.85s to erase flash block
|
||||
Writing at 0x00010000... (1 %)
|
||||
Writing at 0x00014c00... (20 %)
|
||||
Writing at 0x00019c00... (40 %)
|
||||
Writing at 0x0001ec00... (60 %)
|
||||
Writing at 0x00023c00... (80 %)
|
||||
Writing at 0x00028c00... (100 %)
|
||||
Wrote 102400 bytes at 0x00010000 in 3.2 seconds (253.5 kbit/s)...
|
||||
Hash of data verified.
|
||||
Erasing flash...
|
||||
Took 0.04s to erase flash block
|
||||
Writing at 0x00008000... (33 %)
|
||||
Writing at 0x00008400... (66 %)
|
||||
Writing at 0x00008800... (100 %)
|
||||
Wrote 3072 bytes at 0x00008000 in 0.1 seconds (269.0 kbit/s)...
|
||||
Hash of data verified.
|
||||
|
||||
Leaving...
|
||||
Hard resetting via RTS pin...
|
||||
|
||||
|
||||
If there are no issues by the end of the flash process, the board will reboot and start up the “hello_world” application.
|
||||
|
||||
If you'd like to use the Eclipse or VS Code IDE instead of running ``idf.py``, check out `Eclipse Plugin <https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md>`_, `VSCode Extension <https://github.com/espressif/vscode-esp-idf-extension/blob/master/docs/tutorial/install.md>`_.
|
||||
|
||||
Reference in New Issue
Block a user