BK7231T vs BK7238: Beken SoC Comparison, Wi-Fi, BLE 5.2, Power, RAM, Tuya Modules

User question

What is the difference between bk7231t and bk7238

Artificial Intelligence Response

Direct answer to the question

• Brief, precise answer
  • BK7238 is the newer, lower‑power Wi‑Fi + BLE 5.2 combo SoC from Beken with a faster 32‑bit MCU (up to 160 MHz), a bit more SRAM (~288 KB), on‑SiP 2 MB flash, better RF (up to +19 dBm TX, −99 dBm RX), and direction‑finding BLE (AoA/AoD). BK7231T is an earlier Wi‑Fi/BLE part widely used in Tuya modules, built around an ARM968E‑S @120 MHz with 256 KB SRAM and 2 MB in‑package flash; BLE on BK7231T modules is typically 4.x and power/RF figures are less favorable. (bekencorp.com)
• Key points
  • MCU: 160 MHz (BK7238) vs 120 MHz (BK7231T). (bekencorp.com)
  • RAM: ~288 KB (BK7238) vs 256 KB (BK7231T). (bekencorp.com)
  • BLE: 5.2 with AoA/AoD (BK7238) vs BLE 4.x common on BK7231T modules. (bekencorp.com)
  • Power: RX ~40 mA, deep‑sleep ~10 µA (BK7238) vs WB3S/BK7231T RX ≈98–110 mA, higher TX currents. (bekencorp.com)
  • Flash/footprint: both integrate 2 MB SiP flash; BK7238 adds TRNG and eFuse, and comes in QFN20/QFN32. (bekencorp.com)

Detailed problem analysis

• Development of main aspects
  • CPU/architecture
  • BK7231T uses an ARM968E‑S (ARMv5TE) up to 120 MHz—proven for classic Wi‑Fi IoT, but without modern v8‑M features. (docs.libretiny.eu)
  • BK7238 integrates Beken’s current 32‑bit MCU platform up to 160 MHz. The vendor brief does not name the specific core, but positions it as a modern, higher‑efficiency platform than the BK7231 generation. (bekencorp.com)
  • Memory and storage
  • BK7231T: 256 KB SRAM; 2 MB in‑package flash commonly used on Tuya WB‑series modules (e.g., WB3S). (bekencorp.com)
  • BK7238: 288 KB RAM; 2 MB SiP flash; adds a small eFuse (4 bytes) and a true RNG for security/keys. (bekencorp.com)
  • Wireless subsystems
  • Both: 2.4 GHz 802.11 b/g/n, STA, SoftAP, and concurrent AP+STA. (bekencorp.com)
  • BK7238 BLE: LE 5.2 with 1M/2M/Coded PHYs, advertising extensions, and direction finding (AoA/AoD) supporting up to 16‑antenna arrays—useful for indoor positioning/presence. (bekencorp.com)
  • BK7231T BLE: many modules expose BLE 4.x (typically for provisioning/auxiliary features) rather than BLE 5.x; exact capability depends on module/SDK. (docs.libretiny.eu)
  • RF and power
  • BK7238 headline RF: up to +19 dBm TX and −99 dBm sensitivity; typical RX current ≈40 mA, deep‑sleep ≈10 µA—well suited to battery‑biased or thermally‑tight designs. (bekencorp.com)
  • BK7231T (WB3S module): datasheet shows RX near 98–110 mA and TX currents 185–222 mA depending on PHY/rate; acceptable for mains‑powered devices, but less efficient for battery. (manualshelf.com)
  • Peripherals and packaging
  • BK7238: QFN32 4×4 mm (≈19 GPIO) and QFN20 3×3 mm (≈9 GPIO); 2×UART (one for download), SPI, I2C, 6×PWM, 10‑bit SAR ADC (up to 6 ch), RTC, GDMA, TRNG, JTAG. (bekencorp.com)
  • BK7231T (family): 2 MB in‑package flash, 256 KB RAM; common Tuya modules (WB3S, etc.) expose subsets—UART, ADC, a handful of GPIO/PWM. (bekencorp.com)
• Theoretical foundations
  • Moving from an ARM9‑class MCU (BK7231T) to Beken’s newer MCU in BK7238 yields higher code density, better interrupt latency, more refined power domains and coexistence, and hardware blocks (TRNG, eFuse) that improve security baselines.
