logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

divadiow 16176 369
ADVERTISEMENT
Reply | New topic
  • #331 21608464
    DeDaMrAz
    Level 20  
    @divadiow

    I've noticed NTP sync is pending on your device and I've seen it somewhere else doing the same, does it eventually sync or not? If not workaround I found was to add a 5-10 second delay before NTP driver start.

    @p.kaczmarek2 and @insmod

    Just a ping on NTP driver not starting on some devices, sorry not sure which but I'll check.

    It is on W600 with FW 1.18.131 will test after OTA to new version

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

    OTA on 1.18.135 done, without delay on startDriver NTP

    Code: text Expand Select all Copy to clipboard
    Info:NTP:NTP_CheckForReceive: Error while receiving server's msg


    but after about 60 seconds it gets the NTP

    Code: text Expand Select all Copy to clipboard
    Info:NTP:Seconds since Jan 1 1900 = 3961663620
Info:NTP:Unix time  : 1752674820
Info:NTP:Local Time: 2025-07-16 14:07:00
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #333 21609866
    divadiow
    Level 35  
    [postid:965d656204][/postid:965d656204]
    amebair_ec35fc691074
    PA7 receive - not pushing any remote buttons. log is by itself
    Code: Text
    Log in, to see the code


    NEC signals received OK on BK-N

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
  • #334 21611926
    insmod
    Level 27  
    Opened pull req EF for flasher
    https://github.com/openshwprojects/BK7231GUIFlashTool/pull/59
    Not working. Reading ends up with CRC error. Writing - CRC error on device.
    Main problem is CFG offsets - pinsState_t should be 2 times the size on RTL8720D (64 pins instead of 32).
    Move to unsafe cfg, like i've done earlier in EF demo?

    Added Floaders (AmebaD, AmebaD_New, AmebaDplus, AmebaLite, AmebaZ, AmebaZ2) in base64 format.
    Default AmebaD floader works. New one from ameba-rtos doesn't work. It gets flash id successfully, but doesn't read anything (command api changed?)
  • #335 21612039
    p.kaczmarek2
    Moderator Smart Home  
    Nice, but quick question - does it break compatibility?

    I am hoping to find enough time to add LN882H flashing tomorrow or later upcoming week, so I want to have your changes merged, but I don't want them to break existing config of OBK at the moment.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • Helpful post
    #336 21612047
    insmod
    Level 27  
    [postid:d469f422f4][/postid:d469f422f4]
    It shouldn't. I changed almost nothing in what was already there.
    Only OBKFlashLayout.getConfigLocation started returning sector count as an out variable.
    Everything else was either in RTLFlasher or behind RTL8720DN check.

    I'm not sure if writing config in tandem with firmware would work, since erase is not done for config specifically.

    Different? amebad flashloader sources: https://github.com/particle-iot/realtek_ambd_...ject_lp/asdk/flashloader/rtl_flash_download.c
    Potential newer chips tool? https://github.com/Ameba-AIoT/ameba-rtos/blob..._tools/scripts/flash/base/download_handler.py

    Added after 4 [hours] 1 [minutes]:

    BW20 stock boot log
    Code: text Expand Select all Copy to clipboard
    
 .----------------.  .----------------.  .----------------.  .----------------.   .----------------.  .----------------.  .----------------. 
| .--------------. || .--------------. || .--------------. || .--------------. | | .--------------. || .--------------. || .--------------. |
| |      __      | || |     _____    | || |     _____    | || |     ____     | | | |    _______   | || |  ________    | || |  ___  ____   | |
| |     /  \     | || |    |_   _|   | || |    |_   _|   | || |   .'    `.   | | | |   /  ___  |  | || | |_   ___ `.  | || | |_  ||_  _|  | |
| |    / /\ \    | || |      | |     | || |      | |     | || |  /  .--.  \  | | | |  |  (__ \_|  | || |   | |   `. \ | || |   | |_/ /    | |
| |   / ____ \   | || |      | |     | || |      | |     | || |  | |    | |  | | | |   '.___`-.   | || |   | |    | | | || |   |  __'.    | |
| | _/ /    \ \_ | || |     _| |_    | || |     _| |_    | || |  \  `--'  /  | | | |  |`\____) |  | || |  _| |___.' / | || |  _| |  \ \_  | |
| ||____|  |____|| || |    |_____|   | || |    |_____|   | || |   `.____.'   | | | |  |_______.'  | || | |________.'  | || | |____||____| | |
| |              | || |              | || |              | || |              | | | |              | || |              | || |              | |
| '--------------' || '--------------' || '--------------' || '--------------' | | '--------------' || '--------------' || '--------------' |
 '----------------'  '----------------'  '----------------'  '----------------'   '----------------'  '----------------'  '----------------' 

I | [0] [aiio_main] (main.c:48 aiio_main) Combo AT!
I | [1] [aiio_heap_check] (aiio_heap_check.c:23 aiio_heap_check) rtos free heap size:303k
I | [3] [aiio_main] (aiio_nvs.c:26 aiio_nvs_init) File System Init success
[SERIAL-I] uart idx: 1
I | [102] [aiio_main] (aiio_wifi.c:78 aiio_wifi_init) aiio_wifi_init
interface 0 is initialized
interface 1 is initialized
[WLAN-A] Init WIFI
[WLAN-A] Band=2.4G&5G
[WLAN-A] consume heap 19912 Bytes
[WLAN-I] _init_thread(58), Available heap 286976
I | [143] [aiio_main] (aiio_wifi.c:92 aiio_wifi_init) wifi init ok
I | [143] [aiio_main] (aiio_at_wifi_api.c:1224 cb_wifi_event) <<<<<<<<<  WIFI INIT OK <<<<<<<<<<
E | [144] [aiio_main] (aiio_wifi.c:1010 aiio_wifi_set_country_code) WAIT_TOD func wait to define

################################################

arch:RTL8711D,NULL
company:Ai-Thinker|B&T
Acuqire BT PMU LOCK 
Bluetooth init BT_ADDR in cfgbuf [94:c9:60:f4:73:9c]
hci_phy_efuse[PEFUSE(0x741)] = 0x88
Set baudrate to 3000000 success!
Signature check success: Merge patch v2
FW Version: 20240820135258
FW Length: 12084
Start upper stack
Release BT PMU LOCK 
BD_ADDR: 94:C9:60:F4:73:9C(public)
aiio_ble_init success
ble_mac:94c960f4739c
wifi_mac:94c960f47399
sdk_version:release_bl_iot_sdk_1.6.40
firmware_version:release/V4.18_P1.0.9
compile_time:Nov  4 2024 15:59:05

ready

################################################
W | [425] [aiio_main] (aiio_at_wifi_api.c:1211 aiio_wifi_auto_connect_onboot) [aiio_wifi_auto_connect_onboot()-1211]wifi auto connect off

[WLAN-A] IPS in
I | [5001] [aiio_heap_check] (aiio_heap_check.c:23 aiio_heap_check) rtos free heap size:272k
I | [10001] [aiio_heap_check] (aiio_heap_check.c:23 aiio_heap_check) rtos free heap size:272k
I | [15001] [aiio_heap_check] (aiio_heap_check.c:23 aiio_heap_check) rtos free heap size:272k
I | [20001] [aiio_heap_check] (aiio_heap_check.c:23 aiio_heap_check) rtos free heap size:272k
I | [25001] [aiio_heap_check] (aiio_heap_check.c:23 aiio_heap_check) rtos free heap size:272k


    Backup, taken with crudely modified tool and tool itself are attached.
    Code: text Expand Select all Copy to clipboard
    python3 flash.py -p COM16 -d devices/Profiles/AmebaDplus_FreeRTOS_NOR.rdev -i . -b 1500000 -or bw20.bin

    It can probably be used for RTL8720E, just with a different profile (AmebaLite_FreeRTOS_NOR.rdev)
    Attachments:
  • #337 21612234
    divadiow
    Level 35  
    Cool. Just in time. BW20-12F-Kit should arrive tomorrow
  • #338 21612236
    insmod
    Level 27  
    Restoring this backup to OBK flashed BW20-kit worked.
  • Helpful post
    #339 21612965
    divadiow
    Level 35  
    same
    Code: Text
    Log in, to see the code


    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

    Code: Text
    Log in, to see the code

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken? RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

    Added after 11 [hours] 11 [minutes]:

    OBK. Interesting baud @1500000
    Code: Text
    Log in, to see the code


    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

    Added after 1 [hours] 3 [minutes]:

    seems to have connected and is accessible with 802.11AC WPA3-SAE-only AP

    Code: Text
    Log in, to see the code


    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

    Added after 4 [minutes]:

    802.11N
    Code: Text
    Log in, to see the code


    Added after 26 [minutes]:

    maybe platforms.md needs 2.4Ghz/5Ghz column too
  • #340 21633146
    insmod
    Level 27  
    PKM8710ECF
    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken? RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    Original boot log:
    Code: text Expand Select all Copy to clipboard
    ROM:[V1.0]
FLASHRATE:1
IMG1(OTA1) VALID, ret: 0
IMG1 ENTRY[f801c8d:0]
[BOOT-I] KM4 BOOT REASON: 0 
[BOOT-I] KM4 CPU CLK: 200000000 Hz 
[BOOT-I] KR4 CPU CLK: 200000000 Hz 
[BOOT-I] IMG1 ENTER MSP:[30009fe4]
[BOOT-I] Build Time: Jul 23 2024 17:29:19
[BOOT-I] IMG1 SECURE STATE: 1
[FLASH-I] Flash ID: ef-70-17
[FLASH-I] Flash Read 4IO
[FLASH-I] FLASH HandShake[0x2 OK]
[BOOT-I] PMC_CORE_ROLE: 0 (0 represents AP2NP), NP: 1 (1 represents KR4 is NP) 
[BOOT-I] KR4 XIP IMG[0c000000:69de0]
[BOOT-I] KR4 PSRAM[0c069de0:20]
[BOOT-I] KR4 SRAM[20068000:d98]
[BOOT-I] KR4 BOOT[20004c00:40]
[BOOT-I] KR4 PMC[20005500:3e0]
[BOOT-I] KM4 XIP IMG[0e000000:a58e0]
[BOOT-I] KM4 PSRAM[0e0a58e0:20]
[BOOT-I] KM4 SRAM[2000b000:1280]
[BOOT-I] KM4 BOOT[20005fc0:40]
[BOOT-I] KM4 PMC[20005900:3e0]
[BOOT-I] IMG2 BOOT from OTA 1, Version: 1.1 
[BOOT-I] Start IMG2 @ 0xe0015fd ...
[APP-I] KM4 APP START 
[APP-I] VTOR: 30007000, VTOR_NS:30007000
[APP-I] IMG2 SECURE STATE: 1
[MAIN-I] KR4 OS START 
[CLK-I] [CAL131K]: delta:27 target:2441 PPM: 11061 PPM_Limit:30000 
[CLK-I] [CAL4M]: delta:1 target:320 PPM: 3125 PPM_Limit:30000 
[MAIN-I] KM4 MAIN 
[PMC-I] SYSPMC_OPT 200000
[PMC-I] AP wake event 200040 0
[PMC-I] DSP wake event 80 0
[PMC-I] NP wake event 2f 0
[MAIN-I] KM4 START SCHEDULER 
interface 0 is initialized
interface 1 is initialized
[WLAN-A] Init WIFI
[WLAN-A] MP driver
[WLAN-A] consume heap 12784 Bytes
[WLAN-I] _init_thread(53), Available heap 572032
[WLAN-A] IPS in

    OBK boot log:
    Code: text Expand Select all Copy to clipboard
    ROM:[V1.0]
FLASHRATE:1
IMG1(OTA1) VALID, ret: 0
IMG1 ENTRY[f800a9d:0]
[BOOT-I] KM4 BOOT REASON 0: Initial Power on
[BOOT-I] KM4 CPU CLK: 200000000 Hz 
[BOOT-I] KR4 CPU CLK: 200000000 Hz 
[BOOT-I] IMG1 ENTER MSP:[30009fe4]
[BOOT-I] Build Time: Aug 12 2025 15:28:40
[BOOT-I] IMG1 SECURE STATE: 1
[FLASH-I] Flash ID: ef-70-17 (Capacity: 64M-bit)
[FLASH-I] Flash Read 4IO
[FLASH-I] FLASH HandShake[0x2 OK]
[BOOT-I] PMC_CORE_ROLE: 0 (0 represents AP2NP), NP: 1 (1 represents KR4 is NP) 
[BOOT-I] KR4 XIP IMG[0c000000:557c0]
[BOOT-I] KR4 PSRAM[0c0557c0:20]
[BOOT-I] KR4 SRAM[20068000:2fe0]
[BOOT-I] KR4 BOOT[20004c00:40]
[BOOT-I] KR4 PMC[20005500:3e0]
[BOOT-I] KM4 XIP IMG[0e000000:e3c00]
[BOOT-I] KM4 PSRAM[0e0e3c00:20]
[BOOT-I] KM4 SRAM[2000b000:2e20]
[BOOT-I] KM4 BOOT[20005fc0:40]
[BOOT-I] KM4 PMC[20005900:400]
[BOOT-I] IMG2 BOOT from OTA 1, Version: 1.1 
[BOOT-I] Start IMG2 @ 0xe04aef5 ...
[APP-I] KM4 APP START 
[APP-I] VTOR: [LOCKS-I] K3R040 0i7n0i0t0_,r etVaTrOgRe_tN_Sl:ocks
30007000
[APP-I] IMG2 SECURE STATE: 1
[MAIN-I] KR4 OS START 
[CLK-I] [CAL131K]: delta:27 target:2441 PPM: 11061 PPM_Limit:30000 
[CLK-I] [CAL4M]: delta:1 target:320 PPM: 3125 PPM_Limit:30000 
[LOCKS-I] KM4 init_retarget_locks
[MAIN-I] KM4 MAIN 
[VER-I] AMEBA-RTOS SDK VERSION: 1.1.0
[MAIN-I] File System Init Success
[PMC-I] SYSPMC_OPT 200000
[PMC-I] AP wake event 200040 0
[PMC-I] DSP wake event 80 0
[PMC-I] NP wake event 2f 0
[MAIN-I] KM4 START SCHEDULER 
interface 0 is initialized
interface 1 is initialized
[WLAN-I] LWIP consume heap 1312
[WLAN-A] Init WIFI
[WLAN-I] NP consume heap 19760
[WLAN-I] AP consume heap 17056
[WLAN-I] Available heap after wifi init 534240
OpenRTL8720E, version dev_20250812_154825
Entering initLog()...
Commands registered!
initLog() done!
Info:MAIN:Main_Init_Before_Delay
Warn:CFG:CFG_InitAndLoad: Correct config has been loaded with 38 changes count.
Main_Init_Before_Delay done
Main_Init_Delay
Main_Init_Delay done
[WLAN-A] set ssid xx
Error:CMD:no file early.bat err -2
Info:GEN:PIN_SetupPins pins have been set up.
Info:MAIN:Main_Init_Before_Delay done
Info:MAIN:Main_Init_Delay
Info:MAIN:Main_Init_Delay done
Info:MAIN:Main_Init_After_Delay
Info:MAIN:Registered for wifi changes
Info:MAIN:Connecting to SSID [xx]
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTING - 1
Info:MAIN:Using SSID [xx]
Info:MAIN:Using Pass [xx]
Info:HTTP:TCP server listening
Info:MQTT:MQTT_RegisterCallback called for bT rtl8720eB1137EE2/ subT rtl8720eB1137EE2/+/set
Info:MQTT:MQTT_RegisterCallback called for bT obks/ subT obks/+/set
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/rtl8720eB1137EE2/ subT cmnd/rtl8720eB1137EE2/+
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/obks/ subT cmnd/obks/+
Info:MQTT:MQTT_RegisterCallback called for bT rtl8720eB1137EE2/ subT rtl8720eB1137EE2/+/get
Info:CMD:CMD_StartScript: started @startup at the beginning
Info:CMD:LFS_ReadFile: failed to file autoexec.bat
Info:CMD:CMD_StartScript: failed to get file autoexec.bat
Info:BERRY:[berry init]
Info:BERRY:[berry start]
Info:BERRY:[berry end]
Info:BERRY:[berry start]
Info:BERRY:be_pcall fail, retcode 3
Info:BERRY:top=3
Info:BERRY:stack traceback:
Info:BERRY:   
Info:BERRY:string
Info:BERRY::1:
Info:BERRY: in function `
Info:BERRY:main
Info:BERRY:`
Info:BERRY:stack[1] = type='function' ()
Info:BERRY:stack[2] = type='string' (import_error)
Info:BERRY:stack[3] = type='string' (module 'autoexec' not found)
Info:BERRY:[berry end]
Info:MAIN:Main_Init_After_Delay done
[WLAN-A] start auth to xx:xx:xx:xx:xx:xx
[WLAN-A] auth success, start assoc
[WLAN-A] assoc success(32)
[WLAN-A] set pairwise key 4(WEP40-1 WEP104-5 TKIP-2 AES-4 GCMP-15)
[WLAN-A] set group key 4 1
[WLAN-I] set cam: gtk alg 4 0
[$]wifi connected
Info:MAIN:Time 1, idle 0/s, free 489696, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 0/0 
Info:MAIN:Time 2, idle 0/s, free 489696, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 0/0 
[$]wifi got ip:"192.168.1.124"
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MQTT:mqtt_host empty, not starting mqtt
Info:MAIN:Time 3, idle 0/s, free 492352, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 0/0 
Info:MAIN:Time 4, idle 0/s, free 491456, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 0/0 

    REST OTA is not working, verification passes, but on reboot - verification failure.
    LED - red is PA30, green is PA29 and blue is PA28
    Attachments:
  • #341 21633150
    insmod
    Level 27  
    @p.kaczmarek2
    I merged pull into main and integrated windows easyflash vcxproj and ir for ameba (even if it's broken).
  • #342 21633156
    p.kaczmarek2
    Moderator Smart Home  
    Is it ready to safely merge?

    Then I will try OTA clearup and also ask you to do code review and @divadiow to do testing....
    Helpful post? Buy me a coffee.
  • #343 21633171
    insmod
    Level 27  
    I believe so.

    Only 32700 bytes remain free for RTL87X0C with irRemoteESP enabled by default.

    And PRs on github are down...
  • #344 21633238
    p.kaczmarek2
    Moderator Smart Home  
    Why irRemoteESP? I tested it few days ago on BK7238 and for my RC6 remote, the core IRRemote (Arduino) was more stable.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #345 21633248
    insmod
    Level 27  
    >>21633238
    Because changes were made only to drv_ir_new.cpp, not drv_ir.cpp/drv_ir2.c.
  • #346 21633480
    divadiow
    Level 35  
    insmod wrote:
    but on reboot - verification failure

    ah yes

    Code: Text
    Log in, to see the code


    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
  • #348 21633499
    divadiow
    Level 35  
    insmod wrote:
    Even on RTL8721DA?
    Before last update it worked.


    OK that was a silly test. OTA was PR 1718_merge_c2b8f8e6bc6a to 1.18.154

    REST (red update bar in main GUI - is this REST method? 😳)
    Code: Text
    Log in, to see the code


    HTTP
    Code: Text
    Log in, to see the code


    3rd go on WEB APP

    Code: Text
    Log in, to see the code



    Maybe I wipe and start again. My initial UART to 1.18.154 was with chip erase though. Working for you?
  • #349 21633504
    insmod
    Level 27  
    >>21633499
    REST OTA should've been working in 1718_merge_c2b8f8e6bc6a.
    Both web app/red gui are using rest.
    HTTP works, i've tested it before release.

    No, on RTL8720E i have the same problem, as you did on 3rd go.
    I'll have to check later what is wrong.

    Added after 45 [seconds]:

    Hm, does OTA from https work?
    That way, it can be updated directly from github

    Added after 2 [minutes]:

    It doesn't, i get [OTA-E] [ERROR] Get host ip failed
  • #350 21633509
    divadiow
    Level 35  
    insmod wrote:
    It doesn't, i get [OTA-E] [ERROR] Get host ip failed

    same,

    wiped. started again. different AP.

    HTTP does work :)

    Code: Text
    Log in, to see the code


    Added after 8 [hours] 21 [minutes]:

    just seeing what basic IR would do on the DA. Using MiRemote on mobile phone. Various TVs and AC unit button pushes

    Code: Text
    Log in, to see the code


    Added after 2 [minutes]:

    is there anything specific that wants testing at this point?
  • #351 21634211
    insmod
    Level 27  
    Hm, i've just done successful rest ota on RTL8721DA from fw1 to fw2 and vice versa.
    There were no problems.
    I've wiped the flash before flashing though.
    SPI LED works on DA. So, the only realteks that are broken are A and B.

    My main problem with ota was that for some reason what passes into ota function contains http header. Why??
  • #352 21634244
    p.kaczmarek2
    Moderator Smart Home  
    Wait, what? OTA data with HTTP header? But... you mean before my changes, right? Currently I'm just splitting OTA into hal files, because this large function in rest_interface.c is not readable.
    Helpful post? Buy me a coffee.
  • #353 21634246
    insmod
    Level 27  
    >>21634244
    Before, noticed when i started implementing ota for it.
    Did a hack, but it's not perfect - https://github.com/openshwprojects/OpenBK7231...28dc0ac/src/httpserver/rest_interface.c#L3280
    If i remember correctly, i've had the same problem with XRs. Don't remember how i've solved it, but dome data was already received.
    It required another hack - https://github.com/openshwprojects/OpenBK7231...28dc0ac/src/httpserver/rest_interface.c#L3156
  • #354 21634271
    divadiow
    Level 35  
    insmod wrote:
    Hm, i've just done successful rest ota on RTL8721DA from fw1 to fw2 and vice versa.

    hmm. Just wiped and started again. Same result OTA in web app REST

    Code: Text
    Log in, to see the code


    I'm using Chrome. Will try some other things

    Added after 10 [minutes]:

    Brave (Chromium) does the same thing. Firefox =

    Code: Text
    Log in, to see the code


    What browser are you using?
  • #355 21634285
    insmod
    Level 27  
    >>21634271
    Pure signed Chromium 138.0.7204.101

    Added after 5 [minutes]:

    Oh, and only if device was connected to wifi.
    If it was in ap mode - checksum error.

    Added after 11 [minutes]:

    And i remembered from led testing, that on RTL8710B sometimes first line in startup command was skipped. Didn't notice such behaviour anywhere else.
  • #356 21634306
    divadiow
    Level 35  
    insmod wrote:
    Oh, and only if device was connected to wifi.



    yes, always connected to wifi. always erase/flash in between each OTA. trying a diff machine. not had a success yet. gotta be something stupid.
  • #357 21634312
    insmod
    Level 27  
    >>21634306
    You can check what is wrong by taking a backup first with flashed via rest, second with http and run binary comparison between them.
  • #358 21634315
    divadiow
    Level 35  
    insmod wrote:
    You can check what is wrong by taking a backup first with flashed via rest, second with http and run binary comparison between them.

    good shout.

    other machine Win/Chrome no diff

    Added after 11 [minutes]:

    Linux/FF no diff. If it's on proper wifi I get checksum error and so no reboot and no brick.

    If on Windows AP I get OTA success and brick on reboot. Not had a problem with either AP type with other devices. Weird. Will do backup of difference on Windows AP after brick and HTTP method success

    Added after 22 [minutes]:

    difference starts here. written 1 byte out?

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
  • #359 21635098
    insmod
    Level 27  
    Fixed SPI LED on RTL8710A and RTL8710B.
    Turns out MOSI was high by default, + wrong frequency divider was selected.
  • #360 21636112
    insmod
    Level 27  
    Any other platform that need SPI LED support?
    Realteks all work, from RTL_A to RTL_E. I didn't test long led strips with high led count, only a ring with 12 leds.
    + breaking change for esp8266, added 3 missing pins (io9, io10 and io16).
    Updated docs to include IR status.
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.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT