[BK7231T] My HTTP server, configurator, MQTT support from Home Assistant

Yes, but the answer will be given tomorrow

OK. 1. step: i added 0 == g_bHasWiFiConnected

Thank you @p.kaczmarek2 for this firmware!

Here's another lightbulb that is compatible:
Name: Airam Smart A60 827-865 RGB 806lm E27 OP.
Specs: 9W 2700-6500K RGB E27 806lm
Chip: BK7231N (plus 8P5772? and 8P1638? which seems to be controlled with just PWM signal)
Text on PCB: 46.4LH21095

Disassembly:
1. Remove rivet on end of the bulb with knife or screwdriver. There are no threads on it.
2. Metal screw part is screwed in place and pressed into place. Loosen metal gently with a knife/screwdriver and unscrew metal part from plastic.
3. Ball part is glued in place. Gently run a knife or screwdriver around grove and remove it
4. There is a metal plate with leds visible which is also glued. Remove glue with knife or a screwdriver
5. You should now be able to remove LED PCB and microcontroller PCB.

Programming:
Backup chip before programming!
Pinouts are marked on PCB.
1. Solder 1 wire to 3.3v and 2 wires to GND
2. Solder wires to U1_RX and U1_TX
3. Connect your serial adapter to U1_RX, U1_TX, and GND
4. Connect a power supply to 3.3v and GND
5. Start programming command: uartprogram -w -s 0 -d /dev/ttyUSB0 -u -b 115200 OpenBK7231N_QIO_1.0.8.bin
6. Connect CEN to ground briefly, programming should start. This needs to be done quickly, there is a timeout. Restart programming command if timeout was reached.

Confirmed working with firmware version 1.0.8

Configuration:
Set the following pins as PWM
P6 - GREEN COLOR
P7 - RED COLOR
P8 - BLUE COLOR
P24 - COLD WHITE COLOR
P26 - WARM WHITE COLOR

Images:

theosoft wrote:

Code: text Expand Select all Copy to clipboard

