logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

divadiow 10503 276
ADVERTISEMENT
Reply | New topic
  • #211 21444276
    divadiow
    Level 34  
    wait. I'm a fool. I've made an assumption about the BW16E. It is 4mb, not 2mb.

    Electronic module on a purple PCB with visible components and chips.

    🤦🏼‍♂
    Screenshot showing Flash setting with a default value of 4MB.
  • ADVERTISEMENT
  • #212 21444415
    p.kaczmarek2
    Moderator Smart Home  
    I didn't notice it as well, but now imagine how much drivers it could fit. Everything enabled by default, even charts...
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #213 21444607
    divadiow
    Level 34  
    if only 4mb chips were already the minimum for most IoT devices instead of the 2mb BK7231N everywhere.

    Added after 37 [minutes]:

    the FlashTools GH has more bits in now including the original pvvx rtltool and an unzipped one with adjusted delay
    List of software tool files for Ameba chips.

    Screenshot showing two files in a folder: RTL872xDx and rtltool_RTL872xDx_orig.zip.

    Screenshot of ROM Bootloader code with creation date 17/02/2025.
  • ADVERTISEMENT
  • #214 21446863
    p.kaczmarek2
    Moderator Smart Home  
    My gateway arrived, how does one flash WBRG1? It seems only UART port is needed?
    Schematic of WBRG1 module with top and bottom view.
    Green circuit board with mounted modules labeled WBRG1 and Z3L.
    WBRG1 circuit board with visible components and USB port.
    Green electronic module with visible traces on a white background.
    Helpful post? Buy me a coffee.
  • #216 21446909
    p.kaczmarek2
    Moderator Smart Home  
    Ah, so I just ground UART pin at reboot time. Ok.

    It's not from Alie, I haven't found a suitable one on Ali yet, I got one locally.
    Console reading flash data using rtltool.

    Added after 5 [minutes]:

    https://github.com/openshwprojects/FlashDumps/commit/09d910414a3f3fe190f754f4a4d5f1583fe6f186

    Added after 55 [minutes]:

    Boot log:
    Code: text Expand Select all Copy to clipboard
    

#calibration_ok:[2:19:11] 

[TY BOOT2] Images check crc ok, run to application


#example_sw_pta_init success.

sys_thread_new CreatedTask:0x21235a0

interface 0 is initialized

interface 1 is initialized



Initializing WIFI ...Into tuya config loade.

[01-01 18:12:15 TUYA D][uf_flash_file_app.c:215] uf shrink...

[01-01 18:12:15 TUYA I][mqc_app.c:350] mqc app init ...

[01-01 18:12:15 TUYA I][uni_thread.c:228] thread_create name:sys_timer,stackDepth:4096,totalstackDepth:4096,priority:5

[01-01 18:12:15 TUYA I][uni_thread.c:228] thread_create name:cmmod,stackDepth:5120,totalstackDepth:9216,priority:4

[01-01 18:12:15 TUYA D][mqc_app.c:144] mq_pro:5 cnt:1

[01-01 18:12:15 TUYA D][mqc_app.c:144] mq_pro:31 cnt:2

[01-01 18:12:15 TUYA D][svc_online_log.c:295] svc online log init success

[01-01 18:12:15 TUYA E][log_seq.c:864] logseq empty

[01-01 18:12:15 TUYA I][uni_thread.c:228] thread_create name:wk_th-0,stackDepth:5120,totalstackDepth:14336,priority:3

[01-01 18:12:15 TUYA E][ws_db_gw.c:80] wd_protected_read fails gw_bi -23

[01-01 18:12:15 TUYA D][ws_db_gw.c:208] gw base read finish:-23

[01-01 18:12:15 TUYA D][tuya_bt_sdk.c:92] ty bt cmmod regist ok:1

[01-01 18:12:15 TUYA D][tuya_ble_api.c:312] upd adv para, send conn_req beacon.

[TOS_NOTICE]tuya_os_adapt_param_init mode:0x01

[TOS_DBG]tuya_os_adapt_bt_mode_set ability 0x1 enable, force:1, real_bt_mode:0x1, expect_bt_mode:0x1

[01-01 18:12:15 TUYA N][tuya_ble_api.c:647] ble sdk re_inited

[01-01 18:12:15 TUYA D][tuya_ble_active.c:523] bt active init

[01-01 18:12:15 TUYA N][tuya_bt_sdk.c:141] ty bt sdk init success finish


 zigbee_boot_pin(TY_GPIOB4) init output high.



WIFI initialized



init_thread(58), Available heap 0x28d620[01-01 18:12:15 TUYA D][uni_thread.c:250] Thread:sys_timer Exec Start. Set to Running Stat

[01-01 18:12:15 TUYA D][uni_thread.c:250] Thread:cmmod Exec Start. Set to Running Stat

[01-01 18:12:15 TUYA D][uni_thread.c:250] Thread:wk_th-0 Exec Start. Set to Running Stat

[01-01 18:12:15 TUYA N][uni_log.c:197] SetLogManageAttr 2

[01-01 18:12:15 TUYA N][tuya_device.c:155] SDK INFO: < TUYA IOT SDK V:3.1.8 BS:40.00_PT:2.2_LAN:3.4_CAD:1.0.4_CD:1.0.0 >

< BUILD AT:2023_12_11_11_03_30 BY ci_manage FOR ty_iot_gw_wr_wf_sdk AT rtl8720dn >

IOT DEFS < WIFI_GW:1 DEBUG:1 KV_FILE:0 SHUTDOWN_MODE:0 LITTLE_END:1 TLS_MODE:2 ENABLE_CLOUD_OPERATION:0 OPERATING_SYSTEM:98 ENABLE_SYS_RPC:0 RELIABLE_TRANSFER:1 ENABLE_LAN_ENCRYPTION:1 ENABLE_LAN_LINKAGE:1 ENABLE_LAN_DEV:1 >



