ESP32-H2-DEV-KIT-N4

From Waveshare Wiki
Jump to: navigation, search
ESP32-H2-DEV-KIT-N4
ESP32-C6-DEV-KIT-N800.jpg
with pre-soldered pin-header
ESP32-C6-DEV-KIT-N8201.jpg

ESP32-C6
USB Type-C
{{{name3}}}

{{{name4}}}

{{{name5}}}

Overview

Introduction

The ESP32-H2-DEV-KIT-N4 is a compact microcontroller development board with multiple peripheral interfaces.
In terms of hardware, it adopts the ESP32-H2-MINI-1 module with a RISC-V 32-bit single-core processor. It supports up to 96MHz clock frequency with built-in 320 KB SRAM, 128 KB ROM and 4 KB LP memory. Onboard CH343 UART and CH334 USB HUB chips, it supports USB and UART development at the same time via a USB-C port. Compatible with the pinout of the ESP32-H2-DevKitM-1 development board, it is more convenient to use and expand a variety of peripheral modules.
Comes with online examples and tutorials for the ESP-IDF development environment, so that you can easily and quickly get started and apply it to the product.

Feature

  • Adopts ESP32-H2-MINI-1 module with RISC-V 32-bit single-core processor, up to 96MHz main frequency.
  • Integrated 320 KB SRAM, 128 KB ROM, 4 KB LP memory, and 4MB Flash memory.
  • Integrated low-power Bluetooth (Bluetooth LE), and IEEE 802.15.4, with superior RF performance.
  • Type-C connector, easier to use.
  • Onboard CH343 and CH334 chips can meet the needs of USB and UART development via a Type-C interface.
  • Rich peripheral interfaces, compatible with the pinout of the ESP32-H2-DevKitM-1 development board, offer strong compatibility and expandability.
  • The castellated module allows soldering directly to carrier boards.
  • Supports a variety of low-power operating states, adjustable communication distance, data rate, and power consumption balance, to meet the power requirements of various application scenarios.

Function Block Diagram

ESP32-H2-DEV-KIT-N4-FD.jpg

Onboard Interface

ESP32-H2-DEV-KIT-N4-Onboard.jpg

Pinout Definition

ESP32-H2-DEV-KIT-N403.jpg

Dimensions

ESP32-H2-DEV-KIT-N4-dim.jpg

Working with ESP-IDF

The following development system defaults to Windows, and it is recommended to use the VSCode plug-in for development.

Develop with VSCode

Install VSCode

  • Open the VSCode website to download according to the corresponding system and system bits.

ESP32-C6-DEV-KIT-N8-01.png

  • After running the installation package, the rest can be installed by default, but here for a better experience, it is recommended to check the box in the 1, 2, and 3 items.
    • After enabling the 1 and 2 items, you can directly open the VScode by right-clicking the file or the directory to improve your experience.
    • After enabling the 3 items, you can directly select VSCode when choosing how to open,

ESP32-C6-DEV-KIT-N8-02.png

Install Espressif IDF Plug-in

  • Note: Currently the latest version of the plugin is V1.6.4, users can choose the same version as us for a consistent experience!
  • Open VSCode, use Shift+Ctrl+X to enter the plug-in manager.

ESP32-C6-DEV-KIT-N8-03.png

  • In the search bar, enter Espressif IDF to select the corresponding plug-in and click "Install".

ESP32-C6-DEV-KIT-N8-04.png
ESP32-C6-DEV-KIT-N8-05.png

  • Press F1 to input:
esp-idf: configure esp-idf extension

ESP32-C6-DEV-KIT-N8-06.png

  • Select express (this guide is for users who install it for the first time).

ESP32-C6-DEV-KIT-N8-07.png

  • Select download sever.

ESP32-C6-DEV-KIT-N8-08.png

  • Select the version of ESP-IDF you want to use now, we choose the latest V5.1.1 (note that only after V5.1 did ESP-IDF start to support ESP32-H2).

ESP32-C6-DEV-KIT-N8-09.png

  • The following two are the installation paths respectively for the ESP-IDF container directory and the ESP-IDF Tools directory.