if(g_connectToWiFi){
	g_connectToWiFi --;
	if(0 == g_connectToWiFi && 0 == g_bHasWiFiConnected) {
		const char *wifi_ssid, *wifi_pass;
		wifi_ssid = CFG_GetWiFiSSID();

Was that necessary? From a quick glance at code, not, but it's late here in Poland.


@faster_harder_coder - great news and description, altough I'd first look for LDO on the board because using 5V from USB is easier.
By the way, there is supposedly a tuya-cloudcutter that supports BK chips, so wiring might not be needed and first upload could be done with OTA.

@p.kaczmarek2

Unfortunately I’m not sure where to get the same bulb from online
I got the bulbs from local shop sold on clearance price because of the flicker issue

My bulb is still restarting with latest 1.08
Probably whatever is causing the flicker is also causing the reboot with openbk. So this could be hardware issue

Dodano po 6 [minuty]:

@faster_harder_coder

Quote:

Disassembly:
1. Remove rivet on end of the bulb with knife or screwdriver. There are no threads on it.
2. Metal screw part is screwed in place and pressed into place. Loosen metal gently with a knife/screwdriver and unscrew metal part from plastic.
3. Ball part is glued in place. Gently run a knife or screwdriver around grove and remove it
4. There is a metal plate with leds visible which is also glued. Remove glue with knife or a screwdriver
5. You should now be able to remove LED PCB and microcontroller PCB.

Do you mind sharing a video for this? Just to avoid completely damaging the bulb case

Also, for tuya-cloudcutter you can dump your firmware here so it gets added to list of devices. Should be able to flash openbkt via ota method

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

theosoft wrote:

Yes, but the answer will be given tomorrow

OK. 1. step: i added 0 == g_bHasWiFiConnected

Code: text Expand Select all Copy to clipboard

if(g_connectToWiFi){
	g_connectToWiFi --;
	if(0 == g_connectToWiFi && 0 == g_bHasWiFiConnected) {
		const char *wifi_ssid, *wifi_pass;
		wifi_ssid = CFG_GetWiFiSSID();

Update: Uptime till now 12:00... and yes, the extra flag is needed
Update 2 : Module uptime 14:00h but 1 reconnect 1h ago. Uptime in wifi-router now only 1 h again

So it works?
I am suprised that extra flag is needed, because I set the reconnect timer in the same place where I set g_bHasWifiConnected...

Edit: started working on ADC, but the easy drivers for that seems to be missing (BkAdcInitialize and BkAdcTakeSample):

One variable is the delay time value decreased to zero. The other is the state flag from the Wifi state machine. I have seen, when the time value reaches 0, then wifi was always reseted. So i blocked that with the state flag.

The result is ok for me. Actualy, no Wifi reset since 13h ...
Modul is reachable since 2 days w/o manual action ....
regards

Ah, I see now. Connected event may happen with a certain delay.

I am reorganizing most of the codebase to support some new platforms. Take care, new version might have some bugs, but I will do my best to sort them out.

Can anyone here help with testing?

Hi, BLE is supported? It would be neat to use the power socket for presence detections in home assistant.

Cheers

Are you asking because you're following my activity on the repository?

No, not BLE, but the BL602.

ferbulous wrote:

And there’s also this gu10 ewelink bulbs that use BL602. I did order some ESP-01D modules to replace this

pvxvictor wrote:

BL602 IoT SDK (Pine64 fork) https://pine64.github.io/bl602-docs/#
https://github.com/bouffalolab
https://lupyuen.github.io/articles/book

I have added BL602 support to OpenBeken and now I support 4 platforms: BK7231T, BK7231N, XR809 and BL602.




The port is very prelimary and misses some of the important features, like configuration saving to flash memory, but I am planning to add those as well in the upcoming days.


And about the BLE... can you point me towards some resources about the thing you're talking about, some technical documentation or anything? I never used BLE with HA.

EDIT: BL602 update - GPIO testing:




My Tasmota replacement is starting to support BL602 as well.

Here you go: https://circuitdigest.com/microcontroller-projects/ble-based-proximity-control-using-esp32

And an example with Openwrt: https://github.com/devbis/ble2mqtt

I think I can be reduced to 2 main steps:
1- get Bluetooth working (being able to pair a device with the bk7231), and with that have values like distance to report to HA
2- send previous mentioned data to mqtt, so it would be auto discovered in HA having mqtt

Dodano po 4 [godziny] 52 [minuty]:

btsimonh wrote:

pepesuriano wrote:

if you know the offsets

look in bkcdriverflash.c for the partition table.
app starts at 0x11000, boot loader before that.
I tried SPI via ESP32 first, and was unsuccessful. RPi worked after some coaxing...
Theoretically, you should only need SPI if the bootloader is broken - in your case the serial flashing is not working, correct?
So if your serial connections are ok, you could try first putting the std bootloader in from 0x0 - 0x11000, and then retry serial flashing.
I had to SPI because I overwrote the bootloader whilst developing the OTA flashing .
If you do get SPI working, be sure to read all 2Mbyte as a backup first!!!
And don't overwrite the RF partition... I don't think we have calibration yet.

Sorry, I looked around the repositories of https://github.com/openshwprojects and I didn't found bkcdriverflash.c, can you provide me the link to give it a look?

I also tried to run binwalk on file "OpenBK7231N_QIO_1.0.9.bin" of https://github.com/openshwprojects/OpenBK7231T_App/releases/tag/1.0.9 but nothing show, it's encrypted? This is the correct file for flashing bk7231 right? I want to know if it is the file that I should use with my programmer and the bootloader must be extracted from there.

What are you trying to achieve? It's encrypted.
QIO is for N, and UA is for T.
https://github.com/tuya/tuya-iotos-embeded-sd..._os/beken378/func/user_driver/BkDriverFlash.c

By the way, I will rewrite a flash vars save method soon. It has to be done to support multiple platforms smoothly. This will result in configuration loss for all users - so you will all have to reconfigure WiFi pass etc on all devices (they will become open access point if you OTA them with newer binary).

CB3S based door sensor:

https://www.aliexpress.com/item/4000790781739.html

Ali lists it as DS06 but the device itself says D06 on the back.

This seems to be an older ESP based revision on FCC.
https://fccid.io/2ANK8-D06/Internal-Photos/09-D06-IntPho-4574559

Thanks, I will buy this module and make sure it's supported.

Right now I am not even sure, what is this big SOIC chip, is this TuyaMCU? Doesn't seem required in this case. A step up converter? I see no inductor and no schottky diodes here....
For reference, see sensor described here:
https://www.elektroda.com/rtvforum/topic3806769.html

Dodano po 7 [godziny] 9 [minuty]:

BL602 support (with GPIO, MQTT, PWM, flash save config, etc) has been added to the firmware.
So now I support 4 platforms: BK7231T, BK7231N, XR809 and BL602.
I have added support for this device (MWIR-RGB Magic Home Pro RGB):
https://www.elektroda.pl/rtvforum/topic3881416.html#19944184
See photos:


You can control color, brightness and turn device on or off (turned off device does not forget the color and brightness settings)
The only missing part is that HA is not yet able to read back the brightness.

UPDATE - ZN268131 is using WB2S. Guide and support is on the way:

It's hard to flash because you have to cut the RX trace.
Firmware backup (gotta send this to cloudcutter guys, along with photos so they can update their OTA list):
ZN268131_..2s.zip (4.65 MB)You must be logged in to download this attachment.


EDIT:
@ferbulous are you here? I think I solved your problem. Your color range was 0-255 instead of expected 0-100. I added automatic scalling, I will commit changes soon. Can you retest?

Hello again,

@p.kaczmarek2
By any chance, do you know how to flash the RTL8710BN? I've noticed you created a fork of tuya SDK for this module. Were you able to do this yet?

@kuba2k2 Yes I know how to flash RTL8710BN. At first I considered it a dead case, but then a crazy guy with 96 bulbs showed up:

and we struck a deal that I will do my best to support this chip, while he will send me a small donation of bulbs for testing.

I already did a basic flashing test and managed to run "Hello world" on my single RTL that I had in my stock already:
https://www.elektroda.pl/rtvforum/topic3815120.html

NOTE: this is really this chip (uart log shows strange name):

The test configuration:



(screenshot above shows this running: https://github.com/openshwprojects/OpenRTL871...mmit/defd90389c455dc58f710d26941d391128463c3c )
but sadly, I bricked it's bootloader and have no spare ones. I could try programming the SPI memory directly, but I have no tool for that at hand and I have no original SPI content backup... I am waiting for the bulbs donation to arrive.

I will be posting both BL602 programming and RTL programming guides here soon, so don't worry, each step will be documented as good as I am able to.

So far, today, I posted BL0942 LSPA9 socket support guide, right now only in Polish:
https://www.elektroda.pl/rtvforum/topic3887748.html#19984436
Here is how it looks in HA:






I am very optimistic when it comes to new chips, I already support 4 platforms - BK7231T, BK7231N, XR809, BL602 and there is a fair chance of supporting RTL and W600. It's a sign of new times for IoT cloud-cutting trend, because so far people only were desoldering non-ESP chips and replacing them with ESP modules bought on Ebay, which in my opinion is insane. Don't waste good MCUs.

@kuba2k2 if you have some smart devices , know C basics, and would like to contribute, feel free to make a pull request, but keep in mind that I do a lot of rapid changes and improvements on the codebase, so maybe try to consult changes with me before attempting them. Still, any help is welcome.

Ah, right, of course it has a SPI flash. That should be easy then, if only I get the metal shielding off..

My WR3 is fortunately replaceable with an ESP12, but I also wanted not to throw away the original one. Can you briefly describe what tool and hardware did you use to flash it? I think I'll figure the rest out.

Also is this a public discord server? If yes, could you send an invitation link somehow? I could maybe contribute some info there or ask for help.

Where did you get WR3 from? Which RTL chip exactly is inside?

It would be great if you wanted to help me with RTL firmware, at least check if it compiles correctly and try to get threads and pins and stuff running (without even porting OpenBeken).
Run the "access point demo", etc.
I will help you to get this programming, feel free to ask any questions in this thread and report your progress here. This is the main topic.
https://developer.tuya.com/en/docs/iot/burn-and-authorize-wr-series-modules?id=Ka789pjc581u8

the documentation above is a mess but all you should know is this:
1. build with my SDK
2. power chip with 3.3V
3. ground RX , power off, power on (i. e. reboot with RX grounded)
4. disconnect RX from ground
5. rx and tx to USB to UART converter
6. use https://github.com/openshwprojects/OpenRTL871...sdk_for_rtk_871x/tools/amebaz-image-tool-v2.2 to flash


7. to run firwmare, reboot chip again

As far as I know I am the first one to even flash this Tuya-flavoured chip so if you need help, ask here. But I've send you a PM.

Thanks. I didn't even realize the most obvious place for instructions, which are Tuya docs. I will try running this later.

The WR3 is from a touch panel light switch from Shopee (I'm not sure if I should post links here). I don't know which chip is in this, as it has a metal shielding. But I can assume that tuya docs are not wrong and it's an RTL8710BN.

The board also has something that looks like TuyaMCU (16-pin SOIC with no marking) and another SO8 IC with a crystal nearby, which is probably a 433MHz receiver (as the switch has this feature).

Would you be able to get a direct read from SPI memory (not by some some UART tool, but a direct read)?
It would help me continue my development.

As for the links, please just post screenshots from pages because screenshots are safe on our Elektroda images hosting and won't expire.

Dodano po 16 [minuty]:

kuba2k2 wrote:

The board also has something that looks like TuyaMCU (16-pin SOIC with no marking) and another SO8 IC with a crystal nearby, which is probably a 433MHz receiver (as the switch has this feature).

I am not sure, but from my experience (and if you read my tearedowns) you will see that there is usually an unmarked touch button controller chip in soic8 or 16. Second soic8 chip with crystal is indeed 433MHz recv (with buzzer?)

There's no buzzer. Both chips are unmarked. One of them SOIC16, and another SOIC8, with crystal and probably an antenna trace.

p.kaczmarek2 wrote:

Would you be able to get a direct read from SPI memory (not by some some UART tool, but a direct read)?

I'm not sure, as I won't be able to re-attach the shielding, and I would probably damage the entire module, and I only have a single piece.

EDIT: you mention grounding RX, but Tuya docs say to ground Log_TX.. which one then?

kuba2k2 wrote:

I'm not sure, as I won't be able to re-attach the shielding, and I would probably damage the entire module, and I only have a single piece.

What does the Tuya log output say?

kuba2k2 wrote:

you mention grounding RX, but Tuya docs say to ground Log_TX.. which one then?

It was already a week ago but I think that it's TX of RTL module and RX of my USB to UART converter.

Okay, I have managed to flash this realtek. With your code I got "Hello world" on the other UART line, and with another code I actually got a working AT-like command shell.


If you do a dedicated thread for the Realtek modules (not to pollute this thread too much), I can post a way of flashing it, because tuya's methods suck and don't work anyway.

Are AT commands able to create access point or join another WiFi network?

I assume you just launched one of Realtek examples from this SDK:
https://github.com/openshwprojects/OpenRTL8710BN
There are #define like CONFIG_EXAMPLE_UART_ATCMD to select examples.
And here you call example entry:

See commit:
https://github.com/openshwprojects/OpenRTL871...mmit/defd90389c455dc58f710d26941d391128463c3c


Feel free to post information here. It will be closely related to OpenBK because I will port OpenBK to this platform as soon as I get RTL module. In any case, I can move posts, split topics, etc later

I have prepared a HAL for supporting multiple SDKs with that in mind:
https://github.com/openshwprojects/OpenBK7231T_App/tree/main/src/hal


PS2: Can you do a pull request on my Repo with working Access point/AT cmd demo? I remember having crashes when trying to run it.

p.kaczmarek2 wrote:

I assume you just launched one of Realtek examples from this SDK:

No. I launched realtek's official SDK:
https://github.com/ambiot/amb1_sdk

It doesn't have ugly Tuya makefiles, tuya_iot.a libs, weird OTA images, and simply works. I would highly recommend you to base your following work on this SDK instead of the Tuya one. This amb1 is even documented; has PDF files and C API documentation. If you look closely, you can even find an Arduino core in ambiot.

And which flashing method did you use?

tuya_iot.a is not required for building. The only question is would binary built with that SDK work with tuya-cloudcutter?
https://github.com/tuya-cloudcutter/tuya-cloudcutter
(according to tuya-cloudcutter guys, RTL chips a potentially vulnerable to their exploit).

EDIT: the SDK you linked seems like the vanilla version of the one I am using, just without Tuya.

p.kaczmarek2 wrote:

EDIT: the SDK you linked seems like the vanilla version of the one I am using, just without Tuya.

Yes. And documented, and without their crappy build system.

p.kaczmarek2 wrote:

The only question is would binary built with that SDK work with tuya-cloudcutter?

Why wouldn't it?

p.kaczmarek2 wrote:

And which flashing method did you use?

using ImageTool_v2.3.1, with Log_TX to GND during startup, flashing image2_all_ota1.bin to offset 0x0800B000.

EDIT: I created a firmware dump of the stock bootloader and everything else, except for ota1 region. Will post it somewhere when I clean it up and split into appropriate files.

I am not able to flash anything by UART because bootloader is broken, so I need a SPI memory dump.

So it seems you're still using the same flashing method as I. Still, I will check the SDK you mentioned. It really might be a better option.

Try this one, it's extracted from my WR3 using a simple block of code I wrote and flashed. I also have the stock Tuya firmware binary for this particular touch switch. (the "DF62" is a simple checksum; I would prefer to name all firmware dumps as such, to be able to compare them easily)

You can flash this to offset 0 of the SPI flash, by using a Raspberry Pi with flashrom, or an arduino with a programmer from this website:
http://skproj.ru/programmator-spi-flash-svoim...ing_wp_cron=1649756425.0225400924682617187500

I'm attaching the programmer app, translated from Russian to English.

Currently I have 3 different bootloaders (two from github SDKs, from tuya and ameba1)