logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

NiceMCU XH-WB3S BK7238 Flashing, Testing, Pinout, Development, Porting

divadiow 21243 381
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #361 21834217
    insmod
    Level 31  
    Posts: 1356
    Help: 161
    Rate: 426
    It's old, present since early bk7252 sdks, i think?
    Most important lib is rtt_ota, but it's closed source.
  • ADVERTISEMENT
  • #362 21869255
    divadiow
    Level 38  
    Posts: 4880
    Help: 427
    Rate: 869
    not exactly ESP8266 bargain basement cheap, but couldn't resist.

    Store checkout screenshot: NiceMCU WB5E board, £5.49, total £8.27, estimated delivery Apr 10, 2026
  • #365 21876990
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14444
    Help: 650
    Rate: 12416
    What is OpenSDK?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #367 21877108
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14444
    Help: 650
    Rate: 12416
    Maybe we should change OBK name to OpenSDK...
    Helpful post? Buy me a coffee.
  • #368 21877163
    divadiow
    Level 38  
    Posts: 4880
    Help: 427
    Rate: 869
    could do..

    poll needed with options?

    I know there's been mention of renaming OpenBK7231T_App in the past. Is that still on the cards?
  • #369 21877331
    DeDaMrAz
    Level 22  
    Posts: 600
    Help: 34
    Rate: 127
    p.kaczmarek2 wrote:
    Maybe we should change OBK name to OpenSDK...


    My vote is for OpenIOT 🙂 even got the domen purchased...
  • #370 21877332
    divadiow
    Level 38  
    Posts: 4880
    Help: 427
    Rate: 869
    DeDaMrAz wrote:
    My vote is for OpenIOT 🙂 even got the domen purchased...

    oh yes! :D
  • #371 21877340
    insmod
    Level 31  
    Posts: 1356
    Help: 161
    Rate: 426
    My vote is for OpenBeken, simply because it's more known/recognizable.
    Even if there are more non-Beken platforms than Beken now.
  • ADVERTISEMENT
  • #372 21877346
    DeDaMrAz
    Level 22  
    Posts: 600
    Help: 34
    Rate: 127
    insmod wrote:
    Even if there are more non-Beken platforms than Beken now.


    I would argue for this more, beken is "legacy" at this point, even Tuya removed their name from chips.
  • #373 21877348
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14444
    Help: 650
    Rate: 12416
    insmod wrote:
    My vote is for OpenBeken, simply because it's more known/recognizable.

    Oh no, that's exactly what I think as well. That's the main reason for the hesistance for change.
    Helpful post? Buy me a coffee.
  • #374 21877352
    DeDaMrAz
    Level 22  
    Posts: 600
    Help: 34
    Rate: 127
    We can always keep it as legacy name and even call it out as derived from openbeken but we are long past just Beken chips and I think we have just started - just my 2 cents of course.

    openIOT.me domain is in my possession just in case 😉
  • #375 21877817
    divadiow
    Level 38  
    Posts: 4880
    Help: 427
    Rate: 869
    insmod wrote:
    My vote is for OpenBeken, simply because it's more known/recognizable.


    I wonder if a name that uses the real company name would invite the unwanted attention of Beken. like LibreTuya -> Tiny
  • #377 21882551
    DeDaMrAz
    Level 22  
    Posts: 600
    Help: 34
    Rate: 127
    10 out of 10 times spikes in any reading is a bad cap in the power supply - my experience on more than 10 devices 😁
  • #378 21882553
    divadiow
    Level 38  
    Posts: 4880
    Help: 427
    Rate: 869
    oh sure, but this spikiness is fixed by setting loglevel to 0

    I was using the measurement spike issue as a sneaky way to justify posting about that PR and its fix, even though it doesn't ultimately relate
  • #380 21895692
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14444
    Help: 650
    Rate: 12416
    Interesting, a TuyaMCU?
    Helpful post? Buy me a coffee.
  • #381 21895704
    divadiow
    Level 38  
    Posts: 4880
    Help: 427
    Rate: 869
    seems to be, though it's not quite standard. the MCU I think sends product info first instead of heartbeat or something. TMDA won't talk to it. IO34 might need something on it too, low or high hasn't helped bring it to life though.

    it boots on BK7258. boot log without TuyaMCU comms:

    Code: Text
    Log in, to see the code
  • ADVERTISEMENT
  • #382 21895833
    divadiow
    Level 38  
    Posts: 4880
    Help: 427
    Rate: 869
    MCU is on IO0/IO1, 38400 baud.

    XH-WB5E NiceMCU doesn't route IO1 from module to a header, so had to solder

    NiceMCU XH-WB3S BK7238 Flashing, Testing, Pinout, Development, Porting

    NiceMCU XH-WB3S BK7238 Flashing, Testing, Pinout, Development, Porting Phone screenshot of “Advanced Settings” with a green controller icon featuring a solar panel

    Attached is simulator used to communicate and reset dump for pairing.

    At boot the BK7236 asks for product info of the TuyaMCU by sending 
    55 AA 00 01 00 00 00
    . Simulator replies with product key for this product.
    Attachments:
    • TuyaMCU_BK7236_T3_GUI_Simulator_v1.9.zip (276 Bytes) You must be logged in to download this attachment.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion centers on the NiceMCU XH-WB3S development board featuring the BK7238 SoC, initially suspected to be BK7231T but confirmed as BK7238. Users share experiences with flashing, testing, and porting firmware, including challenges with encryption keys, flash IDs, and bootloader compatibility. The BK7238 uses 2MB flash with varying encryption keys per chip, complicating universal firmware flashing. Tools like BKFIL and Easy Flasher (EF) are used for backup and restore, with EF supporting full flash erase and restore including bootloader. Flash ID support was extended to include missing flash chips to avoid CRC errors. Arduino SDK and Beken FreeRTOS SDK (version 3.0.70.1 and newer 3.0.76) are referenced for development, with partial support for BK7238 and related chips (BK7231N, BK7231U, BK7252). Porting efforts include adapting delay functions for 160MHz BK7238, resolving flashvars alignment issues due to 64-bit time_t, and addressing HTTP server and TCP socket stability problems in LWIP. OTA updates are functional but require correct image types and bootloader versions. Power save modes and their impact on peripherals like BL0937 energy meter and DS18B20 sensors are discussed, with some instability noted under power save. SPI flashing and UART flashing methods are compared, with SPI preferred for some devices. BK7231U (CC8000 chip) support is emerging, with builds available but some undefined references and boot issues. BK7252 camera module support is experimental, with encrypted flash complicating firmware use. Users report issues with DS18B20 sensor timing on BK7238 due to delay_us inaccuracies, partially fixed by new SDK delay implementations. Logging and MQTT load affect system stability and sensor reading consistency. The community shares flash dumps, toolchain links, and SDK forks to aid development and testing. Overall, the thread provides detailed technical insights into BK7238-based NiceMCU boards' flashing, SDK porting, peripheral support, and firmware development challenges and progress.
Generated by the language model.
Today's popular
ADVERTISEMENT