ESP32-C6-DEV-KIT-N8-10.png

  • Note: If you have installed ESP-IDF before or failed to do so, please be sure to delete the file completely or create a new path without Chinese.
  • After configuring, click "Install" to download:

ESP32-C6-DEV-KIT-N8-19.png

  • Enter the download interface, and then it will automatically install the corresponding tools and environment, just wait for a second.

ESP32-C6-DEV-KIT-N8-11.png

  • After the installation is complete, you will enter the following interface, indicating that the installation is finished.

ESP32-C6-DEV-KIT-N8-12.png

Official Demo Usage GUIDE

Create Demo (Demo Example)

  • Press F1 to enter:
esp-idf:show examples projects

ESP32-C6-DEV-KIT-N8-13.png

  • Select the corresponding IDF version:

ESP32-C6-DEV-KIT-N8-14.png

  • Take the Hello World demo as an example:
    • ①Select the corresponding demo.
    • ②Its readme will state what chip the demo applies to (how the demo is used and the file structure is described below, omitted here).
    • ③Click to create the demo.

ESP32-C6-DEV-KIT-N8-15.png
Select the path to place the demo, and no folder with the same name as the demo is required.
ESP32-C6-DEV-KIT-N8-16.png

Modify COM Port

  • The corresponding COM ports are shown here, click to modify them.
  • Please select the COM ports according to your device. It is recommended to use the COM port corresponding to the USB connector. (You can view it from the device manager.)
  • In case of a download failure, please press the reset button for more than 1 second and wait for the PC to recognize the device again before downloading once more.

ESP32-C6-DEV-KIT-N8-17.png

  • Select the project or demo to use:

ESP32-C6-DEV-KIT-N8-18.png

  • Then we finish the modification of the COM ports.

Modify the Driver Object

  • The driver object is displayed here, and you can modify it by clicking on it.
  • Select the project or demo to use.

ESP32-C6-DEV-KIT-N8-20.png

  • Wait for a minute after clicking.

ESP32-C6-DEV-KIT-N8-21.png

  • Select the object we need to drive, which is our main chip ESP32H2.

ESP32-H2-DEV-KIT-N8-22.png

  • Choose the path to openocd, it doesn't affect us here, so let's just choose one at random.

ESP32-H2-DEV-KIT-N8-23.png

The Rest of the Status Bar

  • ①SDK configuration editor, supports modifying most functions of ESP-IDF.
  • ②All cleanup, and clear all compiled files.
  • ③Compile.
  • ④Current download mode, default is UART.
  • ⑤Program the current firmware, please do it after compiling.
  • ⑥Open the serial port monitor, which is used to view the serial port information.
  • ⑦All-in-one button, compile, burn, open the serial monitor (most commonly used for debugging).
ESP32-C6-DEV-KIT-N8-24.png

Compile, Program, Serial Port Monitoring

  • Click on the all-in-one button we described before to compile, program, and open the serial port monitor.
ESP32-H2-DEV-KIT-N8-25.png
  • It may take a long time to compile especially for the first time.
ESP32-H2-DEV-KIT-N8-26.png
  • During this process, the ESP-IDF may take up a lot of CPU resources, so it may cause the system to lag.
  • If it is the first time to burn the program for a new project, you will need to select the download method, and select UART.
ESP32-H2-DEV-KIT-N8-27.png
  • This can also be changed later in the Download Methods section (click on it to bring up the options).
ESP32-H2-DEV-KIT-N8-28.png
  • As it comes with the onboard automatic download circuit, there is no need for manual operation to download automatically.
ESP32-H2-DEV-KIT-N8-29.png
  • After successful download, automatically enter the serial monitor, you can see the chip output the corresponding information and be prompted to restart after 10S.
ESP32-H2-DEV-KIT-N8-30.png

Demo Example

Hello World

The official example path: get-started -> hello_world.
The example effect: Output Hello World! on the TERMINAL window every 10s.

    Software Operation
  • Create the official example "hello_world" according to the above tutorial. (Create Example)
  • The demo is compatible with ESP32-H2. You can directly use it with no need to modify the demo.
  • Modify the COM port and the driver object ( it is recommended to prioritize the use of USB corresponding to the COM port, can be viewed through the device manager), click on the compile and burn to run the demo.

