logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Tuya ATORCH S1-B/W/T/H Smart Socket Energy Monitor (BK7231N) (C3BS) (CH573F) (BL0942)

maximesharp 20802 56
Best answers

How do I fix the 10× too-high voltage reading and make the relay button work on an ATORCH S1-B/W/T/H running OpenBeken?

Use the newer OpenBeken channel types and remap the relay correctly: the voltage should be `Voltage_div100`, and the relay is controlled by dpid 131, while dpid 1 is only a relay status indicator, not a control input [#20743537][#20919646] A working setup uses `setChannelType 0 Toggle_Inv`, `setChannelType 1 ReadOnly`, then `linkTuyaMCUOutputToChannel 131 enum 0` for the relay control and `linkTuyaMCUOutputToChannel 1 bool 1` for the relay state [#20919646] For the meter values, the working mapping is `Voltage_div100`, `Power_div100`, `Current_div1000`, `Frequency_div100`, `PowerFactor_div100`, and `EnergyTotal_kWh_div1000` (with dpid 19 for power, 18 for current, 133 for frequency, 134 for power factor, 123 for total energy) [#20919646][#20910128] If Home Assistant still shows the old scale after changing the firmware, redo the HA discovery so it receives the updated MQTT configuration [#20745201]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
| New topic
  • #31 20946539
    divadiow
    Level 38  
    Posts: 5032
    Help: 438
    Rate: 891
    maximesharp wrote:
    As you can see in my post above, on this device, the CPU temp is sent on dpid 135 from tuyamcu and set on channel 7 on OBK


    Ah ok. Not from the BK7231N itself. I was curious about a temp reading for all BK7231s

    Next thing, have you had to calibrate the power on this unit itself after flashing to OBK? I bought mine to calibrate other devices flashed with OBK
  • ADVERTISEMENT
  • #32 20946773
    miegapele
    Level 16  
    Posts: 173
    Help: 15
    Rate: 29

    Beken also has some internal temperature functions, tried to make use of them, but it reports 270 for me, not sure, could it be Celsius *10?
    You can try for yourself this build
    Screenshot showing diagnostic information for an IoT device.
  • #33 20946830
    maximesharp
    Level 6  
    Posts: 13
    Rate: 1
    miegapele wrote:
    Beken also has some internal temperature functions, tried to make use of them, but it reports 270 for me, not sure , could it be Celsius *10?
    You can try for yourself this build


    There is a Temperature_div10 channel type if the temperature read 10x higher, it should fix the reading.

    divadiow wrote:
    Next thing, have you had to calibrate the power on this unit itself after flashing to OBK? I bought mine to calibrate other devices flashed with OBK


    I didn't because I wasn't able to locate some incandescent light bulb (they're banned from my country since 2009) to calibrate it, but seems to be accurate enough according to my amp meter.
    I've recently find some 35w GU10 halogen lamp, I'm waiting to receive my GU10 socket to see if the factory calibration is correct or if I need to calibrate it.
  • #34 20946859
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14587
    Help: 654
    Rate: 12609
    miegapele wrote:

    You can try for yourself this build
    Screenshot showing diagnostic information for an IoT device.

    This is a very good job, but:
    1. please encapsulate the code in a check for safe mode, I don't want to accidentally brick devices for hundreds of users
    2. is it a scaled value from Beken or raw value from ADC (that is in 0-1024 range, I guess)?

    Added after 58 [seconds]:

    divadiow wrote:

    Next thing, have you had to calibrate the power on this unit itself after flashing to OBK? I bought mine to calibrate other devices flashed with OBK

    I think that TuyaMCU is calibrated at factory on the MCU side
    Helpful post? Buy me a coffee.
  • #35 20946866
    miegapele
    Level 16  
    Posts: 173
    Help: 15
    Rate: 29

    p.kaczmarek2 wrote:
    1. please encapsulate the code in a check for safe mode, I don't want to accidentally brick devices for hundreds of users
    2. is it a scaled value from Beken or raw value from ADC (that is in 0-1024 range, I guess)?

    I'm not sure what this is, the sdk limits values to be between 50 and 700. Could be Celsius, but then 70C is sorta low.
  • #36 20946971
    hwti
    Level 2  
    Posts: 2

    p.kaczmarek2 wrote:
    The autoexec.bat posted earlier also contains 0.01W resolution setup;
    Code: text Expand Select all Copy to clipboard
    
setChannelType 3 Power_div100

    So, @hwti, can you elaborate on what you mean here?
    hwti wrote:

    The device shows the energy values with 0.01Wh resolution, but only 1Wh is reported.
    I suppose the only way to get the full resolution would be to modify the CH573F firmware (not sure if possible).

    Are you saying that the values from the screen display are not sent to OBK?

    I wrote about the energy values (in Wh), not the power.
    For example, the screen displays 0.07309kWh, and OpenBK reads 73 for channels 6/9.
    But since Tuya doesn't display these two additional digits either, the MCU firmware probably never reports them (unless it's behind an unknown setting).

    maximesharp wrote:
    the pairing screen disappears once the device is connected to the Wi-Fi network.

    Even with "MQTT State: not configured," like in your first post?
    It seems by default OpenBK waits for the MQTT connection to be established to report the Wi-Fi state 4 (i.e., "connected to the cloud").
    Maybe the MCU remembers if a Tuya pairing has been done and has a different behavior.
  • #37 20947382
    divadiow
    Level 38  
    Posts: 5032
    Help: 438
    Rate: 891
    >>20946773

    this is cool. Hopefully it can be made good for general release :)

    what do your GPIOs look like now as seen in the template export?

    Screenshot of the export template field with highlighted GPIO pin information.

    Added after 34 [minutes]:

    divadiow wrote:
    this is cool. Hopefully it can be made good for general release


    :D Screenshot of the OpenBK7231N interface displaying device status data.
  • ADVERTISEMENT
  • Helpful post
    #38 20948700
    divadiow
    Level 38  
    Posts: 5032
    Help: 438
    Rate: 891
    divadiow wrote:
    what do your GPIOs look like now as seen in the template export?


    Oh I understand now. TuyaMCU controls everything, so no GPIO assignments. This is my first real look at anything with TuyaMCU. And also my first CB3S desoldering, which I didnt particularly enjoy, despite the help of this good vid.

    attached is a factory fw dump.
    Attachments:
    • readResult_BK7231N_QIO_2024-06-2-07-17-11.bin (2 MB) You must be logged in to download this attachment.
  • #40 20950215
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14587
    Help: 654
    Rate: 12609
    Thank you, your PR is merged now.
    Helpful post? Buy me a coffee.
  • #41 20955846
    micbanand
    Level 6  
    Posts: 13

    I have just flashed one of these with /OpenBK7231T_UA_1.17.457.bin
    but nothing works over Wi-Fi.
    How do I flash the .bat file from this thread?
  • ADVERTISEMENT
  • #42 20955863
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14587
    Help: 654
    Rate: 12609
    What do you mean by "nothing works over WiFi"?

    Have you watched our tutorials?

    Autoexec tutorial is here:


    Helpful post? Buy me a coffee.
  • #43 20956255
    micbanand
    Level 6  
    Posts: 13

    I can see it on a given IP.
    But I get no readings, and the switch on/off is not working.

    Yes, I have watched that video.
    But I can't see anywhere how to upload autoexec.bat to my unit, only how to create it.
  • #44 20957424
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14587
    Help: 654
    Rate: 12609
    micbanand wrote:

    But I can't see anywhere how to upload autoexec.bat to my unit, only how to create it.

    Well, for example drag and drop file or just copy content?

    Are you able to open the Web App?
    Helpful post? Buy me a coffee.
  • #45 20957467
    divadiow
    Level 38  
    Posts: 5032
    Help: 438
    Rate: 891
    micbanand wrote:
    But I can't see anywhere how to upload autoexec.bat to my unit, only how to create it.


    I just copy the text into the box after opening the autoexec.bat I created in the web app.
    Screenshot of a web application for editing the autoexec.bat file.
  • #46 20957553
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14587
    Help: 654
    Rate: 12609
    You can also drag and drop a file on a field that says.... "drop file(s) or .tar here"
    Helpful post? Buy me a coffee.
  • #47 20957784
    micbanand
    Level 6  
    Posts: 13

    I think I have lost every WiFi connection.
    I think I have to solder the chip and flash the backup.
    Or can one of you share an obk working one with the default 192.168.1.4 or other known IP?
  • Helpful post
    #49 21005755
    divadiow
    Level 38  
    Posts: 5032
    Help: 438
    Rate: 891
    Finally flashed a replacement after blowing up my first. No desoldering of module, I have no heat gun.
    I had to sever the RX from the CB3S then all was OK flashing with all pins soldered to USB-TTL

    here is Tuya API response for this device

    Code: JSON
    Log in, to see the code


    in summary
    Code: Text
    Log in, to see the code


    This was trace cut and then soldered with a little blob.

    Close-up of a circuit board with visible pins and soldering marks.

    Close-up of a circuit board with a soldered module.
  • #50 21013048
    cdtdsilva
    Level 11  
    Posts: 171
    Help: 4
    Rate: 15
    How is the current measurement done? Is it a sensing resistor?

    Actually - has someone had any of these (current sensing resistors) failing during a mains short circuit?

    Thanks
  • #51 21295321
    divadiow
    Level 38  
    Posts: 5032
    Help: 438
    Rate: 891
    >>20945733 >>20945733

    App screen showing information about available MCU update to version 1.0.7

    this is the 1.0.7 MCU update binary file downloaded by the Tuya app to update from 1.0.6
    Attachments:
    • strings.txt (3.98 KB) You must be logged in to download this attachment.
    • Atorch_S1_MCU_1.0.7.bin (195.71 KB) You must be logged in to download this attachment.
  • #52 21744060
    jcur76
    Level 2  
    Posts: 2
    Could someone please measure the voltage on the 470 µF capacitor located next to the large black inductor? Thanks!
  • ADVERTISEMENT
  • #53 21744827
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14587
    Help: 654
    Rate: 12609
    Hey, why? Do you have a faulty device? This capacitor is in the power supply circuit, the KP3211BSG is used there.
    Application circuit diagram using KP3211BSG with HV DC input
    Do you suspect your KP3211BSG is faulty?
    Considering the fact that the 6118A 33 (3.3V) voltage regulator seems to be connected there, most likely the voltage there is around 5V, but I don't have this device to check. I would not expect 12V there, there is no need for such voltage and it's not used with LDO s directly, for 12V, we would rather see a step down. So, I think that KP3211BSG provides around 5V DC and then LDO provides 3.3V for WiFi module.
    Helpful post? Buy me a coffee.
  • #54 21745809
    jcur76
    Level 2  
    Posts: 2
    I’ve repaired this device, but now the supply voltage is around 4.7–4.8 V, and it fluctuates a bit (which might be normal for this kind of converter, considering its somewhat unusual topology). It looks like the device is working, but I’m still not sure whether this voltage is considered normal, or if it’s supposed to be exactly 5 V.
  • #55 21813650
    Alex2026
    Level 2  
    Posts: 2
    >>20948700 Do I understand correctly that you do not need to select GPIO in the settings? When creating a backup, it issued a CRC error and did not write the specified GPIO, but they were accurate. Now I can't find which ones should be indicated, maybe someone has survived? And please share autoexec.bat in which all functions will work.
  • #56 21813778
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14587
    Help: 654
    Rate: 12609
    This device is using TuyaMCU. There is no GPIO to set. TuyaMCU is almost always using UART1 port on Beken, and our driver is configured to use it by default. There is no GPIO to extract.

    Which tool did give you CRC error? Our Easy Flasher?
    https://github.com/openshwprojects/BK7231GUIFlashTool
    Latest autoexec.bat is in this topic, unless someone else extended it even futher - anyone?
    Helpful post? Buy me a coffee.
  • #57 21813872
    Alex2026
    Level 2  
    Posts: 2
    >>21813778 Used BK7231GUIFlashTool-v220 for reading and firmware; the chip is selected BK7231N (T2, T34). WiFi CB3S module. Immediately when reading it gives the following error:
    CRC mismatch!
    Sent by BK 0x81CD83C7, our CRC 0x62059BF7
    Maybe you have wrong chip type set?
    Did you set BK7231T but have in reality BK7231N or BK7231M?

    Because of this, I could not make my own backup of the installed factory firmware.

    If make EraseAll and upload the latest firmware 1.18.247 or the backup of the factory firmware posted in this topic "readResult _ BK7231N _ QIO _ 2024-06-2-07-17-11.bin" - CRC matches, but if you make a small change to OBK Settings and try to read, a CRC error.

    Now I will try to use the latest version of v228. Tell me the correct sequence for a clean firmware write.
    Do I need to set flags?
    Flag 46 - [TuyaMCU] Store raw data
    Flag 47 - [TuyaMCU] Store ALL data

    Added after 2 [hours] 36 [minutes]:

    And there's another question: after rebooting, the outlet needs to be left idle for at least about an hour, otherwise it doesn't connect via WiFi. Does this mean the WiFi board is failing and needs to be replaced?
