logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

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

Jinaria 6087 47
Best answers

How can I flash OpenBeken onto a BK7238 WB43-M5 V1.1 bulb module used with the Surplife app?

Use Easy Flasher or BKFIL to write the BK7238 OpenBeken build; in Easy Flasher, place `OpenBK7238_QIO__beken_sdk_f866976df64b.bin` in the firmwares folder, rename it to `OpenBK7231N_QIO__beken_sdk_f866976df64b.bin`, enable advanced options, and select `skip key check` [#21376381] On this WB43-M5 / SurpLife bulb, flashing the QIO image to `0x0` did not boot for one tester, but restoring the original firmware and then flashing `OpenBK7238__beken_sdk_f866976df64b.rbl.bin` from `0x132000` made the AP broadcast [#21376560] If the device still fails to boot, the earlier boot issue was traced to using standard Tuya encryption keys instead of no encryption [#21438385] The current BK7238 builds are still experimental, and at least SPIDMA was reported as not working yet [#21438394]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #1 21375936
    Jinaria
    Level 8  
    I have some light bulbs with BK7238 Module (PCB Marking WB43-M5 V1.1) - Surplife app. I bought the same bulb from the same seller and they used to have BL602 modules. Now they are shipping it with this chip, same app, same box.
    I managed to dump the flash and rom, how can I flash OpenBeken?

    You can check the dumps here: https://github.com/tuya-cloudcutter/tuya-cloudcutter/issues/765

    Moderated By p.kaczmarek2:


    I am splitting this to separate topic from https://www.elektroda.com/rtvforum/topic4064640.html

    Attachments:
    • RGBCCT-Bulb-BK7238-Factory-rom.zip (6.84 KB) You must be logged in to download this attachment.
    • RGBCCT-Bulb-BK7238-Factory.zip (673.62 KB) You must be logged in to download this attachment.
  • ADVERTISEMENT
  • Helpful post
    #2 21375947
    divadiow
    Level 38  
    Interesting. I saw your post over there and was planning to look over that firmware backup in the morning.

    BK7238 development is still a work in progress but there are OpenBK7238 firmwares that could be flashed

    https://www.elektroda.com/rtvforum/topic4092465-60.html#21361724

    Added after 7 [hours] 28 [minutes]:

    so yes, your device is a Zengge/SurpLife RGBCCT - BulbD46D - with BP5758D

    Here is boot log 115200/2000000

    Code: Text
    Log in, to see the code


    Added after 7 [minutes]:

    maybe this new device should be its own new thread @p.kaczmarek2 for BK7238 testing/progress?
  • #3 21376355
    Jinaria
    Level 8  
    Thanks,

    - I'm not sure how to flash the experimental firmware, I dumped the flash and ROM using ltchiptool but it cannot write to the flash.
    - How did you get the boot log? Did you flash it to a development board?
    - I'll add PCB and module photos later this evening.
  • Helpful post
    #4 21376381
    divadiow
    Level 38  
    Jinaria wrote:

    - I'm not sure how to flash the experimental firmware, I dumped the flash and rom using ltchiptool but it cannot write to the flash.


    Easy Flasher can be used to read/write firmware from BK7238 - https://github.com/openshwprojects/BK7231GUIFlashTool

    To burn the latest BK7238 firmware, place OpenBK7238_QIO__beken_sdk_f866976df64b.bin from the attached zip into the EasyFlasher firmwares subdir and rename to OpenBK7231N_QIO__beken_sdk_f866976df64b.bin

    View of the firmware folder in BK7231GUIFlashTool.

    Be sure to reveal advanced options and to choose skip key check

    Screenshot of the Easy UART Flasher software with BK7231N selected and OpenBK7231N_QIO__beken_sdk_f866976df64b firmware chosen.

    or flash with BKFIL https://www.elektroda.com/rtvforum/topic4059172.html

    Jinaria wrote:

    - How did you get the bootlog? did you flash it to a development board?


    Yes - the NiceMCU board with XH-WBS3 module
    Attachments:
    • OpenBK7231T_App__beken_sdk_f866976df64b_OpenBK7238.zip (2.03 MB) You must be logged in to download this attachment.
  • #5 21376384
    divadiow
    Level 38  
    please be aware that not everything may work yet and that flashing is at your own risk :)
  • #6 21376434
    Jinaria
    Level 8  
    divadiow wrote:
    please be aware that not everything may work yet and that flashing is at your own risk :)


    Thank you for the step by step guide, I managed to flash the firmware successfully but for some reason the AP does not show up. I noticed that the factory firmware dump is 2MB but the experimental firmware size is only 1224KB.

    Added after 24 [minutes]:

    Cannot edit the first post, here are some photos of the smart bulb:

    Close-up of a circuit board inside a smart bulb showing electronic components. 10W smart bulb with visible technical markings. LED smart bulb circuit board with LEDs and integrated circuits. Close-up of a circuit board with visible electronic components.
  • #7 21376492
    divadiow
    Level 38  
    Jinaria wrote:
    I managed to flash the firmware successfully but for some reason the AP does not show up


    are you able to see if there is any log UART log out from TX to see if it's booting at all? I'm not sure we know much about this module. Does it have labels on the reverse of the module?

    Added after 2 [minutes]:

    if you're able to, please post clear head-on front and rear pictures of the module
  • #8 21376511
    Jinaria
    Level 8  
    divadiow wrote:
    Jinaria wrote:
    I managed to flash the firmware successfully but for some reason the AP does not show up


    are you able to see if there is any UART log out from TX to see if it's booting at all? I'm not sure we know much about this module. Does it have labels on the reverse of the module?


    Here is a boot log, seems to be in some kind of boot loop :
    Code: text Expand Select all Copy to clipboard
    BK7238_1.0.14