ESP32-H2-DEV-KIT-N8-30.png

GPIO

Official path: peripherals -> gpio -> generic_gpio.
Sample effect: LED blinks at 1-second intervals.

    Hardware Connection
ESP32-H2 LED
GPIO18(or GPIO19) LED+
GND LED-
    Software Operation
  • Follow the tutorial above to create the official example generic_gpio. (Create Example)
  • The demo is compatible with ESP32-H2 and can be used without modifying the demo content.
  • Modify the COM port and the driver object (it is recommended to use the COM port corresponding to USB first, you can check it through the device manager), click compile and burn to run the demo.
ESP32-H2-DEV-KIT-N8-37.png
  • Go to the demo macro definition location to see what GPIOs are handled.
ESP32-H2-DEV-KIT-N8-38.png
  • Right-click and go to the GPIO definition location.
ESP32-H2-DEV-KIT-N8-39.png
  • The actual GPIOs are GPIO8, GPIO9.
ESP32-H2-DEV-KIT-N8-40.png

RGB

Official example path: get-started -> blink.
Sample effect: onboard RGB beads blink at 1-second intervals.

    Software Operation
  • Follow the tutorial above to create the official example blink. (Create Example)
  • The demo is compatible with ESP32-H2 and can be used without modifying the demo content.
  • Modify the COM port and the driver object (it is recommended to prioritize the COM port corresponding to USB, which can be viewed through the device manager), click compile and burn to run the demo.
ESP32-H2-DEV-KIT-N8-41.png

UART

Official example path: peripherals -> uart-> uart_async_rxtxtasks
Example effect: shorting GPIO4 and GPIO5 to send/receive UART data.

    Hardware Connection
ESP32-H2 ESP32-H2 (the same one)
GPIO4 GPIO5
    Software Operation
  • Create the official example uart_async_rxtxtasks according to the tutorial above. (Create Example)
  • The demo is compatible with ESP32-H2 and can be used without modifying the demo content.
  • Modify the COM port and driver object (it is recommended to prioritize the COM port corresponding to USB, which can be viewed through the device manager), click compile and burn to run the demo.

ESP32-H2-DEV-KIT-N8-77.png

  • Hardware connection according to the GPIO used.

ESP32-H2-DEV-KIT-N8-78.png

  • You can go to the definition file to see the actual GPIOs used (check GPIO_NUM_4 -> Right click -> Go to Definition).

ESP32-H2-DEV-KIT-N8-79.png

I2C

The official example path: peripherals -> lcd-> i2c_oled.
Example effect: turns on the 0.96-inch OLED (A) and displays a character.

    Hardware Connection
0.96inch OLED (A) ESP32-H2
VCC 3V3
GND GND
DIN GPIO3
CLK GPIO4
CS GND
D/C GND
RES GPIO9
    Software Operation

ESP32-H2-DEV-KIT-N8-31.png

  • Adapts to 0.96-inch OLED (A), defines RES pin as GPIO9.

ESP32-H2-DEV-KIT-N8-32.png

  • Modify the COM port and the driver object ( it is recommended to prioritize the use of USB corresponding to the COM port, which can be viewed through the device manager), click on the compile and burn to run the demo.

ESP32-H2-DEV-KIT-N8-35.png

  • The effect is as shown below:

ESP32-H2-DEV-KIT-N8-33.png

  • You can view the actual use of GPIO:

ESP32-H2-DEV-KIT-N8-34.png

SPI

The path of the official example: peripherals -> spi_master-> lcd.
The example effect: dynamic displaying picture effect on the 2.4inch LCD Module.

    Hardware Connection
2.4inch LCD Module ESP32-H2
VCC 3V3
GND GND
DIN GPIO5
CLK GPIO4
CS GPIO1
D/C GPIO10
RES GPIO11
BL GPIO12
    Software Operation
  • Right-click on the VScode icon and run VScode as administrator:

ESP32-C6-DEV-KIT-N8-035.png

ESP32-H2-DEV-KIT-N8-36.png

  • Jump to a defined position.

