06-12-2026, 01:29 PM
Hi Kincony,
I have tried to flash newer version firmware (tried KCS_KC_TA_V3.25.0.zip) from a Mac. Tried multiple methods, including the use of a Windows VM with the official tool, and web.esphome.io. But while both tool reported success, when I turn off and on the board it is not able to respond on network. I have even tried to use the method of removing power, pressing the DW button, and then attaching the power, and then used the official tool to copy firmware using a low (115200) baud rate, while the tool has reported success, after reset the board it is just not responding on network (I can verify that on the switch statistics, in which the "bytes sent" in switch has high values, however "bytes received" in switch is always showing 0, indicating that the Tiny Alarm board is not responding any packet at all.
I have also tested to use USB C to USB A cable instead of a USB C to USB C cable as I see the youtube video is using one of that.
May I ask how is there a way to troubleshoot a ESP32S3 board boot up message to see if the firmware is correctly copied?
I have tried to flash newer version firmware (tried KCS_KC_TA_V3.25.0.zip) from a Mac. Tried multiple methods, including the use of a Windows VM with the official tool, and web.esphome.io. But while both tool reported success, when I turn off and on the board it is not able to respond on network. I have even tried to use the method of removing power, pressing the DW button, and then attaching the power, and then used the official tool to copy firmware using a low (115200) baud rate, while the tool has reported success, after reset the board it is just not responding on network (I can verify that on the switch statistics, in which the "bytes sent" in switch has high values, however "bytes received" in switch is always showing 0, indicating that the Tiny Alarm board is not responding any packet at all.
I have also tested to use USB C to USB A cable instead of a USB C to USB C cable as I see the youtube video is using one of that.
May I ask how is there a way to troubleshoot a ESP32S3 board boot up message to see if the firmware is correctly copied?