boards/heltec/heltec_wifi_lora32_v2/doc/index.html · boards/heltec/heltec_wifi_lora32_v2/doc/index.rst 공식 원문 ↗

Zephyr 3.7.0 · Boards · Heltec ESP32

Heltec WiFi LoRa 32 V2

ESP32, LoRa와 OLED를 통합한 classic IoT development board입니다.

Official pathboards/heltec/heltec_wifi_lora32_v2/doc/index.html
Source fileboards/heltec/heltec_wifi_lora32_v2/doc/index.rst
Source versionZephyr 3.7.0
TranslationFull · reviewed

본문 기준: Zephyr 3.7.0 LTS3 · 이후 유지보수 패치는 별도입니다.

Part 1

요약·해설

WiFi LoRa 32 V2는 ESP32, SX1276/78 LoRa, battery management와 128×64 OLED를 통합합니다.

SoC

ESP32 · dual-core

Radio

Wi-Fi · BLE · LoRa

Display

SSD1306 · 128×64

Part 2

접을 수 있는 영어 원문 전체

영어 원문 전체 펼치기
원문 SHA-256 90514E53F90214A9887073D5D5F374E1B1F496A2279495AF3D51D174EF6267D5
.. _heltec_wifi_lora32_v2:

Heltec WiFi LoRa 32 (V2)
########################

Overview
********

Heltec WiFi LoRa 32 is a classic IoT dev-board designed & produced by Heltec Automation(TM), it's a highly
integrated product based on ESP32 + SX127x, it has Wi-Fi, BLE, LoRa functions, also Li-Po battery management
system, 0.96" OLED are also included. [1]_

The features include the following:

- Microprocessor: ESP32 (dual-core 32-bit MCU + ULP core)
- LoRa node chip SX1276/SX1278
- Micro USB interface with a complete voltage regulator, ESD protection, short circuit protection,
  RF shielding, and other protection measures
- Onboard SH1.25-2 battery interface, integrated lithium battery management system
- Integrated WiFi, LoRa, Bluetooth three network connections, onboard Wi-Fi, Bluetooth dedicated 2.4GHz
  metal 3D antenna, reserved IPEX (U.FL) interface for LoRa use
- Onboard 0.96-inch 128*64 dot matrix OLED display
- Integrated CP2102 USB to serial port chip

System requirements
*******************

Prerequisites
=============

Espressif HAL requires WiFi and Bluetooth binary blobs in order work. Run the command
below to retrieve those files.

.. code-block:: console

   west blobs fetch hal_espressif

.. note::

   It is recommended running the command above after :file:`west update`.

Building & Flashing
*******************

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.

.. note::

   Simple boot does not provide any security features nor OTA updates.

MCUboot bootloader
==================

User may choose to use MCUboot bootloader instead. In that case the bootloader
must be build (and flash) at least once.

There are two options to be used when building an application:

1. Sysbuild
2. Manual build

.. note::

   User can select the MCUboot bootloader by adding the following line
   to the board default configuration file.

   .. code:: cfg

      CONFIG_BOOTLOADER_MCUBOOT=y

Sysbuild
========

The sysbuild makes possible to build and flash all necessary images needed to
bootstrap the board with the ESP32 SoC.

To build the sample application using sysbuild use the command:

.. zephyr-app-commands::
   :tool: west
   :app: samples/hello_world
   :board: heltec_wifi_lora32_v2
   :goals: build
   :west-args: --sysbuild
   :compact:

By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
images. But it can be configured to create other kind of images.

Build directory structure created by sysbuild is different from traditional
Zephyr build. Output is structured by the domain subdirectories:

.. code-block::

  build/
  ├── hello_world
  │   └── zephyr
  │       ├── zephyr.elf
  │       └── zephyr.bin
  ├── mcuboot
  │    └── zephyr
  │       ├── zephyr.elf
  │       └── zephyr.bin
  └── domains.yaml

.. note::

   With ``--sysbuild`` option the bootloader will be re-build and re-flash
   every time the pristine build is used.