| New topic
Report a violation of the law

Topic summary

✨ The discussion centers on the Tuya ATORCH S1-B/W/T/H Smart Socket Energy Monitor featuring the BK7231N (C3BS) WiFi module, CH573F main MCU, and BL0942 energy metering chip. The device's firmware can be replaced with OpenBeken (OpenBK7231T), enabling custom control and telemetry via MQTT and Home Assistant (HASS) integration. Users shared detailed autoexec.bat configurations for channel types and Tuya MCU data point (dpid) mappings, addressing issues such as incorrect voltage and power scaling factors (e.g., Voltage_div10 vs. Voltage_div100, Power_div10 vs. Power_div100), relay control toggling, and energy cost reporting. Firmware updates progressively added missing channel types like Voltage_div100 and Power_div100, improving measurement accuracy and HASS discovery payloads. Relay control was corrected by distinguishing between dpid 1 (relay state indicator) and dpid 131 (relay control enum). Suggestions included using alternative channel types (Toggle_Inv, OffDimBright, LowMidHigh) for enum control with 0/1/2 states (On/Off/Auto). Programming the C3BS module was discussed, with recommendations to power the module externally during flashing to avoid desoldering. Calibration challenges were noted due to lack of incandescent bulbs, with some success using halogen lamps. The device reports CPU temperature via dpid 135, which can be integrated into OpenBeken. Users also shared Tuya API schema dumps and MCU firmware update binaries. Troubleshooting tips included safe mode entry by power cycling and methods to upload autoexec.bat via the web interface. The device supports multiple dpids for advanced features like OVP, OCP, OPP, language setting, brightness, and standby time, though some require custom handling. Overall, the community collaboratively enhanced OpenBeken support for the ATORCH S1 series, improving smart socket energy monitoring and control capabilities.
Generated by the language model.
Today's popular

