Problem flashing Sonoff Th Elite

[Hurlie]

Hello,

I flashed a Sonoff Th Elite with NodeMuc Flasher with the actual Version "tasmota32.bin" 14.2.0 Rita on ESP32.
(Output attached)

Everything seems to work fine.

After this, I have to power on the device, so it starts the AP-Mode. But after powering on the device, only the "auto" led goes on.

Normaly the Wifi LED has to flash and the AP can be viewed in the Wifi List.

But this does not happen:(

What goes wrong?

Do you have any suggestions?

Many thanks for your help.

[sfromis]

You didn't read the page you posted a screenshot from?

The file you highlighted is in the section "OTA Firmware" (meaning only for OTA), instead of "Factory binaries to be used for initial flashing", which is what you should have used.

And instead of messing with a non-supported tool for flashing (those "NodeMCU" tools can only be expected to work for ESP8266, not ESP32), it would have been simpler if you followed the link after "for an initial installation of Tasmota", which is a supported (and recommended) tool, automatically picking a binary (default selection) to match your hardware, obviously in accordance with the previous paragraph.

[Hurlie]

Hello stromis,

I connected over USB/serial with Hterm and got the following log:

Seems to be an boot loop.

Project tasmota - Tasmota Version 14.2.0(release-tasmota32)-3_0_4(2024-08-14T12:39:45)<\r><\n>00:00:00.000
WIF: WifiManager active for 3 minutes<\r><\n>ets Jul 29 2019 12:21:46<\r><\n><\r><\n>rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)<\r><\n>
configsip: 0, SPIWP:0xee<\r><\n>clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00<\r><\n>mode:DIO, clock div:2<\r><\n>load:0x3fff0030,len:184<\r><\n>load:0x40078000,len:13228<\r><\n>ho 0 tail 12 room 4<\r><\n>
load:0x40080400,len:4<\r><\n>load:0x40080404,len:2924<\r><\n>entry 0x40080570<\r><\n><\r><\n>00:00:00.001 HDW: ESP32-D0WD-V3 v3.0 <\r><\n>00:00:00.015 UFS: FlashFS mounted with 308 kB free<\r><\n>00:00:00.026 CFG:
Loaded from File, Count 2<\r><\n>00:00:00.037 QPC: Count 5<\r><\n>00:00:00.585 BRY: Berry initialized, RAM used 5060 bytes<\r><\n>00:00:00.596

Project tasmota - Tasmota Version 14.2.0(release-tasmota32)-3_0_4(2024-08-14T12:39:45)<\r><\n>00:00:00.000 WIF:

[sfromis]

Well, a typical cause of a boot loop that way is if your USB/serial adapter is too weak (lots of those are, except for the minority able to act as a small power supply) to allow the ESP32 to boot to include Wifi, and the log does look like this is happening. While that should be no issue when using mains power instead, there is not really more to see there, except to confirm that Tasmota was flashed and able to start booting.

[Hurlie]

ok, thats sound possible. When connected to USB there is too less power.
So I have to look for another USB/Serial Adapter with enough power?
Do you have a suggestion, which adapter would fit?
Attached pictures of my actual one.

[sfromis]

Oh no, that board again 😢 It is indeed not much recommended as it is not capable of delivering good power for ESP32, unless you can add a good 3.3V power source on the side (with common ground).

Both recommended ones are highlighted with yellow, the first one being the cheapest, but may still be borderline for getting a Wifi connection, depending on the board with the ESP32.

If you have a NodeMCU around, that can also be used as a pretty good USB/serial adapter, with the described wiring. And cheaper than the VoltLink board.

[Hurlie]

Hello sfromis,

tnx for your help an patience.

Ive just ordered the Voltlink Adapter. When its arrived, I will try it and tell you about the log:)

Have a nice day:)