Lolin32 Lite

Classic ESP32 With Battery Power Support

The Lolin32 Lite development board features a classic ESP32 microcontroller on a board that comes with battery support, making it an ideal choice for portable solutions.

The board comes with a USB C connector to connect to a PC, plus a JST 2.0 socket to connect a battery. The battery can power the board, and the USB C connector can be used to charge it.

Technical Details

Here are the fundamental board details:

Item Description
Memory external 4MB Flash
Clock Speed 240MHz
Charging 500mA charging current, LTH7/HM4054H
Power Consumption 45.4mA (normal), 1.28mA (sleep mode)
Internal LED GPIO22
Battery LiIon/LiPo 3.7V
USB-to-TTL CH340
Size 49.2x25.5mm
Weight 6.6g

Comparison Lolin32

The Lolin32 Lite development board is the smaller version of the Lolin32 development board. The latter has its JST 2.0 battery socket placed on the side rather than next to the USB connector.

The significant differences between Lolin32 Lite and Lolin32 is the lack of these pins: RX0, TX0, and 5V.

Lolin32 Lite is specifically designed to be operated by a connected battery in a 3.3V environment. The board is not designed to receive power via an external power supply nor does it expose 5V for external components. Its GPIOs are not 5V tolerant either.

Some connections differ just in the number of exposed pins: there is just one GND pin (instead of five), and just one 3.3V pin (instead of three).

Caveats

This board is specifically designed for portable devices with a battery and focuses on a small footprint. This results in a few caveats.

Power Supply

This board needs to be powered either by USB or battery. There is no separate 5V input pin. While the board does output 3.3V at its designated pin, you may not be able to run the board by providing 3.3V input. If you do, the battery will not be charged.

In a nutshell, this board is specifically designed for portable apps that run from a battery. The USB connector in this scenario is primarily used to charge the battery.

GPIOs

The board exposes 19 GPIOs and 4 inputs. Compared to other boards, the number of GPIOs is limited. For special purpose projects where you need to access certain functionality (i.e. I2S), make sure all necessary hardware pins are exposed.

All GPIO are 3.3V and not 5V tolerant. Use a level shifter to connect 5V devices.

Pins

The board comes with 26 pins.

Pullup And Pulldown

All GPIO pins support internal pull-up and pull-down resistors.

When To Use

Here are reasons for choosing a Lolin32 Lite:

Feature Use Cases
Battery comes with everything needed to hook up a LiIon/LiPo battery
Price The board is relatively cheap
3.3V You are planning to use 3.3V components and do not need 5V support

These are potential reasons to choose a different microcontroller type:

Use Case Recommendation
External Power Cannot be operated with external 3.3V or 5V power supply
Limited GPIOs Only relatively few GPIO are exposed. When you need a massive number of GPIOs or access to specific CPU pins, this board may not work for you
5V components if you need to work with 5V components you might want to consider a different board. The Lolin32 Lite neither exposes 5V, nor are its GPIOs 5V tolerant.

Programming

The S2 supports the Arduino Framework.

It can be programmed using platformio, the vendors’ esp-idf, or the classic Arduino IDE.

Adding ESP Support To Arduino IDE

Arduino IDE by default only supports Arduino-compatible microcontrollers. To use it with ESP microcontrollers like the S2, the appropriate additional board manager needs to be installed. After that, ESP microcontrollers can be programmed just like any Arduino board.

To add an ESP-compatible board manager, in Arduino IDE choose the menu item File/Preferences, fill the url https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_dev_index.json into the field Additional Boards Manager URLs, and click OK.

Next, go to Tools/Board/Boards Manager, and search for esp32. Install the board manager created by Espressif Systems.

Connecting Microcontroller To Computer

Most microcontroller boards come with a USB connector and a USB-to-Serial component. They can be directly connected to the USB interface of your computer.

When you plug in the USB cable into your computer, you should hear the typical sound that plays when a new USB device is discovered. If you do not hear this sound (even though sound is enabled), make sure you are using a suitable USB data cable. Simple USB charger cables have no data pins and do not work. Also make sure you plugged in the USB cable firmly on both ends.

Once the microcontroller board is successfully connected to the computer, most boards indicate power on status via a red LED. A new port should also become available.

Materials

Lolin Lite eBook
HM4054H Charger
LTH7R Charger (Chinese)
LTH7S Charger (Chinese)

Comments

Please do leave comments below. I am using utteran.ce, an open-source and ad-free light-weight commenting system.

Here is how your comments are stored

Whenever you leave a comment, a new github issue is created on your behalf.

  • All comments become trackable issues in the Github Issues section, and I (and you) can follow up on them.

  • There is no third-party provider, no disrupting ads, and everything remains transparent inside github.

Github Users Yes, Spammers No

To keep spammers out and comments attributable, all you do is log in using your (free) github account and grant utteranc.es the permission to submit issues on your behalf.

If you don’t have a github account yet, go get yourself one - it’s free and simple.

If for any reason you do not feel comfortable with letting the commenting system submit issues for you, then visit Github Issues directly, i.e. by clicking the red button Submit Issue at the bottom of each page, and submit your issue manually. You control everything.

Discussions

For chit-chat and quick questions, feel free to visit and participate in Discussions. They work much like classic forums or bulletin boards. Just keep in mind: your valued input isn’t equally well trackable there.

  Show on Github    Submit Issue

(content created May 15, 2024)