ESP32-H2-DEV-KIT-N8-36.png

  • Currently using ESP32-H2, shield other chip definitions.

ESP32-C6-DEV-KIT-N8-036.png

  • And macro-define ESP32-C6, CONFIG_IDF_TARGET_ESP32H2.
//#define CONFIG_IDF_TARGET_ESP32 1
#define CONFIG_IDF_TARGET_ESP32H2 1

ESP32-H2-DEV-KIT-N8-42.png

  • Wait for it to read the ID.

ESP32-H2-DEV-KIT-N8-43.png

  • Add reading delay to prevent reading failure.
vTaskDelay(100 / portTICK_PERIOD_MS);

ESP32-H2-DEV-KIT-N8-44.png

  • Modify the backlight:

ESP32-H2-DEV-KIT-N8-45.png

  • Modify it as gpio_set_level(PIN_NUM_BCKL, 1);

ESP32-H2-DEV-KIT-N8-46.png

  • Modify the COM port and the driver object (it is recommended to prioritize the use of USB corresponding to the COM port, which can be viewed through the device manager), click on the compile and burn to run the demo.

ESP32-H2-DEV-KIT-N8-47.png

  • The effect is as shown below:

ESP32-H2-DEV-KIT-N8-48.png

Bluetooth

Official sample path: Bluetooth -> bluedroid -> ble -> gatt_server.
Example effect: ESP32-H2 and cell phone Bluetooth debugging assistant for data transmission.

    Software Operation
  • Install the Bluetooth debugging assistant on your phone (or you can use other Bluetooth debugging tools).
  • Follow the tutorial above to create the official example gatt_server. (Example)
  • The demo is compatible with ESP32-H2 and can be used without modifying the demo content.
  • Bluetooth name and UUID, Bluetooth name is ESP_GATTS_DEMO.

ESP32-C6-DEV-KIT-N4-50.png

  • Modify the COM port and the driver object (it is recommended to prioritize the use of USB corresponding to the COM port, which can be viewed through the device manager), and click on the compile, and burn to run the demo.

ESP32-C6-DEV-KIT-N4-51.png

  • Connect to the Bluetooth device named ESP_GATTS_DEMO using the nRF Connect app on your mobile device.
  • The successful connection is shown below:

ESP32-H2-DEV-KIT-N4-51.png

  • Based on the UUID value in the demo, select one of the two servers for upstream transmission.
  • The ESP32-H2 receives data:

ESP32-H2-DEV-KIT-N4-54.png

Zigbee

  • Official example 1 path: Zigbee -> light_sample -> HA_on_off_switch.
  • Official example 2 path: Zigbee -> light_sample -> HA_on_off_light.
  • Example effect: two ESP32-H2, use the BOOT button of one of them (burn HA_on_off_switch demo) to control the RGB light beads of the other one.
  • Note: Please burn the HA_on_off_switch demo to one piece first, and then burn the HA_on_off_light program to the other piece.
    Software Operation 1
  • Create the official example HA_on_off_switch according to the tutorial above. (Create Example)
  • The demo is compatible with ESP32-H2 and can be used without modifying the demo content.
  • Modify the COM port and the driver object (it is recommended to use the COM port corresponding to USB in preference, which can be viewed through the device manager), click compile, and burn to run the demo.

ESP32-C6-DEV-KIT-N4-66.png

    Software Operation 2
  • Follow the tutorial above to create the official example HA_on_off_light. (Create Example)
  • The demo is compatible with ESP32-H2 and can be used without modifying the demo content.
  • Modify the COM port and driver object (please use the COM port corresponding to UART), click compile and burn to run the demo (you need to wait for a moment for the two chips to establish a connection).
ESP32-C6-DEV-KIT-N4-70.png
  • After connecting, the corresponding key demo and LED demo will print the related data.
ESP32-C6-DEV-KIT-N4-71.png
  • If the device remains unconnected, it may be due to residual network information on the device, so you can erase the device information (Erase Tutorial) and reorganize the network.

JTAG Debug

     Software Operation
  • Create a debugging example, this example uses the official example hello_world. (Create Example)
  • Modify the launch.json file.

