Check the serial console output

Oct 13, 2025 by thesweetdesigns.com 59 views

Boot-Loop on ESP32 DevKit rev4 (AZ-Delivery)

The ESP32 DevKit rev4 is a popular development board for IoT projects, but it can be challenging to get it up and running, especially when it comes to booting. In this article, we will explore the issue of boot-loop on the ESP32 DevKit rev4 and provide a step-by-step guide to troubleshoot and resolve the problem.

Symptoms

The symptoms of a boot-loop on the ESP32 DevKit rev4 include:

The board continuously reboots without any apparent reason.
The serial console output shows a repeating pattern of error messages and warnings.
The board's LED indicators may flash rapidly or in a specific pattern.

Setup

To reproduce the issue, we need to set up the ESP32 DevKit rev4 with the following components:

A MacBookPro M3 running DockerDesktop with esphome hostNetwork.
GoogleChrome for debugging and logging.
A C1 Modul connected to the ESP32 via USB.
The ESP32 DevKit rev4 board with the necessary components installed.

Code

The code used to reproduce the issue is as follows:

esphome:
  name: "esp32-watermeter"
  friendly_name: ESP32-Watermeter

esp32:
  board: esp32dev
  framework:
    type: arduino


# Enable Home Assistant API
api:
  id: espapi_wmbus_esp32
  port: 6053
  reboot_timeout: 0s

ota:
  password: !secret ota_pswd
  platform: esphome

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Esp32-Dev Fallback Hotspot"
    password: "fallbackpassword"

captive_portal:

external_components:
  - source: github://SzczepanLeon/esphome-components@main
    components: [wmbus]

wmbus:
  mosi_pin: GPIO23  # D23 auf ESP32
  miso_pin: GPIO19  # D19 auf ESP32
  clk_pin: GPIO18   # D18 auf ESP32
  cs_pin: GPIO5     # D5 auf ESP32
  gdo0_pin: GPIO16  # RX2 auf ESP32
  gdo2_pin: GPIO17  # TX2 auf ESP32
  frequency: 868.950
  all_drivers: True
  # sync_mode: True
  log_all: True

time:
  - platform: sntp
    id: sntp_time
    timezone: Europe/Sofia
    servers:
     - 0.pool.ntp.org
     - 1.pool.ntp.org
     - 2.pool.ntp.org

Troubleshooting

To troubleshoot the issue, we need to follow these steps:

Check the serial console output: The serial console output is the first place to look for clues about the issue. Look for error messages, warnings, and other relevant information.
Check the board's LED indicators: The board's LED indicators can provide valuable information about the issue. For example, a flashing LED may indicate a boot-loop.
Check the C1 Modul connection: Make sure the C1 Modul is properly connected to the ESP32 via USB.
Check the WiFi connection: Make sure the WiFi connection is stable and not causing any issues.
Check the code: Review the code for any errors or issues that may be causing the boot-loop.

Resolving the Issue

To resolve the issue, we need to follow these steps:

Update the code: Update the code to the latest version and make sure it is compatible with the ESP32 DevKit rev4.
Check the board's firmware: Make sure the board's firmware is up-to-date and compatible with the ESP32 DevKit rev4.
Check the C1 Modul connection: Make sure the C1 Modul is properly connected to the ESP32 via USB.
Check the WiFi connection: Make sure the WiFi connection is stable and not causing any issues.
Reset the board: Reset the board and try to boot it again.

Conclusion

In conclusion, the boot-loop on the ESP32 DevKit rev4 can be a challenging issue to resolve, but by following the troubleshooting steps and updating the code and firmware, we can resolve the issue and get the board up and running.
Boot-Loop on ESP32 DevKit rev4 (AZ-Delivery) - Q&A

In our previous article, we explored the issue of boot-loop on the ESP32 DevKit rev4 and provided a step-by-step guide to troubleshoot and resolve the problem. In this article, we will answer some frequently asked questions (FAQs) about the boot-loop issue and provide additional information to help you resolve the problem.

Q: What is a boot-loop?

A: A boot-loop is a situation where the ESP32 DevKit rev4 continuously reboots without any apparent reason. This can be caused by a variety of factors, including software issues, hardware problems, or configuration errors.

Q: What are the common causes of a boot-loop on the ESP32 DevKit rev4?

A: The common causes of a boot-loop on the ESP32 DevKit rev4 include:

Software issues: Bugs in the code, incompatible firmware, or incorrect configuration can cause a boot-loop.
Hardware problems: Faulty components, loose connections, or incorrect wiring can cause a boot-loop.
Configuration errors: Incorrect settings, missing or duplicate configurations, or incorrect pin assignments can cause a boot-loop.

Q: How can I troubleshoot a boot-loop on the ESP32 DevKit rev4?

A: To troubleshoot a boot-loop on the ESP32 DevKit rev4, follow these steps:

Check the serial console output: The serial console output is the first place to look for clues about the issue. Look for error messages, warnings, and other relevant information.
Check the board's LED indicators: The board's LED indicators can provide valuable information about the issue. For example, a flashing LED may indicate a boot-loop.
Check the C1 Modul connection: Make sure the C1 Modul is properly connected to the ESP32 via USB.
Check the WiFi connection: Make sure the WiFi connection is stable and not causing any issues.
Check the code: Review the code for any errors or issues that may be causing the boot-loop.

Q: How can I resolve a boot-loop on the ESP32 DevKit rev4?

A: To resolve a boot-loop on the ESP32 DevKit rev4, follow these steps:

Update the code: Update the code to the latest version and make sure it is compatible with the ESP32 DevKit rev4.
Check the board's firmware: Make sure the board's firmware is up-to-date and compatible with the ESP32 DevKit rev4.
Check the C1 Modul connection: Make sure the C1 Modul is properly connected to the ESP32 via USB.
Check the WiFi connection: Make sure the WiFi connection is stable and not causing any issues.
Reset the board: Reset the board and try to boot it again.

Q: What are some common mistakes that can cause a boot-loop on the ESP32 DevKit rev4?

A: Some common mistakes that can cause a boot-loop on the ESP32 DevKit rev4 include:

Incorrect pin assignments
Missing or duplicate configurations
Incorrect settings
Faulty components
Loose connections

Q: How can I prevent a boot-loop on the ESP32 DevKit rev4?

A: To prevent a boot-loop on the ESP32 DevKit rev4, follow these best practices:

Use the latest code: Use the latest version of the code and make sure it is compatible with the ESP32 DevKit rev4.
Check the board's firmware: Make sure the board's firmware is up-to-date and compatible with the ESP32 DevKit rev4.
Check the C1 Modul connection: Make sure the C1 Modul is properly connected to the ESP32 via USB.
Check the WiFi connection: Make sure the WiFi connection is stable and not causing any issues.
Use a reliable power source: Use a reliable power source to power the board.

Conclusion

In conclusion, the boot-loop on the ESP32 DevKit rev4 can be a challenging issue to resolve, but by following the troubleshooting steps and best practices, you can resolve the issue and get the board up and running. Remember to always check the serial console output, board's LED indicators, C1 Modul connection, WiFi connection, and code for any errors or issues that may be causing the boot-loop.