fuers t3e can't flash.

[lexmark3200]

Hi. I'm trying to flash OpenHasp onto a Fuers T3e. I've disassembled it and connected it to J1 according to https://www.openhasp.com/0.7.0/hardware/golden-security/gs-t3e/#v24
for version 2.4 - my PCB is: ZIGBEE_4CP_WNB_v2.4 2024.09.00.
Neither esphome (web flasher) nor the flasher on the OpenHasp website can connect to the ESP32.
I have a CP2102 - other ESP32s without USB program correctly.
I tried swapping the connection from 1:1 TX -> TX RX -> RX to TX->RX RX -> TX.
Without any success. I shorted pin ZT3L (PIN16) to GND during the flashing process, but it wasn't detected correctly.

Many thx for answers and help.

[fvanroie]

First off, the device appears to be the same hardware as the Golden Security T3E, but I haven't personally tested any Fuers T3E devices.

Without any success. I shorted pin ZT3L (PIN16) to GND during the flashing process, but it wasn't detected correctly.

I think there may be some confusion here: you should not be using any ZT3L pins during the ESP32 flashing process.
You need to short IO0 to GND on the 6-pin flash header:

• connect IO0 to GND before you power on the device
• connect 5V to power on the device while IO0 is shorted to GND
• now the device will boot into download/flash mode, the display should stay black
• try flashing the device using the Web Flasher as described in the documentation

Since neither the OpenHASP Web Flasher nor the ESPHome Web Flasher can detect the ESP32, I suspect the issue is with getting the ESP32 into download mode rather than with the firmware itself. The most likely cause is that IO0 is not being held low during power-up; shorting ZT3L/GPIO16 to GND will not put the ESP32 into flash mode.

For hardware revision v2.4, the connections between the PCB and the USB-to-serial programmer should be:

• GND ↔ GND
• 5V ↔ 5V
• RX ↔ TX
• TX ↔ RX
• IO0 ↔ GND during power-up to force the ESP32 into flash mode.

[fvanroie]

maybe I can use the USB from the devkit board, connecting TX to RX and RX to TX between J1 and the devkit. Maybe that will work.

No that won't work. I think you probably have a problem with either the power supply or wiring.
Do not connect the devkit ESP32 to a T3E ES32, that does not make sense.
Maybe post a clear picture of your wiring, that might help demystify the problem.

[lexmark3200]

Color CP2102 -> J1
Grey TX -> RX
White RX -> TX
Black GND -> GND
Pink 5V -> 5V

Blue J1 GND -> GPIO0

[lexmark3200]

I connected the CP2102 as shown in the attached photos. I ran Putty at 115200 baud, and interestingly, there's silence in the terminal, but the RX LED on the CP2102 is blinking slightly.

Generally speaking, purely hypothetically, if the ESP were somehow blocked from writing, would it show something in the console during startup?

[fvanroie]

Yeah, on a normal ESP32, if TX/RX wiring and power are correct, you should usually see something at boot on the serial console (often boot ROM messages at 115200 baud). Even if flash contents are corrupt, the ROM bootloader still prints startup information.
If there is a writelock, esptool should report it.

[lexmark3200]

Check this: I connected standard ESP32 "2x relay" grom Aliexpress with my cp2102, after that, I get on putty logs, and :

esptool.exe --chip esp32 --port COM6 -b 115200 chip-id
esptool v5.0.0
Connected to ESP32 on COM6:
Chip type: ESP32-D0WD-V3 (revision v3.1)
Features: Wi-Fi, BT, Dual Core + LP Core, 240MHz, Vref calibration in eFuse, Coding Scheme None
Crystal frequency: 40MHz
MAC: b0:cb:d8:e3:2d:78

Stub flasher running.

Warning: ESP32 has no chip ID. Reading MAC address instead.
MAC: b0:cd:d8:e1:2d:7b

Hard resetting via RTS pin...

So, the CP2102 I think, it is ok.
Something is wrong with the borad t3e

[Jero1985]

Hi, I used this one—"https://www.amazon.de/dp/B0B7RHPMT7?ref=ppx_yo2ov_dt_b_fed_asin_title"—for flashing. RX -> RX and TX -> TX. I handled the rest just like you did with the "flash_download_tool_3.9.11"; that was the only way I could get it to work.

PS: Translated using Google Translate.

[fvanroie]

That great news! Good to hear you tracked it down, and thanks for reporting back with the solution.

It looks like the issue was the USB-to-serial adapter rather than the panel itself. Switching from the CP2102 to a CH340 allowed the ESP32-S3 to be detected and flashed successfully. That feedback is really valuable and will likely help the next person who runs into the same problem with this hardware.

Have fun with your openHASP device!

[lexmark3200]

ESP Flash Download Tools 3.9.11 :
Read 16777216 bytes at 0x00000000 in 1620.5 seconds (82.8 kbit/s)...
So if everything read properly we have full dump of original software.

[Jero1985]

I’ve been programming on ESPHome with the help of an AI, but my basic settings aren't quite perfect yet. The image flickers white every now and then, but I don't know what might be causing it.

[lexmark3200]

I tried flashing the firmware from ESPhome, just like you, using AI, but I failed. I finally flashed OpenHasp, transferred the configuration from Guition, and I'll leave it that way for now. Maybe in a while...
Have you tried the official one:
https://devices.esphome.io/devices/tuya-t3e-esp32-s3/
I tried creating my own image based on that.

[fvanroie]

Since this is an openHASP discussion forum, please don't post configs from other firmwares here. Let's keep the thread on topic.

[lexmark3200]

A small update. After using a converter on the CH340, the Fuers T3e can be flashed.
I uploaded the firmware from the GS T3e. Everything seems to be working perfectly.
Mamy thx for help.

[lexmark3200]

OK. So another small different between v2.4 GS and my Fuers is the GPIO.
https://www.openhasp.com/0.7.0/hardware/golden-security/gs-t3e/#v23

Pin	Mode	GS-T3E	Group	Default
45	Output	Relay L1	1	Low (Normal)
46	Output	Relay L2	2	Low (Normal)
44	Output	Relay L3	3	Low (Normal)

Pin	Mode	F-T3E	Group	Default
45	Output	Relay L1	1	Low (Normal)
46	Output	Relay L2	2	Low (Normal)
2	Output	Relay L3	3	Low (Normal)