TTGO LoRa32
Overview
The Lilygo TTGO LoRa32 is a development board for LoRa applications based on the ESP32-PICO-D4.
It’s available in two versions supporting two different frequency ranges and features the following integrated components:
ESP32-PICO-D4 chip (240MHz dual core, 600 DMIPS, 520KB SRAM, Wi-Fi)
SSD1306, 128x64 px, 0.96” screen
SX1278 (433MHz) or SX1276 (868/915/923MHz) LoRa radio frontend
JST GH 2-pin battery connector
TF card slot
Some of the ESP32 I/O pins are accessible on the board’s pin headers.
Hardware
Supported Features
The ttgo_lora32
board supports the hardware features listed below.
- on-chip / on-board
- Feature integrated in the SoC / present on the board.
- 2 / 2
-
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files. -
vnd,foo
-
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.
Type |
Location |
Description |
Compatible |
---|---|---|---|
CPU |
on-chip |
Espressif Xtensa LX6 CPU2 |
|
ADC |
on-chip |
ESP32 ADC2 |
|
Bluetooth |
on-chip |
Bluetooth HCI for Espressif ESP321 |
|
CAN |
on-chip |
ESP32 Two-Wire Automotive Interface (TWAI)1 |
|
Clock control |
on-chip |
ESP32 RTC (Power & Clock Controller Module) Module1 |
|
Counter |
on-chip |
ESP32 Counter Driver based on RTC Main Timer1 |
|
on-chip |
ESP32 general-purpose timers4 |
||
DAC |
on-chip |
ESP32 Digital to Analog converter (DAC)1 |
|
Ethernet |
on-chip |
ESP32 Ethernet1 |
|
Flash controller |
on-chip |
ESP32 flash controller1 |
|
GPIO & Headers |
on-chip |
ESP32 GPIO controller2 |
|
I2C |
on-chip |
ESP32 I2C2 |
|
Input |
on-chip |
ESP32 touch sensor input1 |
|
Interrupt controller |
on-chip |
ESP32 Interrupt controller1 |
|
IPM |
on-chip |
ESP32 soft inter processor message1 |
|
Mailbox |
on-chip |
ESP32 soft mailbox1 |
|
MDIO |
on-chip |
ESP32 MDIO controller1 |
|
Memory controller |
on-chip |
ESP32 pseudo-static RAM controller1 |
|
MTD |
on-chip |
Flash node1 |
|
on-chip |
Fixed partitions of a flash (or other non-volatile storage) memory1 |
||
Pin control |
on-chip |
ESP32 pin controller1 |
|
PWM |
on-chip |
ESP32 LED Control (LEDC)1 |
|
on-chip |
ESP32 Motor Control Pulse Width Modulator (MCPWM)2 |
||
RNG |
on-chip |
ESP32 TRNG (True Random Number Generator)1 |
|
SDHC |
on-chip |
ESP32 SDHC controller1 |
|
on-chip |
ESP32 SDHC controller slot2 |
||
Sensors |
on-chip |
ESP32 Pulse Counter (PCNT)1 |
|
Serial controller |
on-chip |
ESP32 UART3 |
|
SPI |
on-chip |
ESP32 SPI2 |
|
SRAM |
on-chip |
Generic on-chip SRAM description2 |
|
Watchdog |
on-chip |
||
Wi-Fi |
on-chip |
ESP32 SoC Wi-Fi1 |
Start Application Development
Before powering up your Lilygo TTGO LoRa32, please make sure that the board is in good condition with no obvious signs of damage.
System requirements
Prerequisites
Espressif HAL requires WiFi and Bluetooth binary blobs in order to work. Run the command below to retrieve those files.
west blobs fetch hal_espressif
Note
It is recommended running the command above after west update
.
Building & Flashing
Simple boot
The board could be loaded using a 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 built (and flashed) at least once.
There are two options to be used when building an application:
Sysbuild
Manual build
Note
User can select the MCUboot bootloader by adding the following line to the board default configuration file.
CONFIG_BOOTLOADER_MCUBOOT=y
Sysbuild
The sysbuild makes it possible to build and flash all necessary images needed to bootstrap the board with the ESP32-PICO-D4 SoC.
To build the sample application using sysbuild use the command:
west build -b ttgo_lora32/esp32/procpu --sysbuild samples/hello_world
By default, the ESP32-PICO-D4 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:
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 Sysbuild (System build) documentation.
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.
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 Building an Application and Run an Application for more details).
# From the root of the zephyr repository
west build -b ttgo_lora32/esp32/procpu samples/hello_world
The usual flash
target will work with the ttgo_lora32
board target.
Here is an example for the Hello World
application.
# From the root of the zephyr repository
west build -b ttgo_lora32/esp32/procpu samples/hello_world
west flash
The default baud rate for the Lilygo TTGO LoRa32 is set to 1500000bps. If experiencing issues when flashing,
try using different values by using --esp-baud-rate <BAUD>
option during
west flash
(e.g. west flash --esp-baud-rate 115200
).
You can also open the serial monitor using the following command:
west espressif 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! ttgo_lora32/esp32/procpu
Code samples
The following sample applications will work out of the box with this board:
Debugging
Lilygo TTGO LoRa32 debugging is not supported due to pinout limitations.