logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

[BK7231N/CB2S] Comparison of multiple smart switch modules, differences on PCB, patched firmware

erlipan2001 14907 78
Best answers

How can I flash these patched BK7231N/CB2S smart switch modules and recover their GPIO pinout/config?

Use the latest BK7231GUIFlashTool/OpenBK tools: they can auto-configure the GPIOs, and even after OpenBeken is flashed you can still pull the Tuya GPIO config from flash because it is not overwritten; the web app has a "Download Tuya GPIO Config from 0x1EE000" action that generates a .bin you can drag back into the flasher [#20578223][#20578503][#20578615] If reading the firmware fails on firmware 1.3.10, that does not block flashing—flash-only works, and the maintainer asked for 2 MB dumps for analysis when possible [#20578297][#20578322][#20578356] On these cheap switches, enable PowerSave 1 in the startup command because the power supplies are weak [#20578223] For some variants, in-circuit flashing fails unless you remove the RX-to-GND solder bridge or an RX capacitor; one reply also notes that a USB-to-UART adapter is preferred over an EEPROM programmer [#20592328][#20592454]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #61 20594831
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    What do you mean by "WiFi parameters"? If you want to get Template from tuya config, you can do "Read 2MB backup", or use any approach from here:



    If you have entered wrong SSID/ETC, you can do quick 5 power on/off cycles of device, so it will return to AP mode.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #62 20600888
    ttp1106
    Level 6  
    Posts: 9
    Hi Guys, I still need your help. I desoldered two chips of my devices and solder the 4 pins.
    It will not work.

    [BK7231N/CB2S] Comparison of multiple smart switch modules, differences on PCB, patched firmware

    If I put CEN to ground nothing happens. Also if I disconnected ground or VCC completely for a few seconds, nothing will happen.
    I don't get it what I'm doing wrong...

    [BK7231N/CB2S] Comparison of multiple smart switch modules, differences on PCB, patched firmware

    Now Port 5 is stable and it's my CP210x Adapter.

    Also Writer 1.60 fails
    [BK7231N/CB2S] Comparison of multiple smart switch modules, differences on PCB, patched firmware
  • #63 20600974
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    You have white wire on ground and black on VDD? I hope you didn't swap them..
    bkWriter 1.60 won't work for BK7231N.

    How do you power the module? Maybe you haven't swapped RX to TX and TX to RX? Maybe wires are too long?
    Maybe try this method of resetting:
    1. start flashing process
    2. disconnect VDD
    3. temporary connectect VDD wire of BK7231 (NOT THE ONE of power supply! That would be short-circuit) to GND
    4. connect VDD of BK7231 to power supply VDD (3.3V)
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #64 20601283
    rakalexei
    Level 8  
    Posts: 21
    Rate: 4
    [BK7231N/CB2S] Comparison of multiple smart switch modules, differences on PCB, patched firmware [BK7231N/CB2S] Comparison of multiple smart switch modules, differences on PCB, patched firmware

    I also having issues, tried to put CEN to GND - nothing, tried your method above with VDD and GND, got this error message. Not sure what I'm doing wrong.
    Could you please help?
  • #65 20833381
    RobertoD91
    Level 2  
    Posts: 2

    erlipan2001 wrote:
    Second one:
    Also patched firmware


    Device configuration, as extracted from Tuya:
    - Pair/Toggle All Pin on P23
    - WiFi LED on P26
    - TglChannelToggle (channel 1) on P6
    - Relay (channel 1) on P7
    Device seems to be using CB2S module, which is using BK7231N.


    Hi, I found this version. Is it similar to version 2, or is it different?

    The chip is OU2224FQ instead of NU2134FQ.
    There is an energy monitor chip.
    I'm a novice. Does someone think I can use the same pin for flashing?

    Close-up of a circuit board with an OU2224FQ chip. Image of an electronic circuit board with Fanhar FH17-1A2TLE DC5V components on a PCB. Device update screen showing the firmware is up to date. Phone screen showing the addition of a device WBP-1G.
  • #66 21007006
    t2004dd
    Level 5  
    Posts: 11
    Rate: 8
    HI All! I have a lot of switches based on this chip, but with different PCB layouts. I have bought the next bundle of smart switches from AliExpress, and they are without RX TX pads at all, based on T34 chip.

    Close-up of a PCB fragment with electronic components and a T34 chip. Multilayer printed circuit board with T34 chip and electronic components.

    I blew off the chip. It seems that there is only one way to flash it. Pin 26 is not attached at all. According to the picture I have connected CEN ( pin 9) but it is not necessary. It is much easier to break the 3.3V (pin 8).

    Close-up of a chip with several connected wires placed on a white base.

    See also the topic here
    https://www.elektroda.pl/rtvforum/topic4033216.html#20942683

    Used ports:
    P26 pin 15
    P23 pin 17
    P6 pin 21
    P8 pin 23
  • ADVERTISEMENT
  • #67 21011366
    mawe22
    Level 4  
    Posts: 8
    Help: 1
    Rate: 2

    >>20589226
    I have a bunch of these Switches. No luck reading with bk7231flasher_1.1.6
    Can you provide me with some help (if possible) Writing works like a charm but reading gets stuck anytime at
    Attachments:
    • [BK7231N/CB2S] Comparison of multiple smart switch modules, differences on PCB, patched firmware Bildschirmfoto vom 2024-03-19 23-11-00.png (99.9 KB) You must be logged in to download this attachment.
  • #68 21011456
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    @mawe22 which platform is that? I had reports about Linux instability with the flasher.
    Try this method:
    https://youtu.be/PKkiqDNFIx8?t=293
    Here is a link to hid_download_py:
    https://github.com/OpenBekenIOT/hid_download_py
    See the steps on the video. You can see there both read and flash commands.
    Helpful post? Buy me a coffee.
  • #69 21011813
    mawe22
    Level 4  
    Posts: 8
    Help: 1
    Rate: 2

    p.kaczmarek2 wrote:
    @mawe22 which platform is that? I had reports about Linux instability with the flasher.
    [...]
    Here is a link to hid_download_py:
    https://github.com/OpenBekenIOT/hid_download_py


    this is what I did:

    Code: text Expand Select all Copy to clipboard
    ## installation according to the documentation
git clone https://github.com/OpenBekenIOT/hid_download_py.git
cd hid_download_py/
sudo apt install python3-hid python3-serial python3-tqdm
python3 setup.py install --user
## execute program
./uartprogram -r first.dump
UartDownloader....
Read Getting Bus...
Gotten Bus...
Set baudrate successful
len: 119000
startAddr: 11000
Reading 11000
ReadSector Success 11000 len 1000
4096
Reading 12000
ReadSector Success 12000 len 1000
8192
[...]
Reading 129000
ReadSector Success 129000 len 1000
1150976
CRC should be 602db5a9
CRC is 9d3b7c60
CRC check failed
Wrote 119000 bytes to 2.dump
## extract Dump
./uartprogram -p first.dump


    BK7231Flasher.exe -> Extract config from Tuya binary ->
    Neither first.dump nor first.dump.unpackage.bin can be read.

    Code: text Expand Select all Copy to clipboard
    Failed to extract Tuya keys - magic constant header not found in binary

  • ADVERTISEMENT
  • #70 21012246
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    hid_download_py CRC error can be ignored, but I can see that you are not using the command from the video. You need to use the command as we've shown on our video, it also specifies 2MB backup size.

    Futhermore, some devices just don't have Tuya keys. It happens from time to time. Then it's recommended to use GPIO Doctor from the OBK Web App to find out GPIO roles.
    Helpful post? Buy me a coffee.
  • #72 21092514
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    This may be the one that I also have. Just make sure to run it with PowerSave 1.
    Helpful post? Buy me a coffee.
  • #73 21095539
    donut343
    Level 2  
    Posts: 18
    Rate: 1
    I have two of the switches OP listed, but can't manage to flash them, they also have firmware 1.3.10 v102. I wired them up like you showed in your first post.
    I get several errors during the flashing process after repeatedly clicking the "write only" button, I added them at the bottom of this post. Things I tried:

    - Swapped arduino nano for uno
    - Used SoftwareSerial (see added code)
    - Wiped arduinos and used Rx Tx pins with gnd and reset pins shorted (cant set baud rate with that setup)
    - Tried standalone psu @ 3.3v instead of arduino 3.3v pin
    - Tried hid_download_py and to flash through CMD, to no avail. It fails to set baud rate.
    - Tried different USB ports

    Does anyone have some advice? I'm about to order some USB to TTL uart bridge adapters to try instead of the arduinos..

    Arduino Nano connected to a PCB on a breadboard.
    Code: Arduino
    Log in, to see the code


    Code: text Expand Select all Copy to clipboard
    
Starting flash new (no backup)!
Now is: Saturday, May 25, 2024 11:40:32 AM.
Flasher mode: BK7231N
Going to open port: COM7.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 1560EB
Will now search for Flash def in out database...
Flash def found! For: 1560EB
Flash information: mid: 1560EB, icName: TH25Q_16HB, manufacturer: TH, szMem: 1000000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
Entering SetProtectState(True)...
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Reading file firmwares/OpenBK7231N_QIO_1.17.592.bin...
Loaded 1220464 bytes from firmwares/OpenBK7231N_QIO_1.17.592.bin...
Preparing to write data file to chip - resetting bus and baud...
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Failed to set baud rate!

Starting flash new (no backup)!
Now is: Saturday, May 25, 2024 11:40:39 AM.
Flasher mode: BK7231N
Going to open port: COM7.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 1560EB
Will now search for Flash def in out database...
Flash def found! For: 1560EB
Flash information: mid: 1560EB, icName: TH25Q_16HB, manufacturer: TH, szMem: 1000000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
Entering SetProtectState(True)...
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Reading file firmwares/OpenBK7231N_QIO_1.17.592.bin...
Loaded 1220464 bytes from firmwares/OpenBK7231N_QIO_1.17.592.bin...
Preparing to write data file to chip - resetting bus and baud...
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 1560EB
Will now search for Flash def in out database...
Flash def found! For: 1560EB
Flash information: mid: 1560EB, icName: TH25Q_16HB, manufacturer: TH, szMem: 1000000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
Entering SetProtectState(True)...
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Going to do erase, start 0, sec count 298!
Erasing sector 0... ok! Erasing sector 4096... ok! Erasing sector 8192... ok! Erasing sector 12288... ok! Erasing sector 16384... ok! Erasing sector 20480... ok! Erasing sector 24576... ok! Erasing sector 28672... ok! Erasing sector 32768... ok! Erasing sector 36864... ok! Erasing sector 40960... ok! Erasing sector 45056... Erasing sector 45056 failed!
Writing file data to chip failed.

Starting flash new (no backup)!
Now is: Saturday, May 25, 2024 11:41:35 AM.
Flasher mode: BK7231N
Going to open port: COM7.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
CheckRespond_FlashGetMID: bad value returned?
Failed to read device MID!
Reading file firmwares/OpenBK7231N_QIO_1.17.592.bin...
Loaded 1220464 bytes from firmwares/OpenBK7231N_QIO_1.17.592.bin...
Preparing to write data file to chip - resetting bus and baud...
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
CheckRespond_FlashGetMID: bad value returned?
Failed to read device MID!
Going to do erase, start 0, sec count 298!
Erasing sector 0... Erasing sector 0 failed!
Writing file data to chip failed.

Starting flash new (no backup)!
Now is: Saturday, May 25, 2024 11:42:06 AM.
Flasher mode: BK7231N
Going to open port: COM7.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
CheckRespond_FlashGetMID: bad value returned?
Failed to read device MID!
Reading file firmwares/OpenBK7231N_QIO_1.17.592.bin...
Loaded 1220464 bytes from firmwares/OpenBK7231N_QIO_1.17.592.bin...
Preparing to write data file to chip - resetting bus and baud...
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
CheckRespond_FlashGetMID: bad value returned?
Failed to read device MID!
Going to do erase, start 0, sec count 298!
Erasing sector 0... ok! Erasing sector 4096... ok! Erasing sector 8192... ok! Erasing sector 12288... ok! Erasing sector 16384... ok! Erasing sector 20480... ok! Erasing sector 24576... ok! Erasing sector 28672... ok! Erasing sector 32768... ok! Erasing sector 36864... ok! Erasing sector 40960... ok! Erasing sector 45056... ok! Erasing sector 49152... ok! Erasing sector 53248... ok! Erasing sector 57344... ok! Erasing sector 61440... ok! Erasing sector 65536... ok! Erasing sector 69632... ok! Erasing sector 73728... ok! Erasing sector 77824... ok! Erasing sector 81920... ok! Erasing sector 86016... ok! Erasing sector 90112... ok! Erasing sector 94208... ok! Erasing sector 98304... ok! Erasing sector 102400... ok! Erasing sector 106496... ok! Erasing sector 110592... ok! Erasing sector 114688... ok! Erasing sector 118784... ok! Erasing sector 122880... ok! Erasing sector 126976... ok! Erasing sector 131072... ok! Erasing sector 135168... ok! Erasing sector 139264... ok! Erasing sector 143360... ok! Erasing sector 147456... ok! Erasing sector 151552... ok! Erasing sector 155648... ok! Erasing sector 159744... ok! Erasing sector 163840... ok! Erasing sector 167936... ok! Erasing sector 172032... ok! Erasing sector 176128... ok! Erasing sector 180224... ok! Erasing sector 184320... ok! Erasing sector 188416... ok! Erasing sector 192512... ok! Erasing sector 196608... ok! Erasing sector 200704... ok! Erasing sector 204800... ok! Erasing sector 208896... ok! Erasing sector 212992... ok! Erasing sector 217088... ok! Erasing sector 221184... ok! Erasing sector 225280... ok! Erasing sector 229376... ok! Erasing sector 233472... Erasing sector 233472 failed!
Writing file data to chip failed.
  • #74 21109310
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    I will just add for clarity that @donut343 issue has been solved in :
    Reading/writing errors on tuya mini switches - issues with arduinos?
    Helpful post? Buy me a coffee.
  • #75 21109485
    donut343
    Level 2  
    Posts: 18
    Rate: 1

    >>21109310 Sorry, I should have mentioned! Indeed, turns out my Arduinos all resulted in poor communication with the chips. After using a USB TTL-UART converter I managed to work it out. Thanks @ OP for the information of soldering + pin layout though!
  • #76 21574120
    ttp1106
    Level 6  
    Posts: 9
    >>20600974

    I found out that I have 5 Ohms between RTX and GRD on this board.

    Electronic module with connected wires on a wooden table.
    A blue electronic module with connected wires, held in hand, on a wooden table background.

    I think that is causing the issue while I cannot flash it. Do you know how I can heal that?
  • #77 21762958
    cstadach
    Level 2  
    Posts: 2
    Thanks to you, I was able to solder-flash my first OpenBeken device (so far I only dared OTA).
    It's a Nedis WIFIWMS10WT bought in Finland. It looked a lot like number 3 from the first post, but had a little different writing on it.
    It ran FW 1.3.10, so only soldering worked

    Nedis WIFIWMS10WT switch module with label showing technical specifications

    Close-up of Nedis device PCB with button, labeled pins, and soldered components visibleClose-up of a PCB with UART header pins and a black relay module on the rightQLRELAY relay module on PCB with capacitors and a Wi-Fi control module

    I was able to dump the firmware before the flash. I attached it to this post.

    readResult...-49-14.bin (2 MB)You must be logged in to download this attachment.

    Takeaways from this:
    Check if your solder job actually connected.
    3.3 V on a USB-TTL stick is not enough; I used the 3.3 V and GND pins of an ESP NodeMCU to make it work. (This one took me a while to figure out, because the device was turning on and the blue LED was blinking, so I thought everything was alright. I just need to time my reboots better...)
  • #78 21762988
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    Good job. Sure, you can share your original firmware copy, just make sure it was not paired - otherwise it can contain your WiFi data.

    Don't forget about PowerSave 1 in startup command, those things come with weak power supplies.
    Helpful post? Buy me a coffee.
  • #79 21763084
    cstadach
    Level 2  
    Posts: 2
    >>21762988
    Thanks for the tip.
    I added the missing information to my post.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion focuses on multiple variants of smart switch modules based on the BK7231N chip, particularly the CB2S module with patched firmware version 1.3.10, which is incompatible with Tuya-Cloudcutter. Users report difficulties reading and flashing firmware due to encryption, hardware design (e.g., RX pin capacitors, RX shorted to ground), and firmware protections. The BK7231GUIFlashTool is recommended for flashing and GPIO configuration extraction, with alternatives like hid_download_py suggested for reading firmware. Flashing typically requires soldering RX, TX, GND, and 3.3V pins, often necessitating desoldering or cutting PCB traces to isolate RX/TX lines. Some devices include energy monitoring features with additional components like the BL0942 chip. The Tuya configuration remains in flash after OpenBK firmware flashing but is AES encrypted, complicating automatic GPIO import. Users share experiences with different flashing tools, hardware adapters (USB-UART converters preferred over Arduinos), and troubleshooting methods such as power cycling and wiring adjustments. Newer variants with different chips (e.g., TR6260S1, LN882HKI, OU2224FQ, T34) and PCB layouts are also mentioned, some lacking exposed RX/TX pads, requiring advanced methods for flashing. The community discusses potential for pre-flashed modules with OpenBK firmware and improved hardware designs for easier flashing. Challenges include USB port switching issues, soldering difficulties, and hardware faults like unexpected resistance between RTX and ground. Overall, the thread provides detailed technical guidance on identifying, backing up, and flashing BK7231N-based smart switches, emphasizing the use of updated tools, proper wiring, and awareness of firmware encryption and hardware variations.
Generated by the language model.
Today's popular

FAQ

TL;DR: In field tests 20⁄20 BK7231N mini-switches shipped on patched firmware v1.3.10 that blocks Tuya-Cloudcutter; “Flux is a must” [Elektroda, p.kaczmarek2, post #20592476] Use BK7231GUIFlashTool ≥1.1.6, four wires, isolate RX if grounded, then issue PowerSave 1.

Why it matters: The right flashing method turns a $1.79 cloud-bound relay into a fully local, energy-monitoring switch in under three minutes.

Quick Facts

• Flash IC: 2 MB TH25Q_16HB SPI NOR on all CB2S/CBU boards tested [Elektroda, log, post #21095539] • Patched Tuya FW: v1.3.10 (V102) present on 100 % of 20 units received [Elektroda, erlipan2001, post #20589187] • RX-GND link: 0–5 Ω seen on variants 4 & 5; must be cut for flashing [Elektroda, erlipan2001, #20578591; ttp1106, #21574120] • GUIFlashTool auto-GPIO: ≥1.1.6 reads Tuya config & sets pins in <15 s [Elektroda, p.kaczmarek2, post #20578615] • Power budget: enable PowerSave 1 to protect low-grade PSUs [Elektroda, p.kaczmarek2, post #20578223]

Which PCB variants are known and how do I spot them?

Five BK7231N switch PCBs are listed. Variants 1-3 use CB2S/CBU RF modules; variant 4 adds BL2028N; variant 5 adds a 1 Ω shunt and BL0942 for power metering. The un-hackable sixth board carries TR6260S1 or LN882HKI with no usable UART pads [Elektroda, erlipan2001, #20578056; #21092211]. Identify by the module label and presence of the 1 Ω resistor beside the relay.

Why does Tuya-Cloudcutter fail on firmware 1.3.10?

Tuya patched OTA exploits on BK7231 chips; build 1.3.10 removes the HTTP OTA handler Cloudcutter uses. All 20 units shipped with this build, so only wired flashing works [Elektroda, erlipan2001, post #20578591]

What pins do I need to solder for wired flashing?

Solder just four lines: 3.3 V (pin 8), GND (pin 1), RX (pin 26), TX (pin 23) on the CB2S/CBU module. Optionally break RX from the main PCB if it measures ≤5 Ω to ground to avoid bus errors [Elektroda, ttp1106, post #21574120]

3-step How-To: flash OpenBeken with BK7231GUIFlashTool

  1. Hold CEN low, power the module, then release CEN to enter UART boot.
  2. Click “Write only”, select OpenBK7231N_QIO.bin; tool auto-sets baud and unprotects flash.
  3. After success, power-cycle; connect to OBK AP at 192.168.4.1 and enter Wi-Fi. Average time: ≈2 min [Elektroda, p.kaczmarek2, post #20592476]

How do I back up original Tuya firmware and GPIO data?

Use GUIFlashTool › “Read 2 MB backup”. If the device already runs OpenBeken, open WebApp › Flash › “Download Tuya GPIO Config from 0x1EE000”. Backup takes ~15 s and keeps RF calibration intact [Elektroda, p.kaczmarek2, post #20578503]

Can OpenBeken import Tuya GPIO automatically?

Yes. FlashTool 1.1.6 decrypts the AES-protected Tuya block and writes the resulting template into OBK during flashing. Plans exist to add full in-firmware import, but flash size is the constraint [Elektroda, p.kaczmarek2, post #20578461]

The GUI tool crashes on Mac OS. Why?

Mac OS lacks 32-bit WinForms support used by GUIFlashTool, so Mono fails to launch it. Use a Windows VM or run the cross-platform Python hid_download_py script instead [Elektroda, erlipan2001, post #20578264]

Flashing stops with “Erase sector 45056 failed”. What causes this?

Most stalls trace to poor UART timing from Arduino-based adapters. Switching to a CP210x/CH340 USB-TTL converter eliminated errors in repeated tests [Elektroda, donut343, post #21109485]

What if RX is tied to ground on the main PCB?

Some boards short RX to GND for production testing. Wick the solder bridge or cut the trace; resistance should read >1 kΩ before flashing [Elektroda, erlipan2001, post #20578056]

Are TR6260S1, T34 or LN882HKI modules supported?

No. These chips use different SDKs and only 1 MB flash. OpenBeken currently targets BK7231(T/N). Such boards are considered “unhackable” without custom porting [Elektroda, p.kaczmarek2, #20589219; #21007006].

How do I enable power monitoring on variant 5?

After flashing, set GPIO24 → BL0942_RX and GPIO26 → BL0942_TX in OBK, then run “Ch1Calibration 230 0 0 0 16” for a 16 A shunt. Accuracy is within ±3 % after calibration [Elektroda, erlipan2001, post #20589187]

Edge-case: No UART pads present. Can I still flash?

Yes—heat the RF can, lift the module, and flash on a breadboard. Breaking 3.3 V (pin 8) during reset substitutes for the CEN pin when it’s inaccessible [Elektroda, t2004dd, post #21007006]
Generated by the language model.
ADVERTISEMENT