[01-01 18:12:15 TUYA N][tuya_device.c:156] SDK_ID: TuyaOS2.3.2_ty_iot_gw_wr_wf_sdk_feature-3.1.8-beta.28_rtl8720dn_mini_muli_gw_config_uf_1.0.70-beta.10

[01-01 18:12:15 TUYA N][tuya_device.c:157] [keym557nqw3p8p7m 8721csm_bt_zg_gw 1.7.2] at Dec 11 2023 15:19:06

[01-01 18:12:15 TUYA N][tuya_device.c:158] subdev_max_cnt[128]

[01-01 18:12:15 TUYA N][tuya_device.c:142] ble version:bluetooth_mgr:1.2.2-beta.105 1

[01-01 18:12:15 TUYA N][simple_flash.c:459] key_addr: 0x7d7000   block_sz 4096

[01-01 18:12:15 TUYA N][simple_flash.c:548] get kvs:

0x8c 0xea 0xc 0x12 0xe5 0x43 0xd8 0xba 0xe8 0xbd 0x74 0xe7 0x7a 0xdc 0x1 0xc6 

[01-01 18:12:16 TUYA N][tuya_main.c:272] mf_init succ

[01-01 18:12:16 TUYA N][tuya_main.c:273] firmware compiled at Dec 11 2023 15:19:04

[01-01 18:12:16 TUYA N][tuya_device.c:173] cad_ver:1.0.4,sw_ver:1.7.2

[01-01 18:12:16 TUYA E][tuya_gw_prod_test_auth_info.c:553] wd_common_read tptk_mac_need_update ret:-6

[01-01 18:12:16 TUYA E][tuya_gw_prod_test_auth_info.c:31] need not update wifi mac. has not prodtest



[01-01 18:12:16 TUYA E][tuya_ws_db.c:728] kvs_read err:-6

[01-01 18:12:16 TUYA E][tuya_device.c:217] read mf config fail! set to default!

[01-01 18:12:16 TUYA N][user_led.c:458] led_hardware_init,pin -> TY_GPIOA25

[01-01 18:12:16 TUYA N][user_led.c:458] led_hardware_init,pin -> TY_GPIOB22

[01-01 18:12:16 TUYA N][tuya_gw_mgr.c:1014] current gw_cap_full_attr: 0x00000002

[01-01 18:12:16 TUYA N][user_key.c:91] key_init success,key pin -> TY_GPIOB23

[01-01 18:12:16 TUYA N][tuya_device.c:255] WatchDog init OK!

[01-01 18:12:16 TUYA N][tuya_device.c:258] tuya_z3_intf_init......

[01-01 18:12:16 TUYA E][tuya_iot_ext_api.c:168]  /tuya/engineer_dev_flag.ini is not exist

[01-01 18:12:16 TUYA N][rcd_flash_app.c:701] maxlen 131072, pagesz 64, sec_num :1, 5 65535 0 



bit map len[32] 0xe0 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 

[01-01 18:12:16 TUYA N][rcd_flash_app.c:701] maxlen 131072, pagesz 64, sec_num :1, 6 65535 0 



bit map len[32] 0xe0 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 

[01-01 18:12:16 TUYA N][rcd_flash_app.c:701] maxlen 131072, pagesz 64, sec_num :1, 7 65535 0 



bit map len[32] 0xe0 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 

[01-01 18:12:16 TUYA N][tuya_z3_uf_file.c:68] =====devFileInit=====



[01-01 18:12:16 TUYA N][af-main-host.c:659] >>>Normal UART bootup with FLOWCTRL<<<

rsy value=5srsy value=2srsy value=1srsy value=5srsy value=2srsy value=2srsy value=2srsy value=7680srsy value=30srsy value=32768srsy value=1srsy value=30000srsy value=32srsy value=16srsy value=10srsy value=32srsy value=120srsy value=12srsy value=250srsy value=8srsy value=0srsy value=65408srsy value=180s------------0000000000emAfTaskId:0

[01-01 18:12:18 TUYA E][uf_flash_file_app.c:300] uf_open devices.txt err 8

[01-01 18:12:18 TUYA N][device-table.c:944] read devices.txt

[01-01 18:12:18 TUYA E][device-table.c:951] ufopen devices txt error

[01-01 18:12:18 TUYA E][uf_flash_file_app.c:300] uf_open zb_up_file_num err 8

[01-01 18:12:18 TUYA E][ota-storage-linux.c:383] fail to open upgrade number flag file.

[01-01 18:12:18 TUYA E][uf_flash_file_app.c:300] uf_open zb_up_file_num err 8

[01-01 18:12:18 TUYA E][ota-storage-linux.c:383] fail to open upgrade number flag file.

[01-01 18:12:19 TUYA N][tuya_gw_mgr.c:710] current gw_protocol_full_attr: 0x00000002

[01-01 18:12:19 TUYA N][tuya_gw_mgr.c:710] current gw_protocol_full_attr: 0x00000002

[01-01 18:12:19 TUYA N][tuya_device.c:271] tuya_z3_intf_init success.

[01-01 18:12:19 TUYA N][tuya_device.c:276] tuya_z3_intf_get_coo_ver success[2.4.1]

[01-01 18:12:19 TUYA N][tuya_gw_pt_app.c:428] tuya_testframe_register_uart_func success

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_print_sdkInfo:1893]:###########################################

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_print_sdkInfo:1894]:###########################################

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_print_sdkInfo:1895]:#######PROTOCOL VERSION:1.0.0##############

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_print_sdkInfo:1896]:#######SDK      VERSION:1.0.2##############

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_print_sdkInfo:1897]:###########################################

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_print_sdkInfo:1898]:###########################################

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_init:2014]:####tuya_prodtest_init success####