FAQ

TL;DR: With OpenBeken 1.17.406+, this ATORCH S1 works with 9 mapped channels and the real relay control on dpId 131. One expert fix was: “dpid 1 … only shows if the relay is on or off.” This FAQ is for CB3S/BK7231N owners who need correct flashing, scaling, relay control, and Home Assistant behavior. [#20919646]

Why it matters: This device looks simple, but wrong channel types or the wrong relay dpId break switching, scaling, and Home Assistant discovery.

Metoda / opcja Co działa Główne ograniczenie
Wylutowanie CB3S Pewne flashowanie BK7231N Pady łatwo się odrywają
Flashowanie w układzie Może działać bez wylutowania Wymaga mocnego 3.3 V i zgodnego USB-UART
CP2102 USB-UART Potwierdzone jako działające Nadal nie wolno zasilać z sieci jednocześnie
CH343P USB-UART U jednego użytkownika backup się przerywał Możliwe problemy z zasilaniem lub sterowaniem UART

Key insight: To urządzenie używa TuyaMCU, więc OpenBeken nie potrzebuje mapy GPIO. Najważniejsze ustawienia to poprawne typy kanałów dla skali oraz użycie dpId 131 do sterowania przekaźnikiem zamiast dpId 1.

Quick Facts

  • Moduł Wi-Fi to CB3S/C3BS z BK7231N, logikę główną realizuje CH573F, a układ pomiarowy to BL0942. [#20743339]
  • Końcowa działająca konfiguracja używa 9 kanałów: napięcie Voltage_div100, moc Power_div100, prąd Current_div1000, częstotliwość Frequency_div100, współczynnik mocy PowerFactor_div100 i energia EnergyTotal_kWh_div1000. [#20910128]
  • Rzeczywiste sterowanie przekaźnikiem jest na dpId 131 enum z wartościami 0 = ON, 1 = OFF, 2 = auto; dpId 1 bool tylko pokazuje stan przekaźnika. [#20919646]
  • Sekcja zasilania obok kondensatora 470 µF i układu KP3211BSG ma oczekiwane napięcie około 5 V, a zgłoszone 4.7–4.8 V po naprawie wyglądało na działające. [#21744827]

How do I flash OpenBeken on the Tuya ATORCH S1 smart socket with a CB3S/BK7231N module, and what autoexec.bat settings make the measurements work correctly?

Flash OpenBeken to the CB3S/BK7231N, then load an autoexec.bat that starts TuyaMCU and maps 9 channels. 1. Flash the BK7231N module. 2. Open the web panel and paste or drop autoexec.bat. 3. Use the working mapping with Voltage_div100, Power_div100, Current_div1000, Frequency_div100, PowerFactor_div100, and EnergyTotal_kWh_div1000. For relay control, map dpId 131 to channel 0 and keep dpId 1 as read-only status. A confirmed working setup was posted on January 20, 2024. [#20919646]

Why does the ATORCH S1 show voltage or power values 10 times too high in OpenBeken, and which channel types should be used for dpid 19 and dpId 20?

It shows 10× too high because the original scaling was too small for this device. dpId 20 voltage should use Voltage_div100, not Voltage_div10, and dpId 19 power should use Power_div100, not Power_div10. The issue first appeared as about 2378.80 V instead of 237.83 V. Support for Voltage_div100 arrived first, and later Power_div100 was added in OpenBK 1.17.406, after which the device worked correctly. [#20910128]

What is TuyaMCU, and why does this ATORCH S1 device not need any GPIO assignments in OpenBeken?

"TuyaMCU" is a serial control layer that lets a separate MCU handle sensors, UI, and relay logic, while the BK7231N Wi-Fi chip exchanges data over UART. This ATORCH S1 does not need GPIO assignments because OpenBeken talks to the TuyaMCU directly, and the device uses UART1 by default. That is why template export can show no useful GPIO roles here. This was stated explicitly again in January 2026. [#21813778]

What is the CB3S/C3BS module in the ATORCH S1, and how is it related to the BK7231N chip?

The CB3S, also labeled C3BS in the thread, is the plug-in Wi-Fi module, and it contains the BK7231N chip. In this device, the BK7231N runs OpenBeken, while the CH573F handles the main device logic and the BL0942 handles metering. That split explains why flashing the Wi-Fi module alone does not replace the whole device firmware. The hardware IDs were identified when the socket was opened and photographed. [#20743339]

How can I control the relay properly on the ATORCH S1 when dpId 1 only reports relay status and dpId 131 is the real relay control enum?

Control the relay through dpId 131, not dpId 1. dpId 1 is only a status indicator, while dpId 131 is the real enum control with values 0, 1, and 2. A working OpenBeken setup uses channel 0 as Toggle_Inv linked to 131 enum 0, and channel 1 as ReadOnly linked to 1 bool 1. That change fixes the common symptom where the on-screen toggle changes state but does not switch the physical relay. [#20919646]

Which OpenBeken channel type works best for the ATORCH S1 relay enum values 0, 1, and 2, and how do LowMidHigh, OffDimBright, and a possible OnOffAuto mode compare?

For simple on/off control, Toggle_Inv works best today because dpId 131 uses 0 = ON and 1 = OFF. If you need all three enum values, LowMidHigh or OffDimBright can send 0, 1, and 2, but their labels do not match the socket’s meanings. The thread noted that value 2 = auto did not visibly act in one tested mode. An OnOffAuto channel type was discussed as the cleaner long-term option. [#20919694]

How do I upload or apply an autoexec.bat file in OpenBeken after flashing the device?

Upload it through the OpenBeken web app. You can paste the file contents into the autoexec editor, or drag and drop the file onto the field labeled drop file(s) or .tar here. Users who saw Wi-Fi but no readings or no relay action were told that the missing step was applying the autoexec.bat after flashing. If the web panel opens on the device IP, you already have the right place to do it. [#20957553]

What should I do if the ATORCH S1 loses Wi-Fi after flashing OpenBeken, and how can safe mode help recover it?

Use OpenBeken safe mode first, because it can restore access without reflashing. 1. Power the socket off and on 5 times quickly. 2. Let it boot into safe mode. 3. Remove or fix the bad autoexec settings, then reboot normally. This advice was given after a user lost Wi-Fi access while editing settings. Safe mode is the fastest recovery path before you resolder the module or restore a backup. [#20959060]

Why would flashing the CB3S in-circuit work with a CP2102 USB-to-serial adapter but fail with a CH343P, even when using an external 3.3 V supply?

Because in-circuit flashing needs both enough 3.3 V current and strong UART signaling against the active main MCU. One user reported repeated backup interruptions with a CH343P, even with a dedicated 3.3 V supply, but successful flashing with a CP2102. The suggested reason was that the adapter may also need enough drive on the UART line when the CH573F is still talking to the CB3S. That makes adapter choice matter here more than on simpler boards. [#20945220]

How can I flash the CB3S on this ATORCH S1 without desoldering the Wi-Fi module, and what safety precautions matter when powering it from USB-TTL?

You can flash it in-circuit if your USB-TTL adapter can power the 3.3 V rail strongly enough. One method was to power the full low-voltage side from USB-TTL and program the CB3S without removing it; another successful method cut the RX trace temporarily, then resoldered it after flashing. The critical safety rule is simple: never connect the socket to mains while the USB-TTL adapter powers it. That prevents dangerous back-powering and damage. [#21005755]

Why does Home Assistant discovery show the wrong decimal scaling for Voltage_div100, Power_div100, or PowerFactor_div100 in OpenBeken, and how can the HASS payload be fixed?

Home Assistant discovery was wrong because the HASS payload used the wrong decimal offset versus decimal places. After Voltage_div100 fixed the device display in firmware 1.17.252, the Home Assistant template still reported bad scaling until discovery code was corrected. A posted patch changed sensor init values, such as POWER_SENSOR to (2, 2) and POWERFACTOR_SENSOR to (4, 2), then discovery worked correctly. Re-running Home Assistant discovery was also required after the fix. [#20745201]

What do the extra Tuya dpIds on the ATORCH S1 mean, such as 102 cost, 118 menu, 132 warning, 136 price mode, and 139 reporting interval?

They expose many built-in functions beyond power monitoring. The Tuya API dump identified dpId 102 as total cost, 118 as device function page selection, 132 as warning flag, 136 as price mode, and 139 as measurement reporting interval. The same dump also showed ranges, such as dpId 139 from 1 to 90 seconds and dpId 136 with single_rate, stair, and peak_valley_stair. That makes this socket closer to a programmable energy meter than a basic smart plug. [#21005755]

How is current measured inside the ATORCH S1 energy monitor, and what happens to the current-sensing resistor during a mains short circuit?

The thread does not confirm the exact current-sense topology or a tested failure mode during a mains short. The only hard hardware identification was BK7231N, CH573F, and BL0942, plus board photos. A later user asked whether current used a sensing resistor and whether such resistors fail in a short circuit, but no answer in the thread resolved it. So the safe conclusion is that the measurement method and short-circuit behavior remain undocumented in this discussion. [#21013048]

What voltage should appear on the 470 µF capacitor near the large black inductor and KP3211BSG power supply section, and is 4.7 to 4.8 V considered normal?

The expected voltage is about 5 V, and 4.7–4.8 V was reported on a repaired unit that otherwise worked. The reasoning in the thread was that the KP3211BSG likely feeds that rail and a 6118A 3.3 V regulator then powers the Wi-Fi module. The expert comment was clear: “most likely the voltage there is around 5V.” No one measured an exact factory value on an untouched unit in that exchange. [#21744827]

Why does BK7231GUIFlashTool report a CRC mismatch when reading back firmware from a BK7231N-based CB3S module, and what is the correct clean-flash sequence for this device?

The thread reports the CRC mismatch, but it does not confirm a final root cause or a verified clean-flash sequence. One user saw CRC mismatch immediately on readback with BK7231GUIFlashTool v220 using BK7231N, while EraseAll plus writing OpenBeken 1.18.247 or a shared factory dump succeeded. The same user also reported that reading back after changing OBK settings triggered CRC errors again. The only concrete next step suggested in-thread was to verify the exact chip type and try a newer tool version, such as v228. [#21813872]
Generated by the language model.
ADVERTISEMENT