Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
Maximilian0017 wrote:and the wifi was really bad
Quote:ECR6600 with v2.1.23.16 firmware size increased from 850kb to 920kb. (When i tried v2.1.24.11, it was 1222kb. Perhaps some optimization flags were missing?)
Added ECR6600 and BL602 deepsleep (ECR6600 - unknown if it works with new sdk, it didn't in the old one).
BL602 pindeepsleep (GPIO7/8 only)
ESP-IDF sdk from v5.5-beta1 to v5.5
Powersave for ECR6600
ESP deepsleep argument from ms to s
ECR6600 reset reason
divadiow wrote:powersave 1 doesn't crash but don't know if it's effective
insmod wrote:So it can connect after deep sleep?
divadiow wrote:I can check later today..
insmod wrote:I tried 3 different bootloaders (they differ a little, HLK-M20, ELM327 and standard nocrc), but none succeeded.
TL;DR: For modders backing up or porting the LSC Connect Smart Wall Dimmer 3207304, the working path is clear: read a 2048KB flash dump over UART0, because “READ Flash Success!” is confirmed with RDTool plus the ECR6600 stub. This FAQ helps anyone handling the AXY2S/ECR6600 platform, TuyaOS 3 storage changes, and early OpenECR6600 support. [#21377851]
Why it matters: This thread turns a previously unsupported Tuya dimmer into a documented ECR6600 case study for backup, reverse-engineering, and early open-firmware migration.
| Option | What it does well | Main limitation | Practical status |
|---|---|---|---|
| Stock Tuya firmware | Boots reliably and exposes Tuya app logs | Closed platform, config extraction fails | Best baseline |
| RDTool + ECR6600 stub | Reads full flash backup to PC | Wording is confusing; timing matters on VBat | Confirmed working |
| OpenECR6600 / OpenBK | Custom firmware, UART, OTA, TuyaMCU support | Wi-Fi and sleep behavior varied by module/SDK | Usable, still maturing |
| WG236A test modules | Good for bench testing and SDK work | Reported weak receive performance on some units | Mixed results |
Key insight: The hardest blocker was not dumping flash. It was platform maturity: TuyaOS 3 storage changed, UART logs split across ports, and ECR6600 Wi‑Fi and sleep behavior depended heavily on module, partitions, and SDK version.
powersave 1 or powersave 2. [#21622863]ty heap base: 1f000 size: 196352 followed by repeated garbage characters. That split is device-specific: a standard WG236P firmware later showed logs on UART0, but the Tuya dimmer dump did not. [#21391389]UART INIT and UART DEINIT on the app-log UART after boot, and later testing confirmed other users saw the same behavior on the LSC firmware. One developer explicitly said that if you see the same INIT/DEINIT loop, “it is probably working fine.” So treat it as expected firmware behavior, not proof of a bad flash or dead module. [#21417576]block magic. One contributor summarized the reason directly: “TuyaOS3 has changed the way config is stored.” That means the failure is a format mismatch, not proof that the dump is corrupt. [#21389968]nv_amt partition, and erasing flash could replace it with a generic default. OpenECR6600 later added MAC changing, and testers confirmed that changing the MAC inside OBK updated the value stored in flash. Preserving the original backup also keeps RF calibration data, which is stored there too. [#21459742]HF-LPT6200 and did not behave normally. [#21474737]ecx4sg with dpIDs including switch_led_1 as ability 1, bright_value_1 as ability 2, brightness_min_1 as ability 3, and countdown_1 as ability 6. The brightness range was listed as 10 to 1000. A placeholder add to the device list was also linked, showing the device was at least partially characterized. [#21809988]powersave 0 and 0.02–0.03A at powersave 1 or powersave 2, while the device stayed responsive. Deep sleep entered correctly with commands like deepsleep 30, and the module could wake after 30s, but Wi‑Fi rejoin was erratic. In several wake cycles, the device booted, scanned, reached state 6, then disconnected repeatedly until a hard power cycle or later reboot restored normal joins. [#21622863]