[01-01 18:12:19 TUYA W][tuya_gw_pt_app.c:129] #####PRODTEST UART REV TIMEOUT

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_thread_process:1871]:***************TUYA TEST THREAD EXIT****************

PT DEBUG:[tuya_prod_test.c]:[tuya_prodtest_deinit:2037]:####tuya_prodtest_deinit process####



[TOS_DBG]set_wifi_work_mode:2





LwIP_DHCP: dhcp stop.


Deinitializing WIFI ...


WIFI deinitialized


Initializing WIFI ...


WIFI initialized

[TOS_DBG]tuya_os_adapt_bt_stack_init:0x01






BT BUILD Date: 2023/12/11-15:18:12 


BT Reset...


physical efuse: has data hci_tp_phy_efuse[1]= 9e 




hci_tp_phy_efuse[0]=0,


bt_iqk_dump:    DUMP,


the IQK_xx  data is 0xe7,


the IQK_yy  data is 0x3fd,


the QDAC  data is 0x20,


the IDAC  data is 0x1f,


hci_read_rom_check: rom_version 0x0002, bt_hci_chip_id 0x0003



BT ADDRESS: 38:a5:c9:45:fb:c6




 WRITE  physical FLATK=tx_flatk=0 


Set baudrate to 921600




hci_tp_config:BT INIT success 7


Start upperStack

[TOS_DBG]bt_dev_state_evt init:1, adv:0, scan:0, cause:0x0



[TOS_DBG][BLE peripheral] GAP stack ready




[TOS_DBG]le_adv_start success

[TOS_DBG]bt_dev_state_evt init:1, adv:1, scan:0, cause:0x0



[TOS_DBG]bt_dev_state_evt init:1, adv:2, scan:0, cause:0x0



[TOS_DBG]GAP adv start



[01-01 18:12:21 TUYA N][tuya_main.c:207] current product ssid name:tuya_zg_bt_gw_scan

[TOS_ERR]not find scan ssid (tuya_zg_bt_gw_scan)



[TOS_DBG]not connected yet

[TOS_DBG]tuya_os_adapt_bt_mode_set ability 0x4 enable, force:1, real_bt_mode:0x5, expect_bt_mode:0x5

[TOS_DBG]tuya_os_adapt_bt_mode_set ability 0x2 enable, force:1, real_bt_mode:0x7, expect_bt_mode:0x7

[01-01 18:12:22 TUYA N][tuya_gw_mgr.c:710] current gw_protocol_full_attr: 0x00000043

[01-01 18:12:22 TUYA N][tuya_gw_mgr.c:1014] current gw_cap_full_attr: 0x00000003

[01-01 18:12:22 TUYA N][tuya_gw_mgr.c:710] current gw_protocol_full_attr: 0x0000004b

[01-01 18:12:22 TUYA N][tuya_device.c:344] --> tuya_bluetooth_srv_init success, support beacon dev.

[01-01 18:12:22 TUYA N][user_home_security.c:184] --> user_home_security_init success

[01-01 18:12:22 TUYA N][user_app.c:334] get local.dbglog fail

[01-01 18:12:22 TUYA E][tuya_device.c:359] call user_app_load_debug_file() return -6

[01-01 18:12:22 TUYA N][rcd_flash_app.c:701] maxlen 131072, pagesz 64, sec_num :1, 8 65535 0 



bit map len[32] 0xe0 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 

[01-01 18:12:22 TUYA N][rcd_flash_app.c:701] maxlen 131072, pagesz 64, sec_num :1, 9 65535 0 



bit map len[32] 0xe0 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 

boot_reason : 0 

[01-01 18:12:22 TUYA N][tuya_devos_entry.c:1798] Last reset reason: 0

[01-01 18:12:22 TUYA N][tuya_devos_entry.c:1162] serial_no:38a5c945fbc6

[01-01 18:12:22 TUYA N][tuya_devos_entry.c:1193] gw_cntl.gw_wsm.stat:1

[01-01 18:12:22 TUYA N][tuya_devos_netcfg.c:1345] gw_cntl->gw_wsm.nc_tp:2

[01-01 18:12:22 TUYA N][tuya_devos_netcfg.c:1346] gw_cntl->gw_wsm.md:0

[01-01 18:12:22 TUYA N][tuya_devos_entry.c:1252] gw_cntl.gw_if.abi:1 input:1

[01-01 18:12:22 TUYA N][tuya_devos_entry.c:1254] gw_cntl.gw_if.tp:0, input:0

[01-01 18:12:22 TUYA E][rcd_flash_app.c:1271] __read_entry_with_key fail. -10114

[01-01 18:12:22 TUYA E][gw_kv_db.c:116] rcd_entry_kv_read fails lp_off_dev -10114

[01-01 18:12:22 TUYA N][tuya_bt_sdk.c:162] ty bt upd product:keym557nqw3p8p7m 1

[01-01 18:12:22 TUYA N][tuya_device.c:373] --> tuya_gw_srv_init_wf success

[01-01 18:12:22 TUYA N][tuya_device.c:377] --> tuya_iot_reg_get_wf_nw_stat_cb success.

[TOS_DBG]set_wifi_work_mode:3



[TOS_DBG]tuya_os_adapt_bt_stack_deinit



bt_main_task_del_in_task

[01-01 18:12:22 TUYA N][tuya_ble_api.c:482] Ble Disonnected

[01-01 18:12:22 TUYA N][tuya_ble_data_handler.c:64] ble reset sn

[01-01 18:12:22 TUYA N][tuya_ble_data_handler.c:78] ble clear pair rand

[01-01 18:12:22 TUYA N][tuya_ble_api.c:1461] ble set conn stat:2

[BT Mesh Provisioner] BT Stack deinitalized




LwIP_DHCP: dhcp stop.