REG:cpsr        spsr        r13         r14
SVC:0x400000D3              0x0042F810  0x00010008
IRQ:0x400000D2  0x00000010  0x0042FC10  0x48C01942
FIR:0x400000D1  0x00000010  0x00430000  0x30602F40
SYS:0x400000DF              0x0042B820  0x00000158
ST:0x00010000
[I/FAL] Fal(V0.4.0)success
                          [I/OTA] RT-Thread OTA package(V0.2.8-beken-1133282d-20    220604) initialize success.


go os_addr(0x10000)..........
BK7238_1.0.14
REG:cpsr        spsr        r13         r14
SVC:0x400000D3              0x0042F810  0x00010008
IRQ:0x400000D2  0x00000010  0x0042FC10  0x48C01942
FIR:0x400000D1  0x00000010  0x00430000  0x30602F40
SYS:0x400000DF              0x0042B820  0x00000158
ST:0x00010000
[I/FAL] Fal(V0.4.0)success
                          [I/OTA] RT-Thread OTA package(V0.2.8-beken-1133282d-20    220604) initialize success.


    The module has RX/TX/CEN/V3.3/GND on the back.
  • #9 21376519
    divadiow
    Level 38  
    interesting.

    I'll just flash it myself. I can't remember if there was something about the QIO file. We might have to slice it up and flash from a certain address or do OTA
  • ADVERTISEMENT
  • #11 21376560
    divadiow
    Level 38  
    so yes, flashing the QIO from 0x0 (I used BKFIL) does not result in any output for me - not even bootloader.

    I've flashed your original firmware in its entirety

    Screenshot of BKFIL software with a selected binary file for flashing.

    then flashed OpenBK7238__beken_sdk_f866976df64b.rbl.bin (from zip file above - add .bin to the end) from 0x132000

    Screenshot of the BKFIL tool showing device flashing configuration.

    if you can open the COM port quick enough you'll see the tail-end of the OTA

    Screenshot of OTA process on a black terminal background.

    then the AP broadcasts

    OpenBK7238 user interface with technical data and configuration options.
  • #12 21438048
    taggbricka
    Level 7  
    I just bought (accidentally) a few of these XH-WB3S modules. I was not aware they were BK7238 based.
    XH-WB3S electronic module with labeled pins. XH-WB3S module with visible connectors and markings.


    However I have reprogrammed one with BK723flasher like so:

    The Easy UART Flasher screen with BK7231N chip and OpenBK7231N firmware selected. The interface shows the operation is idle.

    After this the module seems to be idle after power up, draws only 4mA.
    I am wondering if some of the port pins need to be at 3.3V or 0V at startup for the module to boot correctly.
  • #13 21438126
    insmod
    Level 31  
    >>21438048
    Try this firmware, it's the latest version available.

    EDIT: deleted, this version fails to boot.
  • #14 21438169
    p.kaczmarek2
    Moderator Smart Home  
    I've seen your PR is ready to merge @insmod, is it working well now? I didn't manage to check it myself yet, first XR806 took my time and now real life stuff.
    Helpful post? Buy me a coffee.
  • #15 21438266
    insmod
    Level 31  
    >>21438169 Probably not, i just tried to flash QIO - and it failed to boot. Shows bootloader log, delays a few seconds, repeatedly. Flashing rbl works.
  • ADVERTISEMENT
  • #16 21438289
    p.kaczmarek2
    Moderator Smart Home  
    Interesting, but it worked before, right? So maybe checking last commits can give us some insights?

    I can also try to get my NiceMCU and test tomorrow morning and report back
    Helpful post? Buy me a coffee.
  • #17 21438378
    taggbricka
    Level 7  
    Flashed the (renamed) "OpenBK7231N_QIO_1527_merge_2fec4f7723d8.bin" to a new BK7238. I don't think it started afterwards.
    Including the flasher log and the backup image from the brand new device if it might be of any interest.
    Attachments:
    • readResult_BK7231N_QIO_tttt_2025-13-2-20-01-02.bin (2 MB) You must be logged in to download this attachment.
    • Burn_log.txt (31.5 KB) You must be logged in to download this attachment.
  • #18 21438385
    insmod
    Level 31  
    Fixed boot, caused by encrypting the binary with standard tuya keys, instead of no encryption.
    Attachments:
    • OpenBK7231T_App_1527_merge_2cd87167de38_OpenBK7238.zip (1.6 MB) You must be logged in to download this attachment.
  • #19 21438394
    insmod
    Level 31  
    @p.kaczmarek2 now it can probably be merged, boots ok.
    Everything bar SPIDMA should work.
    For some reason, flasher fails to read config, encryption problems or something else?
    Code: text Expand Select all Copy to clipboard
    Will try to read device flash MID (for unprotect N):