ESP32-H2-DEV-KIT-N8-72.png

  • Input the following content:
{
 "version": "0.2.0",
 "configurations": [
   {
     "name": "GDB",
     "type": "cppdbg",
     "request": "launch",
     "MIMode": "gdb",
     "miDebuggerPath": "${command:espIdf.getXtensaGdb}",
     "program": "${workspaceFolder}/build/${command:espIdf.getProjectName}.elf",
     "windows": {
       "program": "${workspaceFolder}\\build\\${command:espIdf.getProjectName}.elf"
     },
     "cwd": "${workspaceFolder}",
     "environment": [{ "name": "PATH", "value": "${config:idf.customExtraPaths}" }],
     "setupCommands": [
       { "text": "target remote :3333" },
       { "text": "set remote hardware-watchpoint-limit 2"},
       { "text": "mon reset halt" },
       { "text": "thb app_main" },
       { "text": "flushregs" }
     ],
     "externalConsole": false,
     "logging": {
       "engineLogging": true
     }
   }
 ]

ESP32-H2-DEV-KIT-N8-73.png

  • The demo is compatible with ESP32-H2 and can be used without modifying the demo content.
  • Modify the COM port and the driver object (Please use the USB interface; the UART interface does not support JTAG debugging. The corresponding COM port can be checked through the Device Manager.), click compile and burn to run the demo.

ESP32-H2-DEV-KIT.png

  • Press F1 and input:
ESP-IDF:Device configuration

ESP32-H2-DEV-KIT-N8-75.png

  • Select OpenOcd Config Files.

ESP32-H2-DEV-KIT-N8-76.png

  • Type board/esp32h2-builtin.cfg (if this is the default, just enter)
board/esp32h2-builtin.cfg

ESP32-C6-DEV-KIT-N4-77.png

  • Stretch the width of the window until [OpenOCD Server] is displayed at the bottom.

ESP32-C6-DEV-KIT-N4-78.png

  • Click [OpenOCD Server] and select Start OpenOCD.

ESP32-C6-DEV-KIT-N4-79.png

  • Successfully opened as follows:

ESP32-H2-DEV-KIT-N8-80.png

  • Go to the debug function and click Debug:

ESP32-H2-DEV-KIT-N8-81.png

  • Successfully enter the debugging interface:

ESP32-H2-DEV-KIT-N8-82.png

Erase Device Flash

  • Unpack the software resource package (Flash debugging software).
  • Open flash_download_tool_3.9.5.exe software, select ESP32-H2 and UART.

ESP32-C6-DEV-KIT-H2-83.png

  • Select the UART port number, and click START (not select any bin file).

ESP32-C6-DEV-KIT-H2-84.png

  • After programming, click on "ERASE".

ESP32-C6-DEV-KIT-H2-85.png

  • Waiting for Erase to Finish.

ESP32-C6-DEV-KIT-H2-86.png

Working with Arduino

Please note that Arduino 3.0.0-alpha is based on ESP-IDF v5.1, which is quite different from the previous ESP-IDF V4.X. The original program may need to be adjusted after the following operations.

Environment Set-up

ESP32-C6-DEV-KIT-N8-Arduino01.png

  • Enter Arduino IDE after installation.

ESP32-C6-DEV-KIT-N8-Arduino02.png

  • Enter Preferences.

ESP32-C6-DEV-KIT-N8-Arduino03.png

  • Add JSON link:
https://espressif.github.io/arduino-esp32/package_esp32_dev_index.json

ESP32-C6-DEV-KIT-N8-Arduino04.png
ESP32-C6-DEV-KIT-N8-Arduino05.png

  • Modify the project file folder as C:\Users\Waveshare\AppData\Local\Arduino15\packages (Waveshare is the username).

ESP32-C6-DEV-KIT-N8-Arduino06.png

  • Enter the development board manager, search for "esp32", select version 3.0.0-alpha3 under "esp32 by Espressif Systems" below, and click to install. (If installation fails, try using a mobile hotspot.)

ESP32-C6-DEV-KIT-N8-Arduino07.png
ESP32-C6-DEV-KIT-N8-Arduino08.png

  • Restart the Arduino IDE after installation, and then you can use it now.

ESP32-C6-DEV-KIT-N8-Arduino09.png

If the installation fails

  • Failed to install version 3.0.0-alpha3:

ESP32-C6-DEV-KIT-N8-install.png

ESP32-C6-DEV-KIT-N8-install02.png

  • Click on the path "C:\Users\Waveshare\AppData\Local\Arduino15\staging\packages" (where Waveshare is the user name of the computer, and you need to turn on Show Hidden Files).

ESP32-C6-DEV-KIT-N8-install03.png

  • Unzip the downloaded files to the packages file folder:

ESP32-C6-DEV-KIT-N8-install04.png

  • Install it again:

ESP32-C6-DEV-KIT-N8-Arduino07.png

  • Restart the Arduino IDE after installation and you're ready to go!

ESP32-C6-DEV-KIT-N8-Arduino09.png

Create Example

  • After changing the project folder above to c:\Users\Waveshare\AppData\Local\Arduino15\packages, you can create demos using the examples in the project folder under the files.

ESP32-C6-DEV-KIT-N8-Arduino10.png

  • The following is the RGB flashing example (File -> Sketchbook -> esp32 -> hardware -> esp32 -> 3.0.0-alpha3 -> libraries -> ESP32 -> examples -> BlinkRGB under GPIO).

ESP32-C6-DEV-KIT-N8-Arduino11.png

  • Select the development board and port.

ESP32-C6-DEV-KIT-N8-Arduino12.png

  • Search esp32h2, select ESP32H2 Dev Module, and the ports to download.

ESP32-H2-DEV-KIT-N8-Arduino13.png

  • After selecting, click to upload and Arduino IDE will start to compile and program the demo.

ESP32-H2-DEV-KIT-N8-Arduino14.png

  • After uploading, you can see the effect on the development board.

ESP32-H2-DEV-KIT-N8-Arduino15.png

Resource

Software

Compile

CH343

UART

Flash

Bluetooth Debug

Schematic

Datasheet

ESP32-H2

CH343

Official Document

ESP32 Officail Document

FAQ

 Answer:

Please select the driver object again and compile it again.
ESP32-C6-DEV-KIT-N8-20.png

ESP32-C6-DEV-KIT-N8-22.png

{{{5}}}


 Answer:

Method 1: Press the reset button for more than 1 second, wait for the PC to recognize the device again, and then proceed with the download.
Method 2: You can long-press the BOOT button, simultaneously press the RESET button, then release the RESET button, and finally release the BOOT button. This will put the module into download mode and can resolve most download issues.

{{{5}}}


 Answer:

In VSCode, click the shortcut F1, and search for Espressif IDF, you will find that it is designated as an untrusted extension, set it as trusted.

{{{5}}}


 Answer:

It has no effect on program burning. If you want to use the corresponding COM port of USB after the pop-up of an unrecognized USB device, please disconnect the cable from the computer and reconnect the device. You can also erase the demo by software or instruction, after erasing the demo, the USB port will be recognized again. It can also be achieved by holding down the reset button.

{{{5}}}


 Answer:

Please select the COM port and driver object again after switching ESP, then compile and burn.

{{{5}}}


 Answer:

Check whether the power supply voltage for the USB port is less than 5V, in general, if it is 4.9V or more, the module's two USB ports can be used normally. If it is lower than 4.9V, the power supply may be insufficient and the USB port may disconnect. In this case, you should replace it with a USB port with sufficient voltage.

{{{5}}}


 Answer:

This may be because this device has residual information about other networks. You can erase the device information (#Erase Device Flash) and then reorganize the network.

{{{5}}}


 Answer:

Please select the COM port corresponding to UART on both boards and then burn the program.

{{{5}}}


 Answer:

Close OpenOCD below and reopen it.

{{{5}}}


Support



Technical Support

If you need technical support or have any feedback/review, please click the Submit Now button to submit a ticket, Our support team will check and reply to you within 1 to 2 working days. Please be patient as we make every effort to help you to resolve the issue.
Working Time: 9 AM - 6 PM GMT+8 (Monday to Friday)