[rtw coex]: pcoex is null!


Deinitializing WIFI ...


WIFI deinitialized


Initializing WIFI ...


WIFI initialized

[TOS_DBG]tuya_os_adapt_bt_stack_init:0x07






BT BUILD Date: 2023/12/11-15:18:12 


BT Reset...

>> Hello MeshProvision
physicer <<

>al efuse: has data hci_tp_phy_efuse[1]= 9e 




hci_tp_phy_efuse[0]=0,


bt_iqk_dump:    DUMP,


the IQK_xx  data is 0xe7,


the IQK_yy  data is 0x3fd,


the QDAC  data is 0x20,


the IDAC  data is 0x1f,


hci_read_rom_check: rom_version 0x0002, bt_hci_chip_id 0x0003



BT ADDRESS: 38:a5:c9:45:fb:c6




 WRITE  physical FLATK=tx_flatk=0 


Set baudrate to 921600




hci_tp_config:BT INIT success 7


Start upperStack

ms addr: 0x0000

>[TOS_DBG]bt_dev_state_evt init:1, adv:0, scan:0, cause:0x0



[TOS_DBG]ble mesh use rtl key

[TOS_DBG][BLE peripheral] GAP stack ready




[TOS_DBG]bt_dev_state_evt init:1, adv:0, scan:1, cause:0x0



[TOS_DBG]mesh_le_adv_start

mesh le_adv_start

[TOS_DBG]bt_dev_state_evt init:1, adv:0, scan:2, cause:0x0



[TOS_DBG]GAP scan start



[TOS_DBG]Start scan




[TOS_DBG]bt_dev_state_evt init:1, adv:0, scan:3, cause:0x0



[TOS_DBG]bt_dev_state_evt init:1, adv:0, scan:0, cause:0x0



[TOS_DBG]GAP scan stop



[BT_MESH] mesh_provisioner_cmd_thread(): mesh cmd thread enter !

[TOS_DBG]bt_dev_state_evt init:1, adv:0, scan:1, cause:0x0



[TOS_DBG]bt_dev_state_evt init:1, adv:0, scan:2, cause:0x0



[TOS_DBG]GAP scan start




wlan1: 1 DL RSVD page success! DLBcnCount:01, poll:00000001

[01-01 18:12:23 TUYA N][tuya_ble_api.c:436] update bound stat:0

[TOS_DBG]mesh_le_adv_start

mesh le_adv_start

[01-01 18:12:23 TUYA N][tuya_ble_api.c:724] ble adv && resp changed

[01-01 18:12:23 TUYA N][device-table.c:855] save table.

[01-01 18:12:23 TUYA N][tuya_device.c:299] __gw_wf_nw_stat_cb:2

[01-01 18:12:23 TUYA N][user_led.c:505] ******* gw wifi_stat:[2]

[01-01 18:12:25 TUYA N][z3_slabs.c:154] nodeEuiStr = 0c2a6ffffea1b01c.

[01-01 18:12:25 TUYA N][z3_slabs.c:155] nodeId = 0xfffe.

[01-01 18:12:25 TUYA N][z3_slabs.c:156] panId = 0xd63d.

[01-01 18:12:25 TUYA N][z3_slabs.c:157] channel = 0x19.

[01-01 18:12:25 TUYA N][z3_slabs.c:158] ver = 2.4.1.

[01-01 18:12:25 TUYA N][z3_slabs.c:159] netStatus = 0x00.

[01-01 18:12:25 TUYA N][z3_slabs.c:160] extendedPanId: d65aadd3ec760ab4

[01-01 18:12:25 TUYA N][z3_slabs.c:161] manufacturerId: 0x2020

[01-01 18:12:25 TUYA N][z3_slabs.c:167] netWorkKey: 9f fd bb 0a 8c 79 8f 6b 6f 6b aa 3c 4a 2f ba f1 



[01-01 18:12:27 TUYA N][z3_slabs.c:154] nodeEuiStr = 0c2a6ffffea1b01c.

[01-01 18:12:27 TUYA N][z3_slabs.c:155] nodeId = 0x0000.

[01-01 18:12:27 TUYA N][z3_slabs.c:156] panId = 0xe878.

[01-01 18:12:27 TUYA N][z3_slabs.c:157] channel = 0x14.

[01-01 18:12:27 TUYA N][z3_slabs.c:158] ver = 2.4.1.

[01-01 18:12:27 TUYA N][z3_slabs.c:159] netStatus = 0x02.

[01-01 18:12:27 TUYA N][z3_slabs.c:160] extendedPanId: 58ac56abe1f5ce67

[01-01 18:12:27 TUYA N][z3_slabs.c:161] manufacturerId: 0x2020

[01-01 18:12:27 TUYA N][z3_slabs.c:167] netWorkKey: 18 17 de da 5b 33 0f 3a de 77 60 25 1a 8a 65 4e 



18 17 de da 5b 33 0f 3a de 77 60 25 1a 8a 65 4e 


[01-01 18:12:29 TUYA N][device-table.c:757] get partition[TableSave]:0

[01-01 18:12:29 TUYA N][device-table.c:760] write devices1.txt

[01-01 18:12:29 TUYA E][uf_flash_file_app.c:363] uf_write err 1

[01-01 18:12:29 TUYA N][device-table.c:832] ufwrite table fail.

[01-01 18:12:37 TUYA N][tuya_gw_mgr.c:710] current gw_protocol_full_attr: 0x000000cb

[01-01 18:12:37 TUYA N][tuya_gw_beacon_mgmt.c:264] tuya_beacon_dev_mgmt_start success.

[01-01 18:12:37 TUYA E][tyua_gw_bt_comm_http.c:459] ret:-6

[01-01 18:12:37 TUYA E][subdev_sigmesh.c:1428] key is null.

