Bricked device, bug in version before 0.1.0.3

[wildekek]

Looks like my LYWSD03MMC was bricked after flashing the firmware. The display does not turn on after flashing and can't find it in my zigbee network.

Things I tried:

• Battery removal
• Shorting GND/RESET pins
• Using a 3v PSU to make sure battery is not the problem

Logs:

3:48:30 PM: Searching for devices
3:48:42 PM: NotFoundError: User cancelled the requestDevice() chooser.
3:48:42 PM: Reconnect 1 from 5
3:49:07 PM: Searching for devices
3:49:35 PM: Connecting to: Climate_1
3:50:00 PM: Hardware Revision String: B1.4
3:50:00 PM: Software Revision String: V4.3
3:50:00 PM: Firmware Revision String: github.com/pvvx
3:50:00 PM: Detected custom Firmware
3:50:11 PM: Hardware Version: LYWSD03MMC B1.4, Software Version: 4.3, Sensor: SHTC3 (SHTV3)
3:50:11 PM: Custom config HEX string: 55031002002804a9313180b4
3:50:31 PM: Load firmware file 'Z03MMC_v0102.bin'...
3:50:32 PM: File: Z03MMC_v0102.bin
3:50:32 PM: File size: 128900 bytes
3:50:32 PM: Count: 8057
3:50:36 PM: Start DFU
3:51:07 PM: Update done after 30.577 seconds
3:51:08 PM: Disconnected.

[pvvx]

Unfortunately, later problems were identified with TLSR825x chips with Flash from the ZB (Zbit Semiconductor). Typical TLSR825x containing Flash from Winbond. If you come across an option with a Flash crystal from ZB, you will have to reprogram it with wires... Fixed in the next version - 0.1.0.3.

[wildekek]

Ok, cool. Will try to flash it over UART and will re-flash with 0.1.0.3. Thanks for your work!

[wildekek]

I hooked it up to an FTDI and used your USB-COM Flash Writer . It gave no errors when erasing and writing ATC_v44.bin. Also, the "Soft Reset MCU" worked fine. It still does not show anything on the display. Any ideas on what I could try to unbrick it?

[pvvx]

A very strange situation. "USB-COM Flash Writer" has no feedback and cannot verify the write. You may have to repeat the flashing...

https://github.com/pvvx/ATC_MiThermometer#the-usb-com-adapter-writes-the-firmware-in-explorer-web-version