Flash MID loaded: 152085
Will now search for Flash def in out database...
Flash def found! For: 152085
Flash information: mid: 152085, icName: P25Q16HBK, manufacturer: Puya, szMem: 1000000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-31-FF-FF
Entering SetProtectState(True)...
sr: 4
sr: 4004
final sr: 4004
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Going to read encryption key...
Encryption key read done!
Encryption key: 84f67900 84f67900 84f67900 84f67900
^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^
WARNING! Non-standard encryption key!
If it's all zero, it may also mean that read is disabled.
Please report to forum https://www.elektroda.com/rtvforum/forum51.html 
Or just try using BK7231M mode 
^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^
Going to start reading at offset 0x1D1000...
Reading 0x1D1000... Ok! 
Basic read operation finished, but now it's time to verify...
Data is entirely filled with 0xff, something must went wrong!
OBK config load failed.
  • #20 21438506
    taggbricka
    Level 7  
    Lovely, Thank you!

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

    Added after 1 [hours] 6 [minutes]:

    One device starts up and then goes to zero current consumtion after 2 seconds. (other devices consumes 35mA in operation)
    Tried to reprogram it, programming succeds.

    This is on the serial port:

    BK7238_1.0.14
    REG:cpsr spsr r13 r14
    SVC:0x000000D3 0x00401C1C 0x000033A0
    IRQ:0x000000D2 0x00000010 0x00401E0C 0x09BCA98D
    FIR:0x000000D1 0x00000010 0x00401FFC 0x10F08789
    SYS:0x000000DF 0x0040192C 0x00000158
    ST:0x00000000
    [I/FAL] Fal(V0.4.0)success
    [I/OTA] RT-Thread OTA package(V0.2.8-beken-1133282d-20
    220604) initialize success.


    go os_addr(0x10000)..........
  • #21 21438705
    insmod
    Level 31  
    >>21438506 You either flashed an older firmware, or looking at wrong uart port. OBK sends log to UART1 by default, so try to connect your adapter to either P0 or P1 (i don't remember which).
    If you reflash with bootloader overwrite, then bootloader will also log to uart1.
  • #22 21439888
    p.kaczmarek2
    Moderator Smart Home  
    It seems @insmod did a very good job. Works for me at first try. I just need to update the flasher.
    Screenshot of Easy UART Flasher software showing firmware write success.
    Log from programming UART:
    Screenshot of the Serial Capture Program showing a UART programming log.
    ( didnt have time to connect debug uart)
    Screenshot showing a dialog box for connecting to a Wi-Fi network named OpenBK7238_8C10262A.

    OpenBK7238_8C10262A user interface with options for configuration, restart, and web application.

    Screenshot showing a table listing network devices and their IP addresses.
    LED RGB is on P6, P24, P26..
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #23 21439906
    taggbricka
    Level 7  
    There is something funny with my last unit.

    I reflash it with "bk7231flasherfirmwaresOpenBK7231N_QIO_1527_merge_2cd87167de38.bin"
    That works OK.
    I connect to the device AP 192.168.4.1
    There I get a full UI.
    I go to wifi setup and enter my net's local credentials and submit.
    After this the UI at 192.168.4.1 is still active. I can navigate in it freely. The wifi credentials are there to see.
    Then I power cycle the device, it powers up to 35mA and after 2 seconds crashes to 5mA. It is not possible to access anymore.

    I have repeated this twice.

    EDIT:
    I will try to check debug output and see if there is something.
  • #24 21439932
    p.kaczmarek2
    Moderator Smart Home  
    Here my BK7238 is stable:
    Screenshot of OpenBK7238 user interface showing the state of toggle switches.

    OpenBK7238 board with USB power connection, in front of a screen displaying a graphical interface.
    I am updating flasher:

    User interface of BK7231 Easy UART Flasher with a dropdown menu selecting BK7238 chip.
    Helpful post? Buy me a coffee.
  • #25 21439934
    divadiow
    Level 38  
    p.kaczmarek2 wrote:
    I am updating flasher:

    YES!!
    (and an option to relax filename matching restrictions?) :D :D <3
  • #26 21439937
    p.kaczmarek2
    Moderator Smart Home  
    Is Custom read working or not? I don't really remember at the moment:

    Screenshot of software for downloading and flashing firmware on BK7231T/BK7231N devices with open configuration windows.
    Helpful post? Buy me a coffee.
  • #27 21439939
    divadiow
    Level 38  
    p.kaczmarek2 wrote:
    Is Custom read working or not? I don't really remember at the moment:

    I haven't got round to testing it yet

    Added after 11 [hours] 39 [minutes]:

    insmod wrote:
    Everything bar SPIDMA should work.

    If this is a showstopper for SPI/PixelAnim/SM16703P then I can test using

    https://www.elektroda.com/rtvforum/topic4090758.html
    https://www.elektroda.com/rtvforum/topic4064640.html

    when/if required
  • #28 21440237
    p.kaczmarek2
    Moderator Smart Home  
    I am fixing small stuff for BK7238, I altered flash tool for it, I am fixing OTA in the Web App, etc, I will try to fix DHT11 and later maybe SPI DMA, depending on what is the problem, is the SPI DMA driver totally missing or just different? https://github.com/OpenBekenIOT/webapp/commit/39fde8263f682323bb4b8ced6b0cfe8fa3b1b006

    Added after 1 [minutes]:



    Screenshot of the OTA interface for the BK7238 chipset.

    Added after 1 [minutes]:

    ajh one more fix needed
    https://github.com/OpenBekenIOT/webapp/commit/7cdc1daadd54a10a01bbac2516e3e56d96775a19
    Helpful post? Buy me a coffee.
  • #29 21440318
    taggbricka
    Level 7  
    Here is the startup debug output on pin P0.

    "bk7231flasherfirmwaresOpenBK7238_QIO_1527_merge_2cd87167de38.bin"
    Flashed with today's version of bk7231flasher.
    Attachments:
    • Dump.txt (15.9 KB) You must be logged in to download this attachment.
  • #30 21440502
    p.kaczmarek2
    Moderator Smart Home  
    Looks like a random crash? What does the reboot reason say?

    I'm testing BK7238 NiceMCU on latest release with MQTT and it seems ok so far:
    Screenshot of OpenBK7238 interface displaying temperature and humidity data.
    User interface of a monitoring application for BK7238 device with charts of temperature and humidity, event log, and light control.
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

✨ Discussion revolves around flashing OpenBeken firmware onto light bulbs equipped with the BK7238 module (PCB Marking WB43-M5 V1.1). Users share experiences and methods for successfully dumping and flashing firmware, including the use of tools like Easy Flasher and BKFIL. Several users report issues with boot loops and connectivity after flashing, while others provide insights into the flashing process, including the importance of using the correct firmware size and addressing. The conversation highlights the ongoing development of the BK7238 firmware and the need for careful handling during the flashing process to avoid bricking the devices.
Generated by the language model.
Today's popular

FAQ

TL;DR: If you have a 2 MB Surplife BK7238 bulb and "QIO from 0x0" boot-loops, flash the original dump first, then write the .rbl OpenBeken image at 0x132000; one tester said, "then the AP broadcasts." This FAQ is for people moving a WB43-M5 V1.1 bulb from stock firmware to OpenBeken without losing recovery options. [#21376560]

Why it matters: These BK7238 bulbs can look successfully flashed yet still fail to boot, hide the AP, or stop driving the BP5758D unless you use the right image type, address, UART, and current settings.

Metoda Plik Adres flash Wynik w wątku
Bezpośredni flash QIO OpenBK7238_QIO...bin 0x0 brak startu lub pętla bootowania
Flash OTA-style OpenBK7238__...rbl.bin 0x132000 AP pojawia się i firmware startuje
Przywrócenie kopii fabrycznej pełny dump producenta cały flash urządzenie wraca do stanu wyjściowego

Kluczowy wniosek: Najważniejsza różnica nie dotyczy samego narzędzia, lecz formatu obrazu i adresu zapisu. W tym wątku działający scenariusz dla WB43-M5 V1.1 to zachowanie kopii fabrycznej oraz wgrywanie obrazu .rbl na 0x132000, a nie obrazu QIO od 0x0. [#21438266]

Quick Facts

  • Fabryczny dump żarówki miał 2 MB, a testowany eksperymentalny firmware miał około 1224 KB; sama różnica rozmiaru nie oznacza jeszcze błędu, ale była pierwszym sygnałem, że układ startuje inaczej niż pełny obraz producenta. [#21376434]
  • W logu fabrycznym widać 115200/2000000 jako sprawdzane szybkości UART oraz wersję firmware z datą buildu 20240425 i identyfikatorem 35_243_20240425_ZG-BK38-BP101. [#21375947]
  • Na module pokazano punkty RX, TX, CEN, 3.3V, GND na spodzie, co daje komplet do zasilenia i zczytania logu bez zgadywania podstawowych pinów serwisowych. [#21376511]
  • Jeden z testów wykazał pobór około 4 mA po błędnym flashu, podczas gdy działające sztuki pobierały około 35 mA po starcie; to praktyczny wskaźnik, czy firmware faktycznie ruszył. [#21438048]
  • Dla tej żarówki log fabryczny podał ustawienie sterownika LED rgbwc_ele 8 8 8 30 30, a w OpenBeken zasugerowano komendę BP5758D_Current 8 30, aby odwzorować prądy RGB i CW bliżej ustawień producenta. [#21633387]

How do I flash OpenBeken on a BK7238 bulb with a WB43-M5 V1.1 module from the Surplife app ecosystem?

Use the stock dump as your safety net, then install OpenBeken with the OTA-style image path that worked in this thread. 1. Read and save the full factory flash first. 2. Restore that original image if needed, then write OpenBK7238__...rbl.bin at 0x132000. 3. Reboot and look for the OpenBeken AP before changing Wi‑Fi or LED settings. This exact flow brought up the AP on the Surplife BulbD46D with BP5758D after direct QIO flashing failed. [#21376560]

What is the correct way to use Easy Flasher or BKFIL for BK7238 when ltchiptool can dump flash and ROM but cannot write them back?

Use Easy Flasher or BKFIL for writing, because ltchiptool in this case only handled reading. In Easy Flasher, place the BK7238 test firmware in the firmwares folder, rename it to the expected BK7231N-style filename, enable advanced options, and select skip key check. BKFIL was also used successfully for writing both the factory dump and the .rbl image. The key point is that BK7238 support was still experimental, so write support depended on these specific tools and file naming workarounds. [#21376381]

Why does a BK7238 module boot loop after flashing the OpenBK7238 QIO image from address 0x0?

It boot-loops because the direct QIO image at 0x0 was the failing path in this thread. One boot log repeatedly showed go os_addr(0x10000) and restarted instead of reaching a working AP. Later testing confirmed that flashing QIO directly could fail to boot, while the .rbl image flashed from 0x132000 worked. A later fix also identified one boot issue as wrong encryption handling during build, which broke QIO boot until corrected. [#21438385]

What firmware file and flash address worked for getting OpenBeken running on the Surplife BulbD46D with BP5758D?

The working combination was OpenBK7238__beken_sdk_f866976df64b.rbl.bin flashed at address 0x132000. The tester first restored the original full firmware image, then wrote the .rbl file from that offset. He reported that if you opened the COM port fast enough, you could catch the end of OTA activity, and after that the OpenBeken AP started broadcasting. That is the clearest successful recipe shown for this exact Surplife BulbD46D and BP5758D setup. [#21376560]

How can I capture the boot log from a BK7238 module, and which UART pins or baud rates should I check?

Capture the log over UART using the exposed service pins and check both standard and debug outputs. The module back pads were identified as RX, TX, CEN, 3.3V, GND, and a later note says OpenBeken logs to UART1 by default, so you may need P0 or P1 instead of the programming UART. In the early reverse-engineering log, the tester explicitly referenced 115200/2000000 baud checks. If one port stays silent, switch UART pins before assuming the firmware is dead. [#21438705]

What is BK7238, and how is it different from older modules like BL602 or BK7231N in smart bulbs?

BK7238 is the newer Beken Wi‑Fi module that started replacing older modules in the same bulb SKU. In this thread, the buyer had previously received bulbs with BL602, then got the same seller, same box, and same Surplife app ecosystem but with a BK7238 module marked WB43-M5 V1.1. Compared with BK7231N-era tools, BK7238 support was still labeled work in progress, so image format, flasher behavior, and boot methods differed enough to break simple one-click replacement workflows. [#21375936]

What is the BP5758D LED driver, and what settings in OpenBeken matter for RGB+CCT bulbs that use it?

"BP5758D is an LED driver IC that controls RGB+CCT channels over a two-wire interface, with configurable current levels that strongly affect brightness and safe operation." For this bulb, the factory log exposed BP5758D rgbwc_ele 8 8 8 30 30, and the suggested OpenBeken command was BP5758D_Current 8 30. CLK and DAT mapping also matter; later users tried GPIO 24 and 26. Wrong current or wrong pin mapping can leave the lamp dark even when Wi‑Fi still works. [#21633387]

Easy Flasher vs BKFIL for BK7238 flashing: which tool is better for reading, writing, and recovering these bulbs?

Neither was universally better; each solved a different stage. Easy Flasher was recommended for BK7238 read/write with a rename workaround and skip key check, while BKFIL was used successfully to write the original full image and then the working .rbl file at 0x132000. For recovery, BKFIL proved especially useful because it handled whole-image restoration cleanly in the successful test. If you need predictable rollback, keep BKFIL ready even if you start with Easy Flasher. [#21376381]

Why might the OpenBeken access point not appear after a seemingly successful flash on a BK7238 bulb?

The AP can stay hidden because the wrong image type or address was used even though flashing itself reported success. One user flashed successfully but saw no AP, then provided a log showing repeated early boot output instead of a full start. Another tester reproduced that direct QIO flashing from 0x0 gave no usable output, while restoring stock and flashing the .rbl image at 0x132000 made the AP appear. Success in the flasher does not guarantee a bootable runtime image on BK7238. [#21376560]

How do I restore the original firmware dump on a WB43-M5 V1.1 bulb if OpenBeken flashing fails or the light stops responding?

Write the saved factory dump back to the chip as a full-image restore. One tester explicitly reflashed the original firmware in its entirety before trying the .rbl OpenBeken path, and a later user restored backup firmware after BP5758D control stopped working. In that later case, the bulb still needed an app firmware upgrade before normal light control returned, which shows recovery may take two stages: flash restore first, vendor update second. Keep the original dump before any experiment. [#21633920]

What does the 'skip key check' option do in BK7231GUIFlashTool when flashing experimental BK7238 firmware?

In this thread, skip key check was the required Easy Flasher setting used to bypass key validation while loading experimental BK7238 firmware. The practical reason was simple: BK7238 support was not yet finalized, and strict checks blocked or complicated test flashing. The step was shown together with advanced options and the renamed firmware file workflow. It does not mean the image is guaranteed safe; the same post also warns that not everything may work and flashing remains at your own risk. [#21376381]

How should BP5758D current be configured in OpenBeken to match factory settings like 'rgbwc_ele 8 8 8 30 30' and avoid possible damage or non-working output?

Match the factory current as closely as possible, starting with BP5758D_Current 8 30. The factory boot log showed rgbwc_ele 8 8 8 30 30, and a later warning suggested that running with higher defaults may have contributed to the lamp becoming unresponsive. One tester feared the driver was burnt, but the device later recovered on stock firmware, so misconfiguration is a realistic failure mode. Start low, confirm output, and only then change channel mapping or brightness-related settings. [#21633387]

Why would a BK7238 bulb work in the OpenBeken web UI, accept Wi-Fi credentials, and then crash after the next power cycle?

That pattern points to a runtime crash after config is saved, not a pure flashing failure. One user reached 192.168.4.1, entered local Wi‑Fi credentials, still had a working UI, then after power cycling saw current drop from about 35 mA to 5 mA within 2 seconds and lost access. Separate posts showed BK7238 stability was still being fixed around OTA, flasher updates, and smaller firmware issues. So the likely trigger was a firmware-side crash during normal startup after config reload. [#21439906]

What does the .rbl OTA image mean on BK7238, and how is it different from flashing a QIO .bin directly?

In this thread, the .rbl image was the OTA-style payload that booted correctly when written at 0x132000, while the QIO .bin written from 0x0 was the failing direct-flash path. You do not need the internal packaging details to use it safely here; the operational difference is what matters. The tester even noted you could catch the tail end of OTA over serial, then see the AP start. For this bulb, .rbl was the working install format and QIO-at-zero was not. [#21376560]

Which GPIO pins were identified for the BK7238 NiceMCU and for the WB43-M5 V1.1 bulb, including RGB pins and BP5758D CLK/DAT mappings?

For the BK7238 NiceMCU test board, RGB LED pins were identified as P6, P24, and P26. For the WB43-M5 V1.1 bulb using BP5758D, a later user reported a working flash setup and tried BP5758D mappings of GPIO24 = CLK and GPIO26 = DAT. Service pads on the module back were labeled RX, TX, CEN, 3.3V, GND. Those values give you a concrete starting map, but the thread also shows that LED control can still fail if current settings are wrong. [#21633322]
Generated by the language model.
ADVERTISEMENT