• Practical applications
  • BK7231T: Smart plugs/switches, basic RGB/CW lights, Wi‑Fi‑only sensors—especially where cost and mature community firmware matter most. (github.com)
  • BK7238: Battery‑assisted sensors, BLE‑assisted onboarding, BLE gateways/scanners, indoor positioning, compact modules where lower current and better RF margin are valuable. (bekencorp.com)

Current information and trends

• Beken’s current brief positions BK7238 for low‑power, compact designs with BLE 5.2 direction‑finding—matching the industry trend toward presence/RTLS features in IoT nodes. (bekencorp.com)
• Community firmware:
  • OpenBeken provides separate, non‑interchangeable builds for BK7231T and BK7238; treat them as different targets. (github.com)
  • ESPHome/LibreTiny support for BK7231T/7231N is established; BK7238 support remains limited/experimental in community reports as of late‑2025. (docs.libretiny.eu)

Supporting explanations and details

• Identifying what you actually have
  • Tuya‑style modules with similar markings (e.g., WB3S vs newer “T1/CB3S‑like” boards) can silently swap silicon; always check the UART boot log or use a flasher that reads the chip ID before writing. Mismatched binaries won’t boot. (github.com)
• Flash layout implications
  • Both families commonly reserve portions of the 2 MB flash for boot/OTA/kv storage, so application space is appreciably smaller than raw capacity—plan your image size accordingly. (docs.libretiny.eu)

Ethical and legal aspects

• RF compliance and region codes: ensure end products meet FCC/IC/CE limits for 2.4 GHz and follow module integration rules (antenna type, host labeling). BLE direction‑finding (AoA/AoD) can enable precise location; consider privacy implications and applicable state/federal privacy laws when deploying presence tracking. (General regulatory best practice; confirm with your NRTL and legal counsel.)

Practical guidelines

• Choosing between them
  • Pick BK7238 for new designs needing lower power, stronger RF, or BLE 5.2 features (e.g., beacons, RTLS, better provisioning). (bekencorp.com)
  • Keep using BK7231T for sustaining cost‑sensitive mains‑powered designs leveraging mature community firmware and existing Tuya reference designs. (github.com)
• Firmware and tools
  • Use BK7238‑specific binaries when flashing OpenBeken; never cross‑flash BK7231T images. Verify chip ID over UART first. (github.com)
  • For ESPHome/Arduino via LibreTiny, BK7231T is supported today; confirm BK7238 status before committing to that stack. (docs.libretiny.eu)
• Power budgeting
  • If battery life matters, BK7238’s RX/sleep currents are materially lower; WB3S/BK7231T currents can exceed 100 mA in RX and >180 mA in TX, which strongly favors BK7238 in duty‑cycled applications. (bekencorp.com)

Possible disclaimers or additional notes

• Beken’s BK7238 public brief specifies performance and peripherals but does not disclose the exact MCU core name; avoid relying on unconfirmed core identifications. (bekencorp.com)
• BLE capability on BK7231T is module/SDK dependent; some older module PDFs list “Bluetooth 4.0”, others “BLE 4.2”—verify against the exact module datasheet you are using. (manualshelf.com)

Suggestions for further research

• Review the official BK7238 product brief for the latest RF/power figures and peripheral limits, and check whether Beken has released a full datasheet under NDA if you need register‑level detail. (bekencorp.com)
• For BK7231T‑based modules (WB3S, WB2S, etc.), use the module’s datasheet (RF/power, pinout) rather than generic chip figures; behavior is module‑specific. (manualshelf.com)
• Track OpenBeken releases and LibreTiny/ESPHome issue trackers for BK7238 support maturity if you intend to use those ecosystems. (github.com)

Brief summary

• BK7238 is the modern, lower‑power, BLE 5.2‑capable successor with slightly more RAM, stronger RF, and security niceties (TRNG/eFuse) in small QFN packages—best choice for new designs and battery‑sensitive products. BK7231T remains a cost‑effective legacy option with abundant community firmware, suitable for mains‑powered smart‑home nodes. Use chip‑specific firmware and verify the silicon before flashing to avoid bricks. (bekencorp.com)

If you share your intended product (battery budget, radio range, BLE needs, module form factor), I can turn this into a concrete part/module and firmware recommendation.

Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.