logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

divadiow 31089 392
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #361 21636145
    divadiow
    Level 38  
    insmod wrote:
    Any other platform that need SPI LED support?


    There are these Zengge BL602s https://www.elektroda.com/rtvforum/topic4058754.html

    I have at least one.

    Platforms.md is SO useful now, I keep needing to check it!

    Added after 1 [hours] 58 [minutes]:



    interesting. RTL8711AF device in the wild https://www.reddit.com/r/indotech/comments/1k...ung_multi_tap_lg_mttlw01_teardown_discussion/

    PCB with RTL8711AF chip, push button, and various electronic components

    Added after 1 [hours] 17 [minutes]:

    ah AF ≠ AM
    We don't support AF
    insmod wrote:
    RTL8710AF lacks SDRAM, so not supported. Only RTL8711AM/RTL8195AM are.
    Things are truly difficult when there is no XIP support.
  • ADVERTISEMENT
  • #362 21636342
    p.kaczmarek2
    Moderator Smart Home  
    I guess we need Platforms.md entry for NOT supported platforms like RTL8710AF
    Helpful post? Buy me a coffee.
  • #363 21648741
    array81
    Level 8  
    Has anyone tried using OpenBeken on Teckin SP22 sockets (RTL8710BN - T112_V1.1)? Is there a configuration file?

    Added after 1 [hours] 31 [minutes]:

    I used ltchiptool to flash OpenRTL8710B_1.18.162.bin but no wifi is generated. Any idea?
  • ADVERTISEMENT
  • #364 21648828
    insmod
    Level 31  
    >>21648741
    Disable autodetect parameters and set starting address to 0x0
  • #365 21648847
    array81
    Level 8  
    >>21648828
    Starting address is 0x0, see the image:

    Screenshot of ltchiptool v4.12.1 with the start address set to 0x0 for a Realtek AmebaZ device.
  • #366 21648859
    insmod
    Level 31  
    >>21648847
    Tried it myself, got "Please Re-boot and try again, or re-burn the flash image" in uart.

    Added after 12 [minutes]:

    Flash attached file to 0x0
    Then flash OpenBeken at 0xB000
    Attachments:
    • boot_all.bin (4.56 KB) You must be logged in to download this attachment.
  • #368 21648937
    array81
    Level 8  
    >>21648859
    I tried. I first flashed the file you attached, then the OpenBK one, changing the starting address. I'm attaching images of the two settings. Nothing seems to change. Also, the LED on the RTL8710BN doesn't flash when I power the socket. I had previously installed ESPHome (with LibreTiny), and it worked, but it had reboots due to a known bug (the latest versions of ESPHome have problems with LibreTiny), so I was hoping to use OpenBK (which I already use on other devices).

    Window of litchiptool v4.12.1 showing flash settings for Realtek AmebaZ chip using COM7 USB-SERIAL CH341 interface.

    Screenshot of ltchiptool showing flash settings for Realtek RTL8710BN microcontroller.

    Added after 15 [minutes]:

    >>21648875

    I tried resetting the device and then flashing OpenBK but nothing changed:

    Screenshot of Ameba Image Tool V2.7.18 with three selected binary files and HEX addresses set for flashing via COM7.

    Added after 2 [hours] 7 [minutes]:

    I managed to do it by following divadiow's instructions step by step.
    Now the problem is that I can't find the PINs. So far, I've only found the red and blue LEDs. I can't find the button, the relay, or the energy meter module.

    Added after 42 [minutes]:

    Is there a simple way to detect BL0937 pins?
  • #369 21649483
    divadiow
    Level 38  
    is the red LED IO9 and blue LED IO7?

    try IO10 as a button.

    If yes to the above try these for BL0937

    sel IO2
    cf IO4
    cf1 IO8
  • #370 21654509
    array81
    Level 8  
    >>21649483
    Thanks.

    These are the correct PINs for the Teckin SP22 with T112 v1.1

    "0": "BL0937CF;63",
    "1": "LED_n;53",
    "8": "BL0937CF1;55",
    "9": "BL0937SEL;54",
    "10": "Rel;53",
    "11": "LED_n;52",
    "14": "Btn;53"

    Now I have another problem with a socket of the same model. I don't have a backup for this socket (I forgot to do so). I tried loading the backup of the other socket, then OpenBK, then deleting 4k from 0x080D0000. However, the socket keeps going into a boot loop. Any suggestions?

    Can I backup the socket I got working with ltchiptool and then use ltchiptool to load the file on the new socket? (Same make and model)
  • #371 21696520
    divadiow
    Level 38  
    insmod wrote:
    >>21695089
    This reminded me about RTL_B initial flashing problem.
    Fix: https://github.com/openshwprojects/OpenBK7231T_App/pull/1802


    https://github.com/openshwprojects/FlashTools/tree/main/Realtek/AmebaZ_FlashTool
    Code: Text
    Log in, to see the code


    Code: Text
    Log in, to see the code


    =

    Code: Text
    Log in, to see the code


    Added after 4 [hours] 57 [minutes]:

    Did you sort your issue @array81?
  • #372 21697846
    divadiow
    Level 38  
    array81 wrote:
    These are the correct PINs for the Teckin SP22 with T112 v1.1


    White TECKIN smart plug with European-style socket

    https://github.com/OpenBekenIOT/webapp/pull/2...mits/dbc2537ef3c2d4881f31ab91fc2c338db47bb482

    Should one of those LED_n be standard LED and on the same channel as the other LED and relay so that one LED is off when device is on and they reverse when device is off? Otherwise you just have control of a single LED independent of anything else.
  • ADVERTISEMENT
  • #373 21698893
    array81
    Level 8  
    >>21697846
    Yes, I solved it. Actually, the problem seems to be that once I flashed the firmware following your guide, the socket seems to go into a boot loop. I actually think it's a USB power issue. If I remove the programming module and reassemble the socket, powering it normally, it works.

    Currently, the LEDs work like this: they're all off when the socket is off and turn blue when it's on. There's also a red LED, but it never lights up.. But that's fine, if you want.

    I'm just having an annoying problem with MQTT. Sometimes, when the power goes out, the outlet seems to be exchanging data with Mosquitto when it comes back on, but HA stops seeing the outlet. I have to force discovery of the outlet's web interface, otherwise HA won't see it anymore. This is annoying.
  • Helpful post
    #374 21729481
    insmod
    Level 31  
    Revamped RTL flasher code.
    Started using full Xmodem for both read and write, fixed long erase, added checksum verification for both read and write. Flashloader for AmebaZ (read with checksum and read flash id), unified code with AmebaD.
  • #375 21729605
    divadiow
    Level 38  
    very nice. playing with DN.

    BK7231 Easy UART Flasher interface with “Reading success!” message displayed BK7231 Easy UART Flasher UI showing flash log and warning/error messages Easy UART Flasher interface with “Write complete!” message in main window

    whole-flash 4mb restore worked too. obk flashed booted
  • ADVERTISEMENT
  • Helpful post
    #376 21729963
    divadiow
    Level 38  
    Z1 erase completes but GUI sits like it's in progress. stops after baud change

    Code: Text
    Log in, to see the code


    BK7231 Easy UART Flasher interface during flash memory erase operation

    Z1 erase succeeds and subsequent 115200 read shows blank flash

    BK7231 Easy UART Flasher UI with “Reading success!” and memory dump log visible.

    921600 read success
    BK7231 Easy UART Flasher interface showing Reading success! message

    1500000 read success
    BK7231 Easy UART Flasher interface with Reading success! message displayed

    2000000 read success (though I'm guessing it's topping out somewhere close to 1mb baud - should time each probably)
    Screenshot of BK7231 Easy UART Flasher showing “Reading success!” message

    2000000 OBK write success to blank
    Screenshot of BK7231 Easy UART Flasher showing “Write complete!” message
    OBK boots :)
  • #377 21782369
    divadiow
    Level 38  
    Code: Text
    Log in, to see the code


    UG OTA file works straight from OpenRTL. Boots. Missing a key vault of course
    Code: Text
    Log in, to see the code
  • #378 21783227
    p.kaczmarek2
    Moderator Smart Home  
    We need to add info here which is which Ameba:
    Dropdown list with chip names, RTL87X0C option highlighted
    I am getting lost myself there, I've got this to flash:
    Electronic module with chip and antenna held by tweezers

    Added after 2 [minutes]:

    Green PCB with MR2EHK_REV7.0 label and gold contacts at the bottom edge
    Module startup configuration table with modes and GPIO settings
    Helpful post? Buy me a coffee.
  • #379 21783235
    divadiow
    Level 38  
    Yes. I do need to lookup RTLs sometimes to be sure.

    What does more info look like though, EF is kinda small and crowded. A tab where anyone can type in part or complete models of any chip markings and a match is made in real-time below? lol, dunno. dunno
  • #380 21783244
    p.kaczmarek2
    Moderator Smart Home  
    Just like we have (T4) next to BK name, then add (Ameba Z2) ?

    Added after 3 [minutes]:

    Code: text Expand Select all Copy to clipboard
    

== Rtl8710c IoT Platform ==
Chip VID: 5, Ver: 3
ROM Version: v3.0

== Boot Loader ==
Aug 31 2021:15:42:24
Boot Loader <==

== RAM Start ==
Build @ 14:51:40, Jan  5 2024
$8710c>interface 0 is initialized
interface 1 is initialized
Initializing WIFI ...

WIFI initialized
MRS-WIFI-COUNTR-0069 | set country code: JP, 0x0b

 write mac address success, please reset wifi driver!
init_thread(61), Available heap 0x356308
###############################
####  Meross Smart Things  ####
###############################

reset reason : 0
       model : mss810

Enter INTERACTIVE MODE
#          mac : 48:e1:e9:d8:d0:ce
    chip set : rtl8710cm
      hw_ver : 7.0.0
      fw_ver : 7.3.3
    compiler : gcc 6.5.0
compile time : 2024/01/05-14:51:34

 curr_fw_idx : 1
Login:


    Added after 2 [minutes]:

    Screenshot of BK7231 Easy UART Flasher during flash memory reading of RTL87X0C chip.
    Error..
    Screenshot of BK7231 Flasher showing flash memory read error message

    Added after 19 [minutes]:

    Screenshot of BK7231 Easy UART Flasher showing read completed and Tuya Config extraction error
    Helpful post? Buy me a coffee.
  • #381 21783290
    divadiow
    Level 38  
    Yes. I have found Z2 reading to often be problematic
  • #382 21783307
    p.kaczmarek2
    Moderator Smart Home  
    I am at configuration stage, so it seems to work:
    Wi-Fi module configuration screen showing OpenRTL87X0C_E9D8D0CE and device details
    Helpful post? Buy me a coffee.
  • #384 21785852
    p.kaczmarek2
    Moderator Smart Home  
    I guess it can help a lot. Merged.

    Maybe we could make it somehow even more user friendly, but how?

    Add a link to topic guide when flashing for given platform starts?
    Helpful post? Buy me a coffee.
  • #386 21786353
    array81
    Level 8  
    Anyone having problems with MQTT and Home Assistant? After some time (I'm not sure if it's hours or days), the device becomes unavailable on Home Assistant even though it works. At that point, I have to go into "Home Assistant Configuration" and press "Start Home Assistant Discovery," and the device immediately starts working again. For a while longer, then the problem starts again. Is there a way to permanently fix this?
  • #387 21786432
    p.kaczmarek2
    Moderator Smart Home  
    I don't recognize this issue but I know that you can automatically invoke HA discovery on reboot or on timer via autoexec.bat commands.
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md
    Screenshot of a documentation table with highlighted “scheduleHADiscovery” text
    Helpful post? Buy me a coffee.
  • #388 21793683
    divadiow
    Level 38  
    regarding Z2 in Easy Flasher, I'm just trying to work out the situation regarding flash pin pairs and how it handles the two. This is from the PG Tool guide doc

    Table mapping Flash Pins to IC part numbers RTL8710CX, RTL8720CM, and RTL8720CF


    Screenshot of AmebaZ2 PG Tool interface showing firmware flashing settings

    Dropdown menu for selecting flash pins in configuration software

    3 pairs it seems.
    Attachments:
    • UM0503 Realtek Ameba-ZII Image PG Tool user manual.pdf (601.83 KB) You must be logged in to download this attachment.
  • #389 21802553
    divadiow
    Level 38  
    divadiow wrote:
    3 pairs it seems.


    renpeipei-realtek left a comment (Ameba-AIoT/ameba-rtos-z2#13)
    Code: Text
    Log in, to see the code
  • #390 21802564
    p.kaczmarek2
    Moderator Smart Home  
    but doesn't it mean that old devices (from old batches) will still use it?


    By the way, why do we even have to choose it as in the dropdown list?
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion centers on the compatibility and support of Realtek RTL8720DN, RTL8710B, and RTL8710BX chips with the OpenBeken firmware and SDK. The RTL8720CF-based modules (e.g., BW15, WBR3) are confirmed to be supported by the AmebaZ2 family SDK and OpenBeken ports, with functional WiFi, GPIO, flash configuration, OTA, UART, and basic peripherals. However, RTL8710BX and RTL8710B (AmebaZ family) present challenges such as WiFi initialization freezes, memory management issues, and incomplete SDK support, including lack of static IP and WiFi scanning. OTA updates are functional but have occasional reboot issues, especially on RTL8710B. PWM support is mostly stable after fixes, while MQTT required patching due to missing authorization code in the Realtek LWIP stack. Power-saving modes and sensor drivers (DHT11, DS18B20) have been tested with varying success across platforms. Flashing RTL modules requires specific UART converters (e.g., CH340G) and careful wiring; some modules need manual pin pulls and special flashing tools like AmebaZ2 PGTool. TuyaMCU and energy metering ICs (BL0937, BL0942) support is under active development and testing, with UART and GPIO interrupt methods used. Memory partitioning for configuration, LittleFS, and Tuya config extraction is being optimized to avoid overwriting user data. Static IP implementation required workarounds due to sscanf inconsistencies on RTL and related platforms. A UART-to-TCP bridge driver has been developed for some modules. Overall, RTL8720CF modules have good OpenBeken support, RTL8710B is progressing but unstable, and RTL8710BX remains problematic. The community is actively testing, fixing, and improving support for these Realtek chips within OpenBeken and related tools.
Generated by the language model.
Today's popular
ADVERTISEMENT