[01-01 18:12:37 TUYA E][tuya_gw_mesh_mgmt.c:182] tuya_iot_sigmesh_get_net_info op_ret:-1

[01-01 18:12:37 TUYA N][tuya_gw_ble_mgmt.c:1365] bt dev join, permit:0 timeout:0,fp_fail_cnt:0

[01-01 18:12:37 TUYA N][user_app.c:214] ble server mgr init ok!

[01-01 18:12:37 TUYA N][tuya_gw_mgr.c:1014] current gw_cap_full_attr: 0x00000007

[01-01 18:12:37 TUYA N][tuya_device.c:420] [free mem:2067552 Bytes, 2067552 Bytes], dev_num:[0,0]

[01-01 18:12:37 TUYA N][tuya_device.c:405] device_init success.start app...

[01-01 18:12:37 TUYA E][tuya_gw_mesh_mgmt.c:724] get net info err:-1

[01-01 18:12:52 TUYA E][subdev_sigmesh.c:1428] key is null.

[01-01 18:12:52 TUYA E][tuya_gw_mesh_mgmt.c:182] tuya_iot_sigmesh_get_net_info op_ret:-1

[01-01 18:12:52 TUYA E][tuya_gw_mesh_mgmt.c:724] get net info err:-1

[01-01 18:13:07 TUYA E][subdev_sigmesh.c:1428] key is null.

[01-01 18:13:07 TUYA E][tuya_gw_mesh_mgmt.c:182] tuya_iot_sigmesh_get_net_info op_ret:-1

[01-01 18:13:07 TUYA E][tuya_gw_mesh_mgmt.c:724] get net info err:-1

[01-01 18:13:22 TUYA E][subdev_sigmesh.c:1428] key is null.

[01-01 18:13:22 TUYA E][tuya_gw_mesh_mgmt.c:182] tuya_iot_sigmesh_get_net_info op_ret:-1

[01-01 18:13:22 TUYA E][tuya_gw_mesh_mgmt.c:724] get net info err:-1

[01-01 18:13:30 TUYA N][tuya_device.c:420] [free mem:2093728 Bytes, 26176 Bytes], dev_num:[0,0]

[01-01 18:13:37 TUYA E][subdev_sigmesh.c:1428] key is null.

[01-01 18:13:37 TUYA E][tuya_gw_mesh_mgmt.c:182] tuya_iot_sigmesh_get_net_info op_ret:-1

[01-01 18:13:37 TUYA E][tuya_gw_mesh_mgmt.c:724] get net info err:-1

[01-01 18:13:52 TUYA E][subdev_sigmesh.c:1428] key is null.

[01-01 18:13:52 TUYA E][tuya_gw_mesh_mgmt.c:182] tuya_iot_sigmesh_get_net_info op_ret:-1

[01-01 18:13:52 TUYA E][tuya_gw_mesh_mgmt.c:724] get net info err:-1

[01-01 18:14:07 TUYA E][subdev_sigmesh.c:1428] key is null.

[01-01 18:14:07 TUYA E][tuya_gw_mesh_mgmt.c:182] tuya_iot_sigmesh_get_net_info op_ret:-1

[01-01 18:14:07 TUYA E][tuya_gw_mesh_mgmt.c:724] get net info err:-1

[01-01 18:14:22 TUYA E][subdev_sigmesh.c:1428] key is null.

[01-01 18:14:22 TUYA E][tuya_gw_mesh_mgmt.c:182] tuya_iot_sigmesh_get_net_info op_ret:-1

[01-01 18:14:22 TUYA E][tuya_gw_mesh_mgmt.c:724] get net info err:-1
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #217 21447232
    divadiow
    Level 34  
    interesting. did you capture your boot log too from WBRG1 @insmod?

    what is the relationship/similarities between CS and D families? Can flash from D be expected to boot at all on the WBRG1? Have you given any a go?

    Does this 4mb file do anything if flashed? Anything different to my result flashing to DN board? https://www.elektroda.com/rtvforum/topic4106646.html#21443892
  • #218 21447360
    p.kaczmarek2
    Moderator Smart Home  
    it worked with second attempt, it's flashing now, offset is strange?


    Screenshot of a terminal showing a flashing process with a device error related to setting flash status.

    Added after 5 [minutes]:



    Screenshot with error messages related to Flash memory writing.
    Helpful post? Buy me a coffee.
  • #219 21447390
    divadiow
    Level 34  
    I don't understand the RTL 0x08000000 = 0x0 thing

    But isn't the 8mb file just 4mb read twice, so 4mb is the full correct dump?
  • #221 21447393
    divadiow
    Level 34  
    I was also getting "error: Set Flash Status" when trying to write to RTL8720DN with rtltool so switched to official RTL AmebaD tool
  • #222 21447441
    p.kaczmarek2
    Moderator Smart Home  
    Code: text Expand Select all Copy to clipboard
    
python rtltool.py -p COM4 -b 100000 wf 0 ff1_8mb.bin
Connecting...
Erase Flash 2048 sectors, data from 0x00000000 to 0x00800000
Write Flash data 0x08000000 to 0x08800000 from file: ff1_8mb.bin
Flash block checksum retrieval error!

    Ok it seems I need to try other tool

    Added after 15 [minutes]:


    ImageTool_v2.3.2_AmebaD window with selected serial port COM4 and loading binary files.

    Added after 4 [minutes]:

    Code: text Expand Select all Copy to clipboard
    
COM4 is open successfully!
Uart download server has started...
All images are sent successfully!
COM4 is closed successfully!
COM4 is open successfully!
Uart download server has started...
Erase addr: 0x8000000, size:8192KB
IMG1 image is being sent...
IMG1 image has been sent successfully!
All images are sent successfully!
COM4 is closed successfully!


    Added after 57 [seconds]:

    divadiow wrote:

    Does this 4mb file do anything if flashed? Anything different to my result flashing to DN board? https://www.elektroda.com/rtvforum/topic4106646.html#21443892

    Code: text Expand Select all Copy to clipboard
    
