Cozylife DS-1211AN 3Gang Touch Switch: 1MB BL602L10 [XT-BL12][DT-BL12] - Images, Firmware & Boot

Question

This is the Cozylife DS-1211AN 3-gang touch wall switch. The sticker on the box states it was manufactured by Shenzhen Dianling Intelligent Technology Co Ltd. Unfortunately it comes with a 1mb BL602 so is not an easy candidate for freeing from Cozylife cloud services as OpenBeken does not work...

insmod · Accepted Answer

>>21301826 Is GPIO17 used for anything? If so, then transplantation to ESP-12 would require to solder additional resistor to IO0-3V3 (about 1K), otherwise it may not boot.
On this switch, when i replaced the stock BL602 module with an ESP one, GPIO0 low at boot prevented it from working.

miegapele · Accepted Answer

Here is the build without easyfash. You can't save any settings, so only open ap will work. but if this boots we can troubleshoot that easyflash further.

divadiow · Answer

good point. module swap is conditional. GPIO17 traces to:

divadiow · Answer

module has a new home. ready for some unknown adventure

vinibali · Answer

I'm watching this topic.

divadiow · Answer

The bell at the bottom of the thread can be used to watch a topic

vinibali · Answer

>>21381948 the post might cause more attention, I'm also happy to help the development here if I could

divadiow · Answer

Cool 😎

Added after 2 [minutes]:

This was the latest on the issue. I have not tried to disable LFS yet but I did try really old BL602 builds before LFS was implemented. That was with old SDK though

https://www.elektroda.com/rtvforum/topic4024917-60.html#21372625

Added after 3 [minutes]:

I was looking into it more - perhaps this in here /components/bl602/bl602/evb/ld/flash.ld

but if it is that then it means we've been building fw for 4mb flash to date (?)

Log in, to see the code

@miegapele

miegapele · Answer

that's memory layout in application, not flash layout. It's most likely the same regardless how much flash you have. I would look into partition layout files (toml) and check what we use. Also now I think about it bootloader might be different too maybe?

divadiow · Answer

I've been trying the 1mb toml. I'll transplant BL from 1mb device and test

miegapele · Answer

There is partitions missing in there I believe. You will need to modify it to have all the required partitions or do not use the partitions which don't exists on 1mb layout in the application.

p.kaczmarek2 · Answer

Hey guys, any hope for running BL602 OBK port on this chip? We've got the same switch on polish elektroda side, this topic:
https://www.elektroda.pl/rtvforum/topic4103835.html#21427337
I can help by making PR and reducing build size with obk_config.h , but I don't have XT-BL12 on my site for testing.

Latest OBK version have even options (defines) to disable stuff like config HTML pages, so maybe we could reduce size a lot futher...

divadiow · Answer

how do we turn off OpenBL602 knowing about the OTA partition/expecting one to exist? I've already tried pre-LFS OpenBL602 to 1mb chip in case it was LFS to blame old and new builds and even the latest SDK PR flash fine but always fail at the same point in boot Added after 6 [minutes]:I've transplanted the BL from a 1mb Tuya device into a dump of an OBKd BL602 dump but this made no difference. From what I was reading on Lupyuen, the BL is constructed at build from the toml file anyway, so the BL was already being created ready for 1mb device. Added after 3 [minutes]:by coincidence someone responded to my old post about this this morning Added after 23 [minutes]: Maybe I need to work out how to debug and do this

miegapele · Answer

>>21427362
Which flasher version and which toml file are you using for the module? I don't think size in itself is an issue. It should fit, absence of separate upgrade partition might be issue. Maybe there is different boot loader for that?

divadiow · Answer

1.4.8 and latest - 1.9.0 - both with 1mb ota and no-ota toml

miegapele · Answer

>>21431287 I do not see that toml for 1.4.8, there is only one with 2mb. 1.9.0 works with standard module and 1mb toml, so additional partitions are not used it seems. Do you get any boot log?

divadiow · Answer

ah, maybe I used the 1.9.0 tomls on 1.4.8 - I've tried quite a few things. yes. always to this point: Code: TextLog in, to see the code

miegapele · Answer

So it seems to crash during EasyFlash init which is somewhat expected, given there is less flash. Normally logs continue with


EasyFlash V4.0.99 is initialize success.

But this easyflash init is somewhat suspect:

[EF] Found Valid PSM partition, XIP Addr 230e8000, flash addr 000f9000
*default_env_size = 0x00000001
ENV start address is 0x00000000, size is 32768 bytes.

PSM partition is not at zero, but at 000f9000 and size is not 32768, but only 8096 bytes. This looks strange. Although same logs work with 2mb flash...

p.kaczmarek2 · Answer

maybe let's comment out easyflash and give it a try? I should boot into AP mode with default obk config.

miegapele · Answer

>>21431575
Seems like 32k might be needed.
Could you try this toml file, before we try code changes?

[pt_table]
#partition table is 4K in size
address0 = 0xE000
address1 = 0xF000

[[pt_entry]]
type = 0
name = "FW"
device = 0
address0 = 0x010000
size0 = 0xD7000
address1 = 0x000
size1 = 0x000
# compressed image must set len,normal image can left it to 0
len = 0

[[pt_entry]]
type = 3
name = "media"
device = 0
address0 = 0x0E7000
size0 = 0x2000
address1 = 0
size1 = 0
# compressed image must set len,normal image can left it to 0
len = 0

[[pt_entry]]
type = 4
name = "PSM"
device = 0
address0 = 0x0E9000
size0 = 0x8000
address1 = 0
size1 = 0
# compressed image must set len,normal image can left it to 0
len = 0

[[pt_entry]]
type = 7
name = "factory"
device = 0
address0 = 0x0F1000
size0 = 0x7000
address1 = 0
size1 = 0
# compressed image must set len,normal image can left it to 0
len = 0

#if user want to put RF calibration data on flash, uncomment following pt entry
#[[pt_entry]]
#type = 8
#name = "rf_para"
#device = 0
#address0 = 0x1FF000
#size0 = 0x1000
#address1 = 0
#size1 = 0
## compressed image must set len,normal image can left it to 0
#len = 0

divadiow · Answer

Added after 4 [minutes]:erased whole flash. changed to GA build and did again. loops

divadiow · Answer

gets further (pic animated) Code: TextLog in, to see the code

miegapele · Answer

So it's boot looping and not freezing? Then that feels like power problem... How are you powering this?
The same might be with standard build, it tries to erase some flash and that also requires power.

divadiow · Answer

oh wow. I thought it was power too but this PSU is usually fine with BL602 - even at 3.5v it was looping. Made VCC even shorter and now it's OK. 🙄

Added after 2 [minutes]:

full successful boot

Log in, to see the code

miegapele · Answer

Good!. I think normal firmware will work too. You might need to use toml I provided though, not sure. BL602 is rated up to 3.6V, so should be no issue with that.

divadiow · Answer

also, is this an opportunity to switch to new SDK for 1mb OBK releases?

Added after 16 [minutes]:

would you like me to flash with any other toml now?

These BL602s are SO fussy. it started looping again and always at wifi AP join. Made VCC cable even shorter at 3.55v and now OK again.

miegapele · Answer

I see some capacitors on the main board. Might be not enough decoupling on bare board. I think you should try standard build, maybe with my toml, that 8kb PSM partition feels wrong in the other toml.

divadiow · Answer

maybe time to get a decent bench PSU. Added after 21 [minutes]: (forgive the side-bar on the power issue) bare board being the module breakout? XL4015 looks OK?

miegapele · Answer

I mean these two:

Cozylife DS-1211AN 3Gang Touch Switch: 1MB BL602L10 [XT-BL12][DT-BL12] - Images, Firmware & Boot

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Topic summary