Flashing Smartlive DS-121 with ltchiptool: Stuck After Firmware Update?

Hello,

Not sure how this forum works but hopefully someone can put me in the right direction.

I've a smartlive DS-121 wifi 4 touch glass touch switch with a cb3s chip on it.

try to flash firmware ltchiptool_bk72xx_2024-11-07_11-42-46_efuse.bin (think this is the right one?)

When i try to flash it with ltchiptool v4.11.2 i get:
D [ 4602.494] ( 0.066s) Connecting
W [ 4602.583] ( 0.090s) Unknown bootloader CRC - 0xCBC3D235 - please report this on GitHub issues!
D [ 4602.592] ( 0.009s) Reading 4k page at 0x011000 (0.00%)
D [ 4602.953] ( 0.361s) BK72xx connected - protocol: FULL, chip: BK7231N, bootloader: None, chip ID: 0x7231c, boot version: None
D [ 4602.987] ( 0.034s) Trying to unprotect flash memory...
D [ 4603.003] ( 0.016s) Erasing and writing at 0x11000 (0.00%)
D [ 4603.003] ( 0.000s) - Checking block pre-erase @ 0x11000
D [ 4603.019] ( 0.016s) - Trying to erase block @ 0x11000
D [ 4603.033] ( 0.014s) - Checking block post-erase @ 0x11000
D [ 4603.049] ( 0.016s) - Erase succeeded @ 0x11000
D [ 4603.437] ( 0.388s) Erasing and writing at 0x12000 (0.45%)
D [ 4603.833] ( 0.396s) Erasing and writing at 0x13000 (0.91%)
D [ 4604.237] ( 0.405s) Erasing and writing at 0x14000 (1.36%)
D [ 4604.635] ( 0.398s) Erasing and writing at 0x15000 (1.81%)
D [ 4605.032] ( 0.397s) Erasing and writing at 0x16000 (2.27%)
D [ 4605.431] ( 0.399s) Erasing and writing at 0x17000 (2.72%)
D [ 4605.830] ( 0.399s) Erasing and writing at 0x18000 (3.17%)
D [ 4606.228] ( 0.398s) Erasing and writing at 0x19000 (3.63%)
D [ 4606.627] ( 0.399s) Erasing and writing at 0x1A000 (4.08%)
D [ 4607.025] ( 0.398s) Erasing and writing at 0x1B000 (4.53%)
D [ 4607.427] ( 0.402s) Erasing and writing at 0x1C000 (4.98%)
D [ 4607.825] ( 0.398s) Erasing and writing at 0x1D000 (5.44%)
D [ 4608.222] ( 0.396s) Erasing and writing at 0x1E000 (5.89%)
D [ 4608.621] ( 0.399s) Erasing and writing at 0x1F000 (6.34%)
D [ 4609.019] ( 0.398s) Erasing and writing at 0x20000 (6.80%)
D [ 4609.419] ( 0.401s) Erasing and writing at 0x21000 (7.25%)

and counting

D [ 4689.817] ( 0.398s) Erasing and writing at 0xEB000 (98.79%)
D [ 4690.214] ( 0.398s) Erasing and writing at 0xEC000 (99.24%)
D [ 4690.612] ( 0.397s) Erasing and writing at 0xED000 (99.70%)
D [ 4691.010] ( 0.399s) Verifying CRC
W [ 4691.010] ( 0.000s) The current command timeout of 1.0 second(s) is too low for reading 905216 bytes CRC. Increasing to 3 second(s).
D [ 4693.074] ( 2.064s) OK!
D [ 4693.082] ( 0.008s) Trying to unprotect flash memory...
D [ 4693.098] ( 0.016s) Writing unaligned data...
D [ 4693.149] ( 0.051s) Stopped FlashThread
D [ 4693.228] ( 0.078s) Started TerminalThread
D [ 4693.228] ( 0.000s) Terminal opened


And this is all.

Not restarting or giving an access point. Only the led of the wifi burns when on power.

anyone who can put me in the right direction?



AI: Can you confirm if the firmware file you used is specifically compatible with the Smartlive DS-121 and the CB3S chip?
not sure

AI: After the flashing process, did you perform any specific steps to try and restart the device or set up the access point? If so, what were they?
Yes making a restart and do a power down multiple times

basdelouw78 wrote:

ltchiptool_bk72xx_2024-11-07_11-42-46_efuse.bin

This is a backup of the efuse not the main firmware.

What is your end goal? To be running OpenBeken?

Hello Divadiow,

Thanks for your reply. I want it to function locally on home assistant.

Regards Bas

Did you take a full read of the factory firmware to file before writing anything to flash?

>>21293338 nope I don't think so

Added after 1 [hours] 9 [minutes]:

divadiow wrote:

Did you take a full read of the factory firmware to file before writing anything to flash?

No, i've look again and i cannot find a backup. Is this a problem?

Not necessarily. It looks like your logs show you flashed from 0x11000 so your bootloader is hopefully ok, unless you did other flashing to different addresses.

Maybe go straight to using Easy Flasher to burn the latest Beken N QIO firmware. See if OpenBeken comes up after that?

https://github.com/openshwprojects/BK7231GUIFlashTool

divadiow wrote:

Not necessarily. It looks like your logs show you flashed from 0x11000 so your bootloader is hopefully ok, unless you did other flashing to different addresses.

Maybe go straight to using Easy Flasher to burn the latest Beken N QIO firmware. See if OpenBeken comes up after that?

https://github.com/openshwprojects/BK7231GUIFlashTool

ok, can you tell me the firmware to burn with easyflasher?

It'll be the N variant of the Beken firmware. Have you seen any of the guides and videos? Starting from the Introduction on Github https://github.com/openshwprojects/OpenBK7231T_App?tab=readme-ov-file#introduction



Added after 2 [minutes]:

https://www.elektroda.com/rtvforum/topic4036050.html

Added after 1 [minutes]:

divadiow wrote:

It'll be the N variant of the Beken firmware

divadiow wrote:

It'll be the N variant of the Beken firmware. Have you seen any of the guides and videos? Starting from the Introduction on Github https://github.com/openshwprojects/OpenBK7231T_App?tab=readme-ov-file#introduction

Added after 2 [minutes]:

https://www.elektroda.com/rtvforum/topic4036050.html

Added after 1 [minutes]:

divadiow wrote:

It'll be the N variant of the Beken firmware

Yes I see a lot of videos but not all the chips are the same. I need the n series. That's the version I've burned on the chip as far as I know.

But do I now need this version burned with espeasyflaser?

Your CB3S module will have BK7231N chip on it. Easy Flasher is for Beken N and T chips. Easy Flasher will offer to download the latest firmware for your selected chip if there is not one already downloaded.

divadiow wrote:

Your CB3S module will have BK7231N chip on it. Easy Flasher is for Beken N and T chips. Easy Flasher will offer to download the latest firmware for your selected chip if there is not one already downloaded.

Ok, sorry wrong reading. I was now looking at espeasy but that isn't working.

I try again to burn the chip the way you are telling me. I now also have a backup bin. I think it's all burn ok but still no app or any live but the wifi led.

i attach the backup bin file

hmm. that backup doesn't even boot so I guess the bootloader was overwritten with something in previous efforts.
You could use this to write a new one

divadiow wrote:

hmm. that backup doesn't even boot so I guess the bootloader was overwritten with something in previous efforts.
You could use this to write a new one

Ok, Software says write success with these options but still no live in it.

I have made a new backup attach

that boots into OpenBeken and I see it's got a network it's trying to join. It also goes into safe mode and broadcasts an AP as expected.

Assuming it has the correct credentials is it not now appearing as a device on your network with an IP address you can browse to?

divadiow wrote:

that boots into OpenBeken and I see it's got a network it's trying to join. It also goes into safe mode and broadcasts an AP as expected.

Assuming it has the correct credentials is it not now appearing as a device on your network with an IP address you can browse to?

Still no activity. I have desoldered a 16pin ic to get a free tx/rx. is this needed to solder back before its working?

I see. That sounds like you've removed the TuyaMCU.

I guess tho if the module was powered ok then it should boot and broadcast. What if you power-cycle (off, on, off, on etc) 5 times, any OpenBeken access point broadcast?

divadiow wrote:

I see. That sounds like you've removed the TuyaMCU.

I guess tho if the module was powered ok then it should boot and broadcast. What if you power-cycle (off, on, off, on etc) 5 times, any OpenBeken access point broadcast?

No broadcast at all. I assume that if I can program the device it's also capable to startup without extra power but only the 3.3 volt of the programmer.

Ah. Power from the USB programmer is often not enough, especially when the WiFi initialises. It may be browning out and boot looping. This would be seen in the TX2 boot log output.

divadiow wrote:

Ah. Power from the USB programmer is often not enough, especially when the WiFi initialises. It may be browning out and boot looping. This would be seen in the TX2 boot log output.

Now put it back together but no difference.

no safe mode AP after power cycling it 5 times?

divadiow wrote:

no safe mode AP after power cycling it 5 times?

Nothing.

OK. I think it it was me I'd want to blow away whatever state the firmware is in on the module by writing another (because you do not have the original backed-up) full known-working BK7231N Tuya factory firmware to the device from 0x0 (eg https://www.elektroda.com/rtvforum/topic4028222.html#21293815) then just use Easy Flasher to flash OpenBeken as normal. The module should not be powered from the mains through any of this but a decent external 3.3v PSU - ie not the USB programmer 3v line

divadiow wrote:

OK. I think it it was me I'd want to blow away whatever state the firmware is in on the module by writing another (because you do not have the original backed-up) full known-working BK7231N Tuya factory firmware to the device from 0x0 (eg https://www.elektroda.com/rtvforum/topic4028222.html#21293815) then just use Easy Flasher to flash OpenBeken as normal. The module should not be powered from the mains through any of this but a decent external 3.3v PSU - ie not the USB programmer 3v line

Ok so burn your backup on the device must wake it up again. Do i need to change settings in the programmer or just select bk7231n chip and burn the bin file?

I make a power connection with a external power supply.

yes, burn backup from 0x0, no offset and nothing in write length in LT like this

Ok, can you tell me how to write from offset 0x0? Where in the settings do I make that change?