#calibration_ok:[2:23:13] 
                                                     
[MEM DBG] heap init-------size:256000 addr:0x1003a740---------
                 
#Invalid image, reboot
                                       
                
#calibration_ok:[2:23:13] 
                                                     
[MEM DBG] heap init-------size:256000 addr:0x1003a740---------
                 
#Invalid image, reboot
                                       
                
#calibration_ok:[2:23:13] 
                                                     
[MEM DBG] heap init-------size:256000 addr:0x1003a740---------
                 
#Invalid image, reboot
                                       
                
#calibration_ok:[2:23:13] 
                                                     
[MEM DBG] heap init-------size:256000 addr:0x1003a740---------
                 
#Invalid image, reboot
                                       
                
#calibration_ok:[2:23:13] 
                                                     
[MEM DBG] heap init-------size:256000 addr:0x1003a740---------
                 
#Invalid image, reboot
   
    Helpful post? Buy me a coffee.
  • #223 21447491
    divadiow
    Level 34  
    Oh well. Same experience. Does BW16 backup boot?
  • #224 21447572
    groove6j
    Level 8  
    p.kaczmarek2 wrote:
    #Invalid image, reboot

    Maybe my dump is bad? Or is it more likely another device?
    I can take another dump with another UART adapter as soon as it arrives.
  • #225 21447641
    divadiow
    Level 34  
    >>21447572

    Not really sure tbh. I guess more dumps would be something to try. If you have a CH341A you could dump off that flash chip directly.
  • #226 21447645
    insmod
    Level 22  
    >>21447232
    My boot log is at >>21421289
    Started porting today, but those compilation times... ugh.
    Everything builds using only one job, and combine that with building using wsl2 on ntfs...
  • #227 21447651
    divadiow
    Level 34  
    insmod wrote:
    My boot log is at >>21421289

    ah, sorry. cheers!

    Added after 6 [minutes]:

    insmod wrote:
    but those compilation times... ugh

    how long does it take to build?
  • Helpful post
    #228 21447667
    insmod
    Level 22  
    >>21447651 I have yet to measure full build, but one file is taking about 5-15 seconds. And that is on Zen4

    Added after 4 [hours] 1 [minutes]:

    Basics are done, i can at least get it to boot. Decided to do it all on wbrg1, not bw16.
    Code: text Expand Select all Copy to clipboard
    #[MODULE_BOOT-LEVEL_INFO]:IMG1 ENTER ROMSUB:2
[MODULE_BOOT-LEVEL_INFO]:OTA1 USE
[MODULE_BOOT-LEVEL_INFO]:IMG2 DATA[0xc014750:9328:0x83000]
[MODULE_BOOT-LEVEL_INFO]:IMG2 SIGN[RTKWin(8300c)]
[MODULE_BOOT-LEVEL_INFO]:IMG2 ENTRY[0x83000:0xc002835]
[MODULE_BOOT-LEVEL_INFO]:KM0 BOOT_IMG2 BOOT REASON: 0 
Flash ID:68, 40, 17
read_mode:2
calibration_ok:[2:19:11] 
FLASH CALIB[NEW OK]
RRAM: c0080 176B 
[MODULE_BOOT-LEVEL_INFO]:IMG1 ENTER MSP:[1007fffc]
[MODULE_BOOT-LEVEL_INFO]:IMG2 DATA[0xe090c90:98096:0x10005000]
[MODULE_BOOT-LEVEL_INFO]:IMG2 SIGN[RTKWin(1000500c)]
[MODULE_BOOT-LEVEL_INFO]:IMG2 ENTRY[0x10005000:0xe0271f1]
[MODULE_BOOT-LEVEL_INFO]:Start NonSecure @ 0xe0271f0 ...
[MODULE_BOOT-LEVEL_INFO]:KM4 BOOT REASON: 0 
#interface 0 is initialized
interface 1 is initialized

Initializing WIFI ...Entering initLog()...
Commands registered!
initLog() done!
Warning: Sector header check failed. Format this sector (0x001bInfo:MAIN:Main_Init_Before_Delay
0000).
Warning: Sector header check failed. Format this sector (0x001b1000).
Warning: Sector header check failed. Format this sector (0x001b2000).
Warning: Sector header check failed. Format this sector (0x001b3000).
Warning: Sector header check failed. Format this sector (0x001b4000).
Warning: Sector header check failed. Format this sector (0x001b5000).
Warning: Sector header check failed. Format this sector (0x001b6000).
Warning: Sector header check failed. Format this sector (0x001b7000).
Warning: Sector header check failed. Format this sector (0x001b8000).
Warning: Sector header check failed. Format this sector (0x001b9000).
Warning: Sector header check failed. Format this sector (0x001ba000).
Warning: Sector header check failed. Format this sector (0x001bb000).
Warning: Sector header check failed. Format this sector (0x001bc000).
Warning: Sector header check failed. Format this sector (0x001bd000).
Warning: Sector header check failed. Format this sector (0x001be000).
Warning: Sector header check failed. Format this sector (0x0
WIFI initialized

init_thread(58), Available heap 0x2ffa001bf000).
Warning: Sector header check failed. Format this sector (0x001c0000).
Warning: Sector header check failed. Format this sector (0x001c1000).
Warning: Sector header check failed. Format this sector (0x001c2000).
Warning: Sector header check failed. Format this sector (0x001c3000).
Warning: Sector header check failed. Format this sector (0x001c4000).
Warning: Sector header check failed. Format this sector (0x001c5000).
Warning: Sector header check failed. Format this sector (0x001c6000).
Warning: Sector header check failed. Format this sector (0x001c7000).
Warning: Sector header check failed. Format this sector (0x001c8000).
Warning: Sector header check failed. Format this sector (0x001c9000).
Warning: Sector header check failed. Format this sector (0x001ca000).
Warning: Sector header check failed. Format this sector (0x001cb000).
Warning: Sector header check failed. Format this sector (0x001cc000).
Warning: Sector header check failed. Format this sector (0x001cd000).
Warning: Sector header check failed. Format this sector (0x001ce000).
Warning: Sector header check failed. Format this sector (0x001cf000).
Warning: Sector header check failed. Format this sector (0x001d0000).
Warning: Sector header check failed. Format this sector (0x001d1000).
Warning: Sector header check failed. Format this sector (0x001d2000).
Warning: Sector header check failed. Format this sector (0x001d3000).
Warning: Sector header check failed. Format this sector (0x001d4000).
Warning: Sector header check failed. Format this sector (0x001d5000).
Warning: Sector header check failed. Format this sector (0x001d6000).
Warning: Sector header check failed. Format this sector (0x001d7000).
Warning: Sector header check failed. Format this sector (0x001d8000).
Warning: Sector header check failed. Format this sector (0x001d9000).
Warning: Sector header check failed. Format this sector (0x001da000).
Warning: Sector header check failed. Format this sector (0x001db000).
Warning: Sector header check failed. Format this sector (0x001dc000).
Warning: Sector header check failed. Format this sector (0x001dd000).
Warning: Sector header check failed. Format this sector (0x001de000).
Warning: Sector header check failed. Format this sector (0x001df000).
Warning: Sector header check failed. Format this sector (0x001e0000).
Warning: Sector header check failed. Format this sector (0x001e1000).
Warning: Sector header check failed. Format this sector (0x001e2000).
Warning: Sector header check failed. Format this sector (0x001e3000).
Warning: Sector header check failed. Format this sector (0x001e4000).
Warning: Sector header check failed. Format this sector (0x001e5000).
Warning: Sector header check failed. Format this sector (0x001e6000).
Warning: Sector header check failed. Format this sector (0x001e7000).
Warning: Sector header check failed. Format this sector (0x001e8000).
Warning: Sector header check failed. Format this sector (0x001e9000).
Warning: Sector header check failed. Format this sector (0x001ea000).
Warning: Sector header check failed. Format this sector (0x001eb000).
Warning: Sector header check failed. Format this sector (0x001ec000).
Warning: Sector header check failed. Format this sector (0x001ed000).
Warning: Sector header check failed. Format this sector (0x001ee000).
Warning: Sector header check failed. Format this sector (0x001ef000).
Warning: Sector header check failed. Format this sector (0x001f0000).
Warning: Sector header check failed. Format this sector (0x001f1000).
Warning: Sector header check failed. Format this sector (0x001f2000).
Warning: Sector header check failed. Format this sector (0x001f3000).
Warning: Sector header check failed. Format this sector (0x001f4000).
Warning: Sector header check failed. Format this sector (0x001f5000).
Warning: Sector header check failed. Format this sector (0x001f6000).
Warning: Sector header check failed. Format this sector (0x001f7000).
Warning: Sector header check failed. Format this sector (0x001f8000).
Warning: Sector header check failed. Format this sector (0x001f9000).
Warning: Sector header check failed. Format this sector (0x001fa000).
Warning: Sector header check failed. Format this sector (0x001fb000).
Warning: Sector header check failed. Format this sector (0x001fc000).
Warning: Sector header check failed. Format this sector (0x001fd000).
Warning: Sector header check failed. Format this sector (0x001fe000).
Warning: Sector header check failed. Format this sector (0x001ff000).
Warning: All sector header check failed. Set it to default.
EasyFlash V4.1.0 is initialize success.
You can get the latest version on https://github.com/armink/EasyFlash .
Warn:CFG:CFG_InitAndLoad: Config crc or ident mismatch. Default config will be loaded.
Info:CFG:CFG_SetDefaultLEDCorrectionTab
Main_Init_Before_Delay done

Main_Init_Delay

Main_Init_Delay done
Main_Onle: setting defaults
Error:CMD:lfs is absent
Info:GEN:PIN_SetupPins pins have been set up.
Info:MAIN:Main_Init_Before_Delay EverySecond
done
Info:MAIN:Main_Init_Delay
Info:MAIN:Main_Init_Delay done
Info:MAIN:Main_Init_After_Delay
Info:MAIN:Using SSID []
Info:MAIN:Using Pass []
Info:HTTP:TCP server listening
Info:MQTT:MQTT_RegisterCallback called for bT rtl8720d00000000/ subT rtl8720d00000000/+/set
Info:MQTT:MQTT_RegisterCallback called for bT obks/ subT obks/+/set
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/rtl8720d00000000/ subT cmnd/rtl8720d00000000/+
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/obks/ subT cmnd/obks/+
Info:MQTT:MQTT_RegisterCallback called for bT rtl8720d00000000/ subT rtl8720d00000000/+/get
Info:CMD:CMD_StartScript: started @startup at the beginning
Error:CMD:LFS_ReadFile: lfs is absent
Info:CMD:CMD_StartScript: failed to get file autoexec.bat
Info:MAIN:Main_Init_After_Delay done
Main_OnEverySecond
Main_OnEverySecond


    Added after 1 [hours] 30 [minutes]:

    Is there a limit on maximum pins displayed in cfg_pins? i set up pins PA0-PA31 and PB0-PB31, but only PA0-PA28 are displayed.
    Screenshot of a user interface with PA25-PA28 options and a save button.
  • #229 21448209
    p.kaczmarek2
    Moderator Smart Home  
    32?
    Screenshot from Microsoft Visual Studio showing a code snippet in C language.
    There is also PLATFORM_GPIO_MAX...
    Helpful post? Buy me a coffee.
  • #230 21448216
    insmod
    Level 22  
    >>21448209 My bad, i forgot to define PLATFORM_GPIO_MAX

    Added after 1 [hours] 32 [minutes]:

    Beta, no ota implemented
    https://github.com/NonPIayerCharacter/OpenBK7...actions/runs/13436706995/artifacts/2623708313
    flash binary at 0x08000000

    Added after 12 [minutes]:

    Currently untested functions: uart, gpio interrupts, i2c sensors, ds18b20, dht11
    Works: wifi, mqtt, gpio input and output
  • #232 21448421
    p.kaczmarek2
    Moderator Smart Home  
    Excellent work!
    Screenshot of ImageTool v2.3.2 program with process for AmebaD chip.
    List of available Wi-Fi networks with a visible network named OpenRTL8720D_C945FC6.
    First page open at 192.168.4.1:
    OpenRTL8720D user interface with configuration and restart options.
    Page loads quickly, but not always fully.
    Table with information about a network client with the assigned IP address 192.168.0.228.
    Let me prepare something for testing...

    Added after 8 [minutes]:

    Wait a sec, where is save button:
    Startup command interface for OpenRTL8720D device.
    Code: text Expand Select all Copy to clipboard
    
setChannelType 1 Temperature
setChannelType 2 Humidity
setChannelType 3 Motion


again:
setChannel 1 23
setChannel 2 58
setChannel 3 0
publishAll
delay_s 10
goto again


    OpenRTL8720D configuration page with startup command console.

    Added after 4 [minutes]:

    No Humidity/Temperature/etc in HA?
    Screenshot of the device information panel with sections Device info, Diagnostic, and Logbook.
    Is
    Code: C / C++
    Log in, to see the code

    present in obk_config.h ?
    Helpful post? Buy me a coffee.
  • #233 21448455
    insmod
    Level 22  
    >>21448421 No, it's not enabled on RTL8720D, RTL8710B, RTL8710A, TR6260, ESP-IDF, LN882H, BL602 and W800/W600
  • #234 21448465
    p.kaczmarek2
    Moderator Smart Home  
    We may need to go through flash sizes on each platform and consider what we can realistically enable... or add compile-time alarms so we won't release a "broken" (too large) OTA file. I remember something happening like that on BL602, luckily, the fault was on OTA file and didn't break anything on current firmware size.

    I'm testing DS18B20, but I am not sure about my connections yet.
    Code: text Expand Select all Copy to clipboard
    
Error:SENSOR:DS1820[25] - Reset failed

    Wait, let me connect LED first

    Added after 8 [minutes]:

    Ah PA25 is red LED:
    Circuit board with two electronic modules and a lit red LED.
    This may be interfering with DS18B20, let's check other pin

    PB22 (next pin up) is the second LED
    Helpful post? Buy me a coffee.
  • #235 21448524
    insmod
    Level 22  
    While my board looks different, pins are the same. Button is on PB23.
    Any form, where SUBMIT_AND_END_FORM is used aren't working.
    Doesn't work on RTL8710B either.

    Added after 11 [minutes]:

    I changed it to const and it is now working
    Updated https://github.com/NonPIayerCharacter/OpenBK7...actions/runs/13439220529/artifacts/2624610380

    top dd performance
    Code: text Expand Select all Copy to clipboard
    806912+0 records in
806912+0 records out
806912 bytes (807 kB, 788 KiB) copied, 321.01 s, 2.5 kB/s
  • #236 21448804
    p.kaczmarek2
    Moderator Smart Home  
    Very interesting, why would the lack of const break usage of this string?
    Helpful post? Buy me a coffee.
  • #237 21449354
    insmod
    Level 22  
    Don't know.
    New build, this time with ota https://github.com/NonPIayerCharacter/OpenBK7231T_App/actions/runs/13451371991
    Updated all but bk7231t workflow to use ubuntu 22.04, since 20.04 "will be fully unsupported by 2025-04-01".
    bk7231t on 22.04 fails when using otafix. Don't know why, because on my 22.04 wsl2 and 24.04 server it works. Maybe need some additional package?
    Also tried 24.04, but several builds fail, most likely because of some incompatible gcc/newlib changes. But since 22.04 will be supported for some time, i didn't try to fix it.

    Now need to implement uart hw flow control in obk, since coordinators are mostly using it.
  • #238 21449607
    divadiow
    Level 34  
    initial flash to BW16E/DN after full erase
    ImageTool v2.3.2.3 window with a list of files for download.
    First boot, join AP and then join test wifi as a client
    Code: Text
    Log in, to see the code

    doesn't like something about mac
  • #239 21449615
    divadiow
    Level 34  
    submit button OK + FW#
    OpenRTL8720D configuration screen with buttons: Config, Restart, Launch Web Application, About. OpenRTL8720D command tool interface with command input field

    Added after 4 [minutes]:

    OTA FW1->FW2->FW1 ✅
    Code: Text
    Log in, to see the code
  • #240 21449647
    insmod
    Level 22  
    MAC address is taken from efuse, same address as in AmebaZ. But, it seems bw16 lacks it. Since i see you have connected it to router, does it display a proper mac, or is it FF too?
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around the compatibility of RTL8720DN, RTL8710B, and RTL8710BX with OpenBeken firmware. Users share their experiences with various modules, including BW15 and WBR3, and discuss issues related to memory management, Wi-Fi connectivity, and flashing procedures. Several users report successful flashing and functionality tests, while others encounter problems with memory leaks and device reboots. The conversation also touches on the use of different tools for flashing, such as ltchiptool and rtltool, and the need for proper firmware versions to ensure compatibility. Additionally, there are mentions of specific features like MQTT support, GPIO control, and OTA updates.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT