Flashing OpenBeken on BK7238 Module (WB43-M5 V1.1) with Surplife App

>>> Looks like a random crash? What does the reboot reason say?

It crashes in the same manner every time. Never connects to wifi.
I have to power cycle to get something on debug for a few seconds.

>>21376434

I bought two of these exact bulbs with a BK7238 Module (WB43-M5 V1.1) with Surplife App and were able to flash it using the following pin layout, see image below.

Sorry for the small font indicating RX, TX, 3V3 and GND.



Pin layout for RGB driver; was working and then stopped, maybe I have the wrong pins?

"pins": {
"24": "BP5758D_CLK;0",
"26": "BP5758D_DAT;0"
},

Hey, that's a nice finding! Do you have original firmware dump?

Also, can you elaborate, what do you mean by "stopped working"? You mean it stopped after OTA or when? Was it working fully correctly, or did you just get random colors once? Because you know, if you have chosen wrong I2C LED driver, you might have gotten a random color once or twice, without it working fully.

>>21633362

The light stopped turning on and off, can't change the color, like the pins are wrong. It was working correctly, could change the color and brightness and then no response after a while, I rebooted but light would not come on, I am concerned that wrong pins could have broken the BP5758 chip. I reset to factory settings in OpenBeken, reconfigured WiFi, then select the BP5758 driver CLK and DAT, reboot, but no light comes on. Am a bit confused.

I do have a backup of the original firmware.

Well, since you're saying you reconfigured it from 0, it seems there are not much options... or are there? Can you power it off fully, wait, and power it on again?

Was it super bright before it broke?

>>21633375

Yes it was bright, I was so convinced I have the config correct. I have tried power off and on. I will try more configurations. As long as the BP5758 is fine. Thanks for trying to help.

I hope your BP5758 isn't burnt out.

If you have the same device as original post then what looks like power levels in the factory boot log can be seen



To mimic this would need to have been set with command


BP5758D_Current [MaxCurrentRGB][MaxCurrentCW]

>>21633387

Damn, that might just be it. What a pity if I fried the BP5758 I tried the command, but sadly it's still dead Jim

could flash your backup back to be 100% sure I guess

Added after 15 [minutes]:

was it bought from Ali Express? Could I trouble you for the exact product link if yes?

thanks

>>21633397

Not Ali Express but here in South Africa @ https://www.geewiz.co.za/smart-lights/156246-...ticolour-bayonet-compatible-surplife-app.html

Maybe a cold joint? Soldering issue?

It seems we need to lower the default current, @divadiow

p.kaczmarek2 wrote:

It seems we need to lower the default current, @divadiow

yes. and/or if @max4elektroda channels/maps/current stuff ever got realised in config page in GUI then the starting current settings could be low. but lower defaults now would be quicker to do I assume

ref: https://www.elektroda.com/rtvforum/topic4132298.html

@divadiow though I made some suggestions to alter pins, roles and channels page, current (in this context ) is new to me.

Letting my imagination run away with me! In my head I'd extended the idea to include settings fields for various drivers if chosen from the drop-down

Feel free to draft the idea and I'll try to see, if/how this might be realized ...

EDIT:
I think this would need a "driver based" configuration page, like

Add new "driver/role...", e.g. from a "select"
BP5758D
--> select Pins for CLK and Data
--> select other settings like MaxCurrentRGB, MaxCurrentCW, ...

I tried once to let copilot create such a page, but gave up after the 10th or so iteration, far from a usable result.
Would probably needed to be coded by hand (or using better prompts )

Weird news, I was able to flash back the backup firmware. I then paired it with the app on iOS, but the bulb did not want to turn on or anything, and I presumed it was fried.

Then the app said there is a firmware upgrade for the bulb. I upgraded it, and the bulb then started to work, so nothing is fried.

Now I don't know whether I want to try OpenBeken again; I might not be lucky a second time around.

BTW, in HomeAssistant you can use the "Magic Home" plugin to use these lights with the original firmware - https://www.home-assistant.io/integrations/flux_led/

Some more pictures of my bulb below, just a FYI.






When I have time again to waste, I will try Flash again with OpenBeken.

interesting. I wonder if this module is in any bulbs from Ali Express.

Maybe I can find a BP5758D bulb in my collection and hang a BK7238 module off it somehow in place of what it has 🤔

Added after 4 [minutes]:

xref https://github.com/tuya-cloudcutter/tuya-cloudcutter/issues/765

>>21635385

I noticed that it is not 'Tuya' compatible. I was impressed by how stable OpenBeken was on it, just the BP5758D that I could not get working; maybe I did something wrong in trying to get it working. Anyway, here are pictures of the box.

PS. Some information on the BP5758D - https://developer.tuya.com/en/docs/iot-device-dev/driver_i2c_bp5858d?id=Kb7bciwq50zfc