For more information about the system build please read the :ref:`sysbuild` documentation.

Manual build
============

During the development cycle, it is intended to build & flash as quickly possible.
For that reason, images can be build one at a time using traditional build.

The instructions following are relevant for both manual build and sysbuild.
The only difference is the structure of the build directory.

.. note::

   Remember that bootloader (MCUboot) needs to be flash at least once.

Build and flash applications as usual (see :ref:`build_an_application` and
:ref:`application_run` for more details).

.. zephyr-app-commands::
   :zephyr-app: samples/hello_world
   :board: heltec_wifi_lora32_v2/esp32/procpu
   :goals: build

The usual ``flash`` target will work with the ``heltec_wifi_lora32_v2`` board
configuration. Here is an example for the :ref:`hello_world`
application.

.. zephyr-app-commands::
   :zephyr-app: samples/hello_world
   :board: heltec_wifi_lora32_v2/esp32/procpu
   :goals: flash

Open the serial monitor using the following command:

.. code-block:: shell

   west espressif monitor

After the board has automatically reset and booted, you should see the following
message in the monitor:

.. code-block:: console

   ***** Booting Zephyr OS vx.x.x-xxx-gxxxxxxxxxxxx *****
   Hello World! heltec_wifi_lora32_v2

Debugging
*********

As with much custom hardware, the ESP32 modules require patches to
OpenOCD that are not upstreamed yet. Espressif maintains their own fork of
the project. The custom OpenOCD can be obtained at `OpenOCD ESP32`_

The Zephyr SDK uses a bundled version of OpenOCD by default. You can overwrite that behavior by adding the
``-DOPENOCD=<path/to/bin/openocd> -DOPENOCD_DEFAULT_PATH=<path/to/openocd/share/openocd/scripts>``
parameter when building.

Here is an example for building the :ref:`hello_world` application.

.. zephyr-app-commands::
   :zephyr-app: samples/hello_world
   :board: heltec_wifi_lora32_v2/esp32/procpu
   :goals: build flash
   :gen-args: -DOPENOCD=<path/to/bin/openocd> -DOPENOCD_DEFAULT_PATH=<path/to/openocd/share/openocd/scripts>

You can debug an application in the usual way. Here is an example for the :ref:`hello_world` application.

.. zephyr-app-commands::
   :zephyr-app: samples/hello_world
   :board: heltec_wifi_lora32_v2/esp32/procpu
   :goals: debug

Utilizing Hardware Features
***************************

Onboard OLED display
====================

The onboard OLED display is of type ``ssd1306``, has 128*64 pixels and is
connected via I2C. It can therefore be used by enabling the
:ref:`ssd1306_128_shield` as shown in the following for the :zephyr:code-sample:`lvgl` sample:

.. zephyr-app-commands::
   :zephyr-app: samples/subsys/display/lvgl
   :board: heltec_wifi_lora32_v2/esp32/procpu
   :shield: ssd1306_128x64
   :goals: flash

References
**********

- `Heltec WiFi LoRa (v2) Pinout Diagram <https://resource.heltec.cn/download/WiFi_LoRa_32/WIFI_LoRa_32_V2.pdf>`_
- `Heltec WiFi LoRa (v2) Schematic Diagrams <https://resource.heltec.cn/download/WiFi_LoRa_32/V2>`_
- `ESP32 Toolchain <https://docs.espressif.com/projects/esp-idf/en/v4.2/esp32/api-guides/tools/idf-tools.html#xtensa-esp32-elf>`_
- `esptool documentation <https://github.com/espressif/esptool/blob/master/README.md>`_
- `OpenOCD ESP32 <https://github.com/espressif/openocd-esp32/releases>`_

.. [1] https://heltec.org/project/wifi-lora-32/

Part 3

한국어 전문 번역

개요

Heltec WiFi LoRa 32는 Heltec Automation이 설계·생산한 classic IoT development board입니다. ESP32와 SX127x를 통합해 Wi-Fi, BLE, LoRa를 제공하며 Li-Po battery management system과 0.96-inch OLED도 포함합니다.

