Hi guys,
I encounter the following problem:
I’m using an ESP32 Relay x1 board.
My SoC is the ESP32-WROOM-32E
I base it on the following YAML code:
Unfortunately, after loading the *.bin file via ESPTool 4.7, the software does not start on the target. Can you help me ?
Did you try just using the esphome web flasher? All you have to do is copy/paste the relevant part of that esphome config to setup a single relay and paste that into a “New Project” It’s really simple and is the recommended way to flash them.
Is there a reason you’re kind of going out of your way to take a .yaml and compile it, then go to esptool and flash it. It’s all done for you using the web flasher and right there on 1 screen.
You didn’t post the actual yaml config you used to create the .bin so no one knows if the error is there. You have no log outputs to share that would help. How are you determining the software isn’t starting on the board? You did change the configurations from that repo, right? You set your wifi credentials, you did something with the places that have a “xxxx” right?
Hello, thank you for your reply.
I tried to prepare the map with the ESP web tool.
after preparing the board, it tries to connect to the wifi but without success .
here are the logs :
[0;32mI (148) esp_image: segment 1: paddr=000287c4 vaddr=3ffb0000 size=02f08h ( 12040) load
I (153) esp_image: segment 2: paddr=0002b6d4 vaddr=40080000 size=04944h ( 18756) load
I (162) esp_image: segment 3: paddr=00030020 vaddr=40
I (330) esp_image: segment 4: paddr=000a0bf8 vaddr=40084944 size=0f794h ( 63380) load
I (366) boot: Loaded app from partition at offset 0x10000
I (366) boot: Disabling RNG early entropy source…
I (377) cpu_start: Pro cpu up.
I (378) cpu_start: Starting app cpu, entry point is 0x40081940
I (364) cpu_start: App cpu up.
I (392) cpu_start: Pro cpu start user code
I (392) cpu_start: cpu freq: 160000000
I (392) cpu_start: Application information:
I (396) cpu_start: Project name: esp32-th-4
I (402) cpu_start: App version: 2023.12.9
I (407) cpu_start: Compile time: Feb 8 2024 13:18:09
I (413) cpu_start: ELF file SHA256: 9708cf188b95a016…
I (419) cpu_start: ESP-IDF: 4.4.5
I (424) cpu_start: Min chip rev: v0.0
I (428) cpu_start: Max chip rev: v3.99
I (433) cpu_start: Chip rev: v3.1
I (438) heap_init: Initializing. RAM available for dynamic allocation:
I (445) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (451) heap_init: At 3FFB6E18 len 000291E8 (164 KiB): DRAM
I (457) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (464) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (470) heap_init: At 400940D8 len 0000BF28 (47 KiB): IRAM
Brownout detector was triggered
ets Jul 29 2019 12:21:46
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6608
load:0x40078000,len:15060
ho 0 tail 12 room 4
load:0x40080400,len:3816
entry 0x40080698
I (29) boot: ESP-IDF 4.4.5 2nd stage bootloader
I (29) boot: compile time 13:23:49
I (29) boot: chip revision: v3.1
I (32) boot.esp32: SPI Speed : 40MHz
I (37) boot.esp32: SPI Mode : DIO
I (41) boot.esp32: SPI Flash Size : 4MB
I (46) boot: Enabling RNG early entropy source…
I (51) boot: Partition Table:
I (55) boot: ## Label Usage Type ST Offset Length
I (62) boot: 0 otadata OTA data 01 00 00009000 00002000
I (69) boot: 1 phy_init RF data 01 01 0000b000 00001000
I (77) boot: 2 app0 OTA app 00 10 00010000 001c0000
I (84) boot: 3 app1 OTA app 00 11 001d0000 001c0000
I (92) boot: 4 nvs WiFi data 01 02 00390000 0006d000
I (99) boot: End of partition table
I (104) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=1879ch (100252) map
I (148) esp_image: segment 1: paddr=000287c4 vaddr=3ffb0000 size=02f08h ( 12040) load
I (153) esp_image: segment 2: paddr=0002b6d4 vaddr=40080000 size=04944h ( 18756) load
I (162) esp_image: segment 3: paddr=00030020 vaddr=400d0020 size=70bd0h (461776) map
I (330) esp_image: segment 4: paddr=000a0bf8 vaddr=40084944 size=0f794h ( 63380) load
I (366) boot: Loaded app from partition at offset 0x10000
I (366) boot: Disabling RNG early entropy source…
I (377) cpu_start: Pro cpu up.
I (378) cpu_start: Starting app cpu, entry point is 0x40081940
I (364) cpu_start: App cpu up.
I (392) cpu_start: Pro cpu start user code
I (392) cpu_start: cpu freq: 160000000
I (392) cpu_start: Application information:
I (396) cpu_start: Project name: esp32-th-4
code yaml:
esphome:
name: esp32-th-4
esp32:
board: esp32dev
framework:
type: esp-idf
logger:
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
captive_portal:
light:
switch:
binary_sensor:
I’m not quite sure what you mean by, “prepare the map with Esp web tools”. I would just start over if I were you. I still don’t understand why you were using esptool and where you got this .bin from. It looks like the board specs that were compiled in the .bin do not match the esp32 board specs that you are using. Hook that board back up to your PC, go to the esphome web flasher, it will auto discover which esp32 and how big the flash, memory, etc and it will auto configure all of that, You just need to click, “OK” and “Next” It’s almost impossible to do it wrong or make a mistake which is why i’m so confused about the method you were using and where this .bin came from.
So, just go ahead and try it that way, it should work on the first try and you’ll be ready to go!