주요 기능은 다음과 같습니다.

  • Dual-core 32-bit MCU와 ULP core를 갖춘 ESP32
  • SX1276/SX1278 LoRa node chip
  • Voltage regulator, ESD·short-circuit protection, RF shielding을 갖춘 Micro USB interface
  • SH1.25-2 battery interface와 integrated lithium battery management system
  • WiFi·LoRa·Bluetooth, onboard 2.4GHz metal 3D antenna, LoRa용 IPEX(U.FL) interface
  • 0.96-inch 128×64 dot-matrix OLED
  • CP2102 USB-to-serial chip

System requirement

Prerequisite

Espressif HAL이 동작하려면 WiFi와 Bluetooth binary blob이 필요합니다. 다음 명령으로 file을 가져옵니다.

west blobs fetch hal_espressif

Build와 Flash

Simple boot

Second-stage bootloader 없이 single binary image로 board를 load할 수 있으며 추가 configuration 없이 application을 build할 때의 default입니다.

MCUboot bootloader

MCUboot를 선택할 수도 있으며 이 경우 bootloader를 적어도 한 번 build하고 flash해야 합니다. Application build 방식은 Sysbuild와 manual build 두 가지입니다.

Board default configuration file에 다음 line을 추가하면 MCUboot를 선택할 수 있습니다.

CONFIG_BOOTLOADER_MCUBOOT=y

Sysbuild

Sysbuild는 ESP32 SoC board를 bootstrap하는 데 필요한 모든 image를 함께 build하고 flash할 수 있게 합니다.

west build -b heltec_wifi_lora32_v2 --sysbuild samples/hello_world

Default sysbuild는 MCUboot와 application image를 만들며 다른 image도 만들도록 구성할 수 있습니다. Output은 domain subdirectory별로 구성됩니다.

build/
├── hello_world
│   └── zephyr
│       ├── zephyr.elf
│       └── zephyr.bin
├── mcuboot
│   └── zephyr
│       ├── zephyr.elf
│       └── zephyr.bin
└── domains.yaml

자세한 내용은 Zephyr sysbuild 문서를 참조하십시오.

Manual build

Development cycle에서는 image를 하나씩 전통적인 방식으로 build해 build·flash 시간을 줄일 수 있습니다. 이후 절차는 manual build와 sysbuild 모두에 적용되며 build directory 구조만 다릅니다.

west build -b heltec_wifi_lora32_v2/esp32/procpu samples/hello_world

일반 flash target을 사용할 수 있습니다.

west flash

Serial monitor를 엽니다.

west espressif monitor

Board가 자동으로 reset·boot하면 다음 message가 표시되어야 합니다.

***** Booting Zephyr OS vx.x.x-xxx-gxxxxxxxxxxxx *****
Hello World! heltec_wifi_lora32_v2

Debugging

ESP32 module에는 upstream에 아직 포함되지 않은 OpenOCD patch가 필요합니다. Espressif가 관리하는 OpenOCD ESP32 fork를 사용할 수 있습니다.

Zephyr SDK는 bundled OpenOCD를 기본으로 사용합니다. Build 때 다음 parameter로 custom OpenOCD binary와 script path를 지정할 수 있습니다.

west build -b heltec_wifi_lora32_v2/esp32/procpu samples/hello_world -- -DOPENOCD=<path/to/bin/openocd> -DOPENOCD_DEFAULT_PATH=<path/to/openocd/share/openocd/scripts>

Application은 일반적인 방법으로 debug할 수 있습니다.

west debug

Hardware 기능 활용

Onboard OLED display

Onboard OLED는 I2C로 연결된 128×64 pixel ssd1306입니다. 다음과 같이 ssd1306_128x64 shield를 활성화해 LVGL sample에서 사용할 수 있습니다.

west build -b heltec_wifi_lora32_v2/esp32/procpu samples/subsys/display/lvgl --shield ssd1306_128x64
west flash

참고 자료

Source

출처

영어 원문에는 문단, 문서 지시문, 표, 코드, 코드 심벌, 경로를 그대로 보존했습니다.