logo elektroda
logo elektroda
X
logo elektroda

Converting WRG1 and TYZS3 Zigbee Gateways to OpenBeken

insmod 5169 25

TL;DR

  • Converts WRG1 and TYZS3 Zigbee gateways, including ZXGWZ-04, JMWZG1, and TYZG1 variants, to OpenBeken.
  • Flashing uses a J-Link adapter over SWD, then OpenRTL8710A is written to WRG1 and a TYZS3 .gbl is flashed in Simplicity Commander.
  • The WRG1 backup is a 4MB rtl8711am_dump.bin, and OpenBeken UART logs use 38400 baud on LOG-TX/L-TX and LOG-RX/L-RX.
  • A successful WRG1 flash boots OpenBeken, creates a new access point, and lets you configure it at http://192.168.4.1.
  • UART flashing is not supported, and TYZS3 firmware must match swflow or rtscts by changing the startup uarttcp line.
Generated by the language model.
ADVERTISEMENT
📢 Listen (AI):
  • Converting WRG1 and TYZS3 Zigbee Gateways to OpenBeken
    This guide will show you how to convert WRG1 and TYZS3 Zigbee gateways to OpenBeken.

    There are several known variants using this combination.
    1. ZXGWZ-04 (internal board is named TYGWZW1), seen here
    2. JMWZG1 (JMZ1-V1.2 or JMZ1-V1.3), seen here
    3. TYZG1 (JZZWD-TY1.1), seen here

    If you have a WBRG1 module instead of WRG1, see here

    Pictures
    Converting WRG1 and TYZS3 Zigbee Gateways to OpenBeken Converting WRG1 and TYZS3 Zigbee Gateways to OpenBeken

    Be warned, that they can't be flashed via UART, you would need to buy a J-Link adapter
    Chinese J-Link OB clone for $2 would work too
    Converting WRG1 and TYZS3 Zigbee Gateways to OpenBeken

    If you previously haven't used J-Link, you will need to install drivers.
    From attached rtl8711am.rar install JLink_Windows_V632g.exe

    When you've installed drivers and connected J-Link, check if you have "J-Link driver" in device manager under USB controllers, and not an unknown device.

    Connect your J-Link to SWD port of WRG1 module (SWCLK_WIFI and SWD_WIFI)
    First, you need to take a backup.
    Execute RTL8711AM_ReadFlash.bat
    It would create rtl8711am_dump.bin. That is your 4MB backup of RTL8711AM internal flash.

    Open RTL00Flasher (ignore Flash ID warning if it shows)
    Converting WRG1 and TYZS3 Zigbee Gateways to OpenBeken
    Download latest OpenRTL8710A JTAG firmware from https://github.com/openshwprojects/OpenBK7231T_App/releases
    Latest at the moment of writing this post: https://github.com/openshwprojects/OpenBK7231...s/download/1.18.135/OpenRTL8710A_1.18.135.bin
    Open page "Auto", where button "Write Flash" is located. Check "Image1" and "Image2,3". Ensure that checkboxes "System data" and "Calibration data" are not set. That way we will preserve original MAC address and WiFi calibration.
    Then press "Write Flash" and select previously downloaded firmware. Flashing will begin automatically.

    Once flashed, connect UART to LOG-TX/L-TX and LOG-RX/L-RX, set baud rate to 38400.
    Power-cycle the device.
    If everything gone right, you will see OpenBeken boot log.
    <RTL8195A>=========================================================
    
    ROM Version: 0.3
    
    Build ToolChain Version: gcc version 4.8.3 (Realtek ASDK-4.8.3p1 Build 2003) 
    
    =========================================================
    Check boot type form eFuse
    SPI Initial
    Image1 length: 0x53a8, Image Addr: 0x10000bc8
    Image1 Validate OK, Going jump to Image1
    
    BOOT from Flash:YES
    
    ===== Enter Image 1 ====
    SDR Controller Init
    
    OTA Im INVALID
    
    load NEW fw 0
    Flash Im2:Addr 0xb000, Len 223448, Load to SRAM 0x10006000
    Im3 length: 0x7ca00, Im3 Addr: 0x30000000
    Im2 Sign: RTKWin, InfaStart @ 0x10006189 
    ===== Enter Image 2 ====
    interface 0 is initialized
    interface 1 is initialized
    
    Initializing WIFI ...
    WIFI initialized
    
    init_thread(53), Available heap 0x23a78OpenRTL8710A, version dev_20250714_133008
    Entering initLog()...
    Commands registered!
    initLog() done!
    Info:MAIN:Main_Init_Before_Delay
    ...
    ...
    

    Connect to newly-created access point and via http://192.168.4.1 configure to your needs.
    OBK pin setup:
    PB2 - Button
    PC0 - Blue led
    PC1 - Red led


    Time to flash TYZS3.

    Connect your J-Link to SWD port of TYZS3 module (SWCLK and SWD on the right side of the module)
    First, of course, is taking a backup.
    Execute TYZS3_ReadFlash.bat
    It would create tyzs3_dump.hex
    Open Simplicity Commander and select your J-Link adapter
    Screenshot of Simplicity Commander with the “Select Kit...” menu open and a USB J-Link adapter selected.
    Open Flash category, click "Browse..." and select any of included in rtl8711am.rar .gbl files
    1. tyzs3_zigbee_ncp_7.4.5.0_115200_swflow_buf64.gbl - previously tested by me for several months. Working.
    2. tyzs3_zigbee_ncp_7.5.0.0_115200_swflow_buf64.gbl - only confirmed that it works and connects to Zigbee2MQTT, nothing else.
    3. tyzs3_zigbee_ncp_7.5.0.0_115200_swflow_nobuf.gbl - not tested. Main difference is default RX buffer. In 7.4.x there was some bug, so an increased buffer was required. Unknown if it was fixed in 7.5.0
    4. tyzs3_zigbee_ncp_7.5.0.0_115200_rtscts_buf64.gbl - confirmed that it works and connects to Zigbee2MQTT, but no true testing was done. Comes with hardware flow offloading. Should be the best variant.
    5. tyzs3_openthread_rcp_2.4.6.0_230400_swflow_buf64.gbl - OpenThread firmware with software flow control. Not tested.
    6. tyzs3_openthread_rcp_2.4.6.0_230400_rtscts_buf64.gbl - OpenThread firmware with hardware flow control. Not tested.

    When you've selected firmware that you chose, click "Flash" and wait until it is done.
    Disconnect J-Link adapter and power it via USB.

    Autoexec/startup command for OpenBeken:
    startdriver uarttcp 115200 512 1 1
    SetChannelLabel 1 "Bridge Connection"
    SetChannelVisible 1 0
    SetChannelType 1 OpenClosed_Inv

    Now, depending on what firmware you flashed to TYZS3, edit first line and replace in first line last symbol with 0 if you flashed swflow firmware. Keep 1 if you flashed rtscts firmware.

    When adding this gateway as an adapter to either ZHA or Zigbee2MQTT, use this string:
    tcp://<OBK_IP>:8888

    Replace <OBK_IP> with whatever IP was set up to your device by DHCP or static IP if you configured it.
    Attachments:
    • Zigbee Gateway_Tuya Smart_Docs Center.pdf (317.38 KB) You must be logged in to download this attachment.
    • rtl8711am.rar (65.41 MB) You must be logged in to download this attachment.

    Cool? Ranking DIY
    About Author
    insmod
    Level 31  
    Offline 
    insmod wrote 1346 posts with rating 423, helped 159 times. Been with us since 2024 year.
  • ADVERTISEMENT
  • #2 21607779
    divadiow
    Level 38  
    are these the same across the 3 gateway variations and what is the template assignment in json? I don't have RTL-AM to quickly see what pins they are

    insmod wrote:
    OBK pin setup:
    PB2 - Button
    PC0 - Blue led
    PC1 - Red led
  • #3 21607790
    insmod
    Level 31  
    >>21607779
    Probably yes, since they're all based on the same template.
    Likely the same with WBRG1 gateways.
  • #5 21607820
    insmod
    Level 31  
    I use blue led for wifi, and red for zigbee
    So 9 is WifiLED. 10 remains as it is, and 7 should use different channel.
  • #6 21608001
    p.kaczmarek2
    Moderator Smart Home
    Very interesting, I didn't look into Zigbee gateways yet. Still, I have a question - how exactly this traffic going through gateway look like? That going through uarttcp? Is it JSON?

    I am curious how reasonable would it be to let OBK control Zigbee directly, not just act like TCP to UART gateway.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #8 21636423
    svetlinp
    Level 8  
    How to restore original firmware from 4 MB rtl8711am_dump.bin ?
  • #9 21636458
    insmod
    Level 31  
    >>21636423
    First try to do it via RTL00Flasher, select everything and then write flash.
  • #10 21636781
    svetlinp
    Level 8  
    After restoring device, it's not booting correctly. I restored TYZS3_dump.hex to TYZS3. This is the log file for RTL8710 booting. I cannot understand where the problem is: is it the RTL or the Zigbee module?
    =========================================================
    
    ROM Version: 0.3
    
    Build ToolChain Version: gcc version 4.8.3 (Realtek ASDK-4.8.3p1 Build 2003)
    
    =========================================================
    Check boot type form eFuse
    SPI Initial
    Image1 length: 0x53a8, Image Addr: 0x10000bc8
    Image1 Validate OK, Going jump to Image1
    
    BOOT from Flash:YES
    
    ===== Enter Image 1 ====
    SDR Controller Init
    
    OTA Im INVALID
    
    load OLD fw 0
    Flash Im2:Addr 0xb000, Len 270024, Load to SRAM 0x10006000
    Im3 length: 0x89200, Im3 Addr: 0x30000000
    Im2 Sign: RTKWin, InfaStart @ 0x10006189
    ===== Enter Image 2 ====
    interface 0 is initialized
    interface 1 is initialized
    
    Initializing WIFI ...
    WIFI initialized
    
    [01-01 18:12:15 TUYA Info][mqc_app.c:337] mqc app init ...
    [01-01 18:12:15 TUYA Info][uni_thread.c:205] thread_create name:sys_timer,stackDepth:4096,totalstackDepth:4096,priority:5
    [01-01 18:12:15 TUYA Info][uni_thread.c:205] thread_create name:cmmod,stackDepth:4096,totalstackDepth:8192,priority:4
    [01-01 18:12:15 TUYA Debug][mqc_app.c:148] mq_pro:5 cnt:1
    [01-01 18:12:15 TUYA Debug][mqc_app.c:148] mq_pro:31 cnt:2
    [01-01 18:12:15 TUYA Err][log_seq.c:850] logseq empty
    [01-01 18:12:15 TUYA Debug][svc_online_log.c:293] svc online log init success
    [01-01 18:12:15 TUYA Info][uni_thread.c:205] thread_create name:wk_th-0,stackDepth:5120,totalstackDepth:13312,priority:3
    [01-01 18:12:15 TUYA Err][tuya_ws_db.c:324] kvs_read fails gw_bi -1
    [01-01 18:12:15 TUYA Debug][ws_db_gw.c:141] gw base read finish:-18
    [01-01 18:12:15 TUYA Debug][tuya_bt_sdk.c:84] ty bt cmmod regist ok:1
    [01-01 18:12:15 TUYA Debug][tuya_ble_api.c:105] upd adv para, send conn_req beacon.
    [01-01 18:12:15 TUYA Notice][tuya_ble_api.c:397] ble sdk re_inited
    [01-01 18:12:15 TUYA Notice][tuya_bt_sdk.c:125] ty bt sdk init finish
    [01-01 18:12:15 TUYA Debug][group_scene_serve.c:2442] start group scene serve
    [01-01 18:12:15 TUYA Debug][group_scene_serve.c:744] =====__group_scene_save_init=====
    [01-01 18:12:15 TUYA Debug][group_scene_serve.c:781] group scene flag file: grp_sce_flag_file.
    [01-01 18:12:15 TUYA Debug][group_scene_serve.c:782] group scene file: grp_sce_save_file.
    [01-01 18:12:15 TUYA Debug][group_scene_serve.c:783] group scene back file: grp_sce_save_bak_file.
    [01-01 18:12:15 TUYA Err][group_scene_serve.c:719] read grp_sce_list err. -1
    [01-01 18:12:15 TUYA Debug][group_scene_serve.c:811] No old group scene flag file.
    [01-01 18:12:15 TUYA Info][uni_thread.c:205] thread_create name:grp_sce,stackDepth:2048,totalstackDepth:15360,priority:3
    [01-01 18:12:15 TUYA Debug][group_scene_serve.c:2474] end group scene serve
    [01-01 18:12:15 TUYA Debug][tuya_device.c:781] < TUYA IOT SDK V:1.0.2 BS:40.00_PT:2.2_LAN:3.3_CAD:1.0.3_CD:1.0.0 >
    < BUILD AT:2020_12_03_21_29_00 BY embed FOR ty_iot_wr_wf_bt_sdk_rtos AT rtl8711am_ameba >
    IOT DEFS < WIFI_GW:1 DEBUG:1 KV_FILE:0 SHUTDOWN_MODE:0 LITTLE_END:1 TLS_MODE:2 ENABLE_LOCAL_LINKAGE:1 ENABLE_CLOUD_OPERATION:0 ENABLE_SUBDEVICE:1 ENABLE_ENGINEER_TO_NORMAL:0 OPERATING_SYSTEM:2 ENABLE_SYS_RPC:0 TY_SECURITY_CHIP:0 RELIABLE_TRANSFER:1 ENABLE_LAN_ENCRYPTION:1 ENABLE_LAN_LINKAGE:1 ENABLE_LAN_LINKAGE_MASTER:0 ENABLE_LAN_DEV:1 ENABLE_LAN_DEV_MASTER:0 >
    
    [01-01 18:12:15 TUYA Debug][tuya_device.c:782] rtlam_gw_external_common_4M_iot_config_ty:1.2.8
    [01-01 18:12:15 TUYA Notice][simple_flash.c:408] key_addr: 0x2ff000   block_sz 4096
    [01-01 18:12:15 TUYA Err][simple_flash.c:428] key data is not matched magic(0x3a2d3e45),crc32(0xe2d8782c)
    [01-01 18:12:15 TUYA Err][simple_flash.c:442] flash is encrypted or empty
    [01-01 18:12:15 TUYA Err][simple_flash_app.c:286] create_flash_hand_and_init err 10
    [01-01 18:12:15 TUYA Err][tuya_ws_db.c:452] db init fails -1
    [01-01 18:12:15 TUYA Err][tuya_iot_com_api.c:357] db init fails -1
    [01-01 18:12:15 TUYA Info][uni_thread.c:205] thread_create name:mf_test,stackDepth:5120,totalstackDepth:20480,priority:4
    uart_dev_init:9600
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    uart_dev_deinit
    [01-01 18:12:16 TUYA Notice][tuya_main.c:299] mf_init succ
    [01-01 18:12:16 TUYA Err][tuya_ws_db.c:324] kvs_read fails gw_bi -1
    [01-01 18:12:16 TUYA Err][gw_intf.c:8890] base read err
    [01-01 18:12:16 TUYA Err][tuya_device.c:800]  app_init tuya_iot_support_home_security_set err:-18
    [01-01 18:12:16 TUYA Notice][tuya_device.c:676] device_init
    [01-01 18:12:16 TUYA Info][uni_thread.c:205] thread_create name:ty_uart_task,stackDepth:5120,totalstackDepth:25600,priority:4
    [01-01 18:12:16 TUYA Notice][weather_sever.c:430] ty_uart_public_weather_component_version:1.0.0
    [01-01 18:12:16 TUYA Notice][tuya_app_gw.c:695] max num:128,sig num:32
    [01-01 18:12:16 TUYA Notice][tuya_gw_baud_cfg.c:166] query baud:115200
    uart_dev_init:115200
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    uart_dev_deinit
    [01-01 18:12:18 TUYA Notice][tuya_gw_baud_cfg.c:166] query baud:9600
    uart_dev_init:9600
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    uart_dev_deinit
    [01-01 18:12:20 TUYA Notice][tuya_gw_baud_cfg.c:166] query baud:115200
    uart_dev_init:115200
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    uart_dev_deinit
    [01-01 18:12:22 TUYA Notice][tuya_gw_baud_cfg.c:166] query baud:9600
    uart_dev_init:9600
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    uart_dev_deinit
    [01-01 18:12:24 TUYA Notice][tuya_gw_baud_cfg.c:166] query baud:115200
    uart_dev_init:115200
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    tyzs3_dump.hexuart_dev_deinit
    [01-01 18:12:26 TUYA Notice][tuya_gw_baud_cfg.c:166] query baud:9600
    uart_dev_init:9600
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    tyzs3_dump.hextyzs3_dump.hexuart_dev_deinit
    [01-01 18:12:28 TUYA Notice][tuya_gw_baud_cfg.c:166] query baud:115200
    uart_dev_init:115200
    RTL8195A[HAL]: ISR 8 had been allocated!!!
  • #11 21637042
    insmod
    Level 31  
    >>21636781
    Zigbee.
    Though why tyzs3_dump.hex shows up in log several times?
  • ADVERTISEMENT
  • #12 21637256
    svetlinp
    Level 8  
    Thank you for your support.
    The mistake was made when I reconnected the JTAG from the RTL8710 to the TYZS3. The positions of power and ground are opposite, so I connected the power of the JTAG to the GND of the TYZS3 and the GND of the JTAG to the 3.3V of the TYZS3. The result was expected... the power supply chip of my JTAG has to be replaced (5V -> 3.3V). But there may be more damage to the TYZS3. I don't know if it's a capacitor, a resistor, or the chip itself. The Commander does not show any suspicious output during the flash of the EFR32MG13P732F512GM48. I want to build a Zigbee gateway that is not connected to the cloud. Can I use this platform (RTL8710A) to build this gateway, or do I have to start from the beginning and buy a new device for cloud-free use? What can I use for the TYZS3 replacement on this platform, or what device is better for this purpose (cloud-free - works without Tuya or Smart Home or other services)?
    Development setup with RTL8710A, TYZS3 and Arduino Mega connected via jumper wires.
    OpenRTL8710A control panel showing MQTT status and Wi-Fi connection details
  • #13 21637265
    insmod
    Level 31  
    >>21637256
    Well, you can repair JTAG and check if TYZS3 is alive.
    But since WRG1 is alive, TYZS3 is probably too.
    This one can be converted to be free from cloud. I've tested Zigbee2MQTT and Home Assistant ZHA, they both worked well enough. Though for WIFI+EFR32 Zigbee2MQTT is better, since they've rewrote their EZSP protocol implementation, and it is more stable.
    If you decide to buy a new device, current Tuya ones are like in https://www.elektroda.com/rtvforum/topic4127578.html
    Alternative is Ewelink. Those can also be used as bluetooth proxy. See https://www.elektroda.com/rtvforum/topic4099946.html
  • #14 21657359
    hazilo
    Level 2  
    Hi there,
    I joined the forum for this device as I have two lying around to work with.
    I have backed up the original rom, and then I flashed with RTL00. Now when I power it on it never gets to openbeken, instead here's what I get from the log uart:

    
    =========================================================
    
    ROM Version: 0.3
    
    Build ToolChain Version: gcc version 4.8.3 (Realtek ASDK-4.8.3p1 Build 2003)
    
    =========================================================
    Check boot type form eFuse
    SPI Initial
    Image1 length: 0x41fc, Image Addr: 0x10000bc8
    Image1 Validate OK, Going jump to Image1
    
    BOOT from Flash:YES
    
    ===== Enter Image 1 ====
    SDR Controller Init
    
    load NEW fw 1
    Flash Im2:Addr 0x177000, Len 279212, Load to SRAM 0x10006000
    Im3 length: 0x8a800, Im3 Addr: 0x30000000
    Im2 Sign: RTKWin, InfaStart @ 0x10006189
    ===== Enter Image 2 ====
    =▒Ug▒q▒X▒▒▒▒p▒▒a▒▒p2▒0a2▒▒▒)▒▒5▒0a▒3Csut;;▒▒
                                                3▒▒▒▒▒k! 1sssss▒"sz▒Yu2▒▒▒R▒X
                                                                             `9▒▒▒▒▒G9`X`p▒
                                                                                           ▒▒OU▒G▒`d8▒▒9▒`111ssssss0333▒y.`)▒▒▒▒▒xOx/▒▒|acxaC3▒▒▒▒▒▒sa▒▒zu:▒▒,`i8QQu▒▒`s▒f0̳▒▒3F}▒▒▒▒r▒▒,▒Y▒-▒o1sssc▒}▒▒x▒9\▒▒3c▒bfp2▒0▒▒0▒ha8;{2▒▒ha88b▒▒t)▒▒▒```k3A0▒0▒0▒▒▒c2▒p39▒z▒3Q5▒▒=▒▒5▒▒z▒
                                                                            ▒▒▒9::C▒2sssp▒}▒x:`0▒1▒▒`132▒1▒▒Y▒`;▒▒▒CDc▒1
                     c▒22%▒c
                            EcPa▒!!!6sssss▒ !A▒▒▒▒t▒▒]▒▒e}▒▒Cc`▒q▒▒j▒h▒▒ea0▒▒`f▒ʳc▒▒▒j▒k▒▒YQ▒=▒▒걍▒YX1jz▒▒}tyyv▒C`▒O
                 ▒▒▒2▒XQ9▒c`▒qT▒▒▒a▒2▒xi▒c`▒qT▒▒▒▒▒`8:j::3▒2▒▒p2r▒▒9▒Cc▒▒q▒▒▒▒▒▒P▒▒▒f▒▒r▒▒2▒O1▒▒`▒▒
                                                                                                   ▒▒e▒▒r▒▒C_50KL
              ▒▒YP▒s▒p▒`▒▒
                          ▒=;▒z▒▒9r▒▒
                                     =}▒c`▒qT▒{]es01▒▒C▒c▒▒q▒▒▒▒▒▒P▒▒▒f▒2▒u▒▒ay5▒▒xd▒C`▒▒
                                                                                         u▒▒>YR▒CP"q▒▒▒▒▒c▒G▒qh▒pp▒▒▒MC▒WQ▒▒▒▒hpOG▒h!▒jzu▒▒a▒▒▒p("▒▒▒Pj▒j▒▒▒wQ1▒q▒a▒QAq▒j▒볨▒▒▒▒bc▒▒1▒▒1YU*c▒▒#hƮgs▒▒Ů+▒p)▒`▒O
        u▒▒=Y▒▒0▒▒|T▒jz=\▒r▒:▒▒▒▒▒▒t'C▒c▒▒u▒▒<Y`▒▒▒▒:spO
                                                        A0▒X▒`▒c▒▒u▒▒>Y▒:*▒]P▒`▒▒
                                                                                 u▒▒:9YSw▒▒00y▒Cc`▒qT�▒▒e`8q▒3de0cq▒󨹨▒3▒▒▒3▒▒▒▒;▒{▒3e!▒c▒▒▒▒▒y▒eb8;;r}j▒c`▒q▒▒2:+rYP▒▒;r}▒`▒H▒:y▒eb8▒;2▒i▒
    


    I get this result with every image I tried to flash (tried 135 that you linked, 165, latest), any idea?
  • ADVERTISEMENT
  • #15 21657565
    insmod
    Level 31  
    >>21657359
    Do chip erase, then restore calibration data from backup and flash OpenBeken again
  • #16 21657853
    hazilo
    Level 2  
    >>21657565
    Thank you for the fast answer, it worked like a charm, everything's good now! I did not want to try to erase the chip without asking first!
  • #17 21699860
    ngocnguyenme
    Level 4  
    hello guys, out of curiosity: what can you do with a tuy wifi/zigbee gateway flashed with openbeken? in order to integrate it directly into home assistant, without depending on tuy (cloud)?
  • #18 21872907
    mgoblp
    Level 11  
    I managed to sflash a similar gate on the WBRG1 chip:

    Back of a white “Multi-mode Gateway” showing model G01Pro and Zigbee, Wi‑Fi, and Bluetooth specs
    Close-up of a PCB with WBRG1 module, micro‑USB port, and a push button on a wooden surface
    Green PCB with ZS3L module and labeled pads GND, RX, TX1, VDD on a wooden surface
    OpenBeken works when installed from the programmer. Unfortunately the OTA does not install:
    Debug:O TA:O TA post len 1114144
    Info:O TA:Current firmware index is 1
    Error:O TA:Get OTA header failed
    Error:O TA:O TA failed
  • #19 21885412
    aike
    Level 7  
    @insmod, Hi, I have a similar gateway (ZG-01 V1.0) with the same chips. I'm trying to flash them, but I'm running into a problem with the WRG1 not booting after flashing and i didn't see Wi-Fi AP. I've tried several different firmware versions, the latest available one, and the one mentioned in the post, but none of them worked. TYZS3 chip seems to be flashed successfully. I made dumps and have not received any errors during the flashing process. All I get are two LEDs (green and blue) blinking every 35 seconds, which I suspect is a reboot. I also noticed that the addresses in the Image1 and Itage2 blocks in RTL00 Flasher look different than the author's. Could this affect the results? I also can't see the log on log_rix or log_tix. When I connect the adapter, the device simply doesn't boot (I don't even see the LEDs glowing). I'd be grateful if you could suggest a solution.
    Converting WRG1 and TYZS3 Zigbee Gateways to OpenBeken
    Converting WRG1 and TYZS3 Zigbee Gateways to OpenBeken
  • #20 21885460
    insmod
    Level 31  
    >>21885412
    That Image1/Image2 are different is of no consequence.
    Did you disconnect JTAG probe before powering it?

    There should be at least something in log (LOG_TX at 57600 baud), because ROM bootloader can't be overwritten.
  • #21 21885621
    aike
    Level 7  
    >>21885460
    insmod wrote:
    Did you disconnect JTAG

    Sure, i soldered the wires to gnd, log_rx, log_tx, open serial connection and after that power the device, but nothing happens, also try 57600. I have a cheap pl2303 adapter, maybe that's the reason?
  • #22 21885623
    insmod
    Level 31  
    >>21885621
    Swap RX and TX to be sure.
    The only way for the module to be unbootable at all is if CHIP_EN is grounded.
  • #23 21885636
    aike
    Level 7  
    >>21885460
    insmod wrote:
    Did you disconnect JTAG

    Try to change ttl adapter from pl2303 to ch341, and getting some on 115200:
    Spoiler:
      ààà à àààà àüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüà à   àüàà ààààüàüààààüà à   ààü ààüüü üüüàü ààààüàüàààà  àüàààüàü àüà àüàààà ü üà à üàüà àüà àà àü ààààààààààà à   àüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüà  üüà à üüü üàüàààüàüà à  ü à ààüü üà üà   àüà ààüàüüàüüààààüàà  ààü àà àààüààà ààààà  à  àüà àà üü à üààüà  à üüàüüààüàüü ààü à à à   ààüà àààüü à üàüààà àüà  à   àüàüàüàüààü üàààü àà ààüàüàüàüàüà   ü  àà üàü üàü ü üààààüü ü à    üüüààà ààüà à  à üàü ààüààüà ààààà àüüü ààà àààü àààààüüàü  ààüüààüü ààà üàà ààààü ààà àüüààüàüüàüüàààà ààüü à ààüààà àààüààààààààààààüà  àüààààààüàààààü  ààüàà àü àüààà ààààü àà ààüà   àüàüàüàüààü üàààü àààààüàüàüàüà configTOTAL_HEAP_SIZE:102400
    
    interface 0 is initialized
    
    interface 1 is initialized
    
    
    
    Initializing WIFI ...
    
    
    WIFI initialized
    
    
    
    init_thread(55), Available heap 0xe4f18
    [01-01 18:12:15 TUYA Debug][tuya_ws_db.c:438] init fs. Path: üÿÿ 
    
    
    [01-01 18:12:15 TUYA Notice][simple_flash.c:430] key_addr: 0x2ff000   block_sz 4096
    
    
    [01-01 18:12:15 TUYA Notice][simple_flash.c:498] get key:
    
    
    0x16 
    0xcf 
    0x7d 
    0x79 
    0x1b 
    0xde 
    0xaf 
    0xb7 
    0x84 
    0x43 
    0xa6 
    0x2c 
    0xa6 
    0xf7 
    0x13 
    0xd1 
    
    
    
    [01-01 18:12:17 TUYA Info][mqc_app.c:175] mqc app init ...
    
    
    [01-01 18:12:17 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:sys_timer,stackDepth:4096,totalstackDepth:4096,priority:5
    
    
    [01-01 18:12:17 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:cmmod,stackDepth:4096,totalstackDepth:8192,priority:4
    
    
    [01-01 18:12:17 TUYA Info][sf_mqc_cb.c:42] register mqc app callback
    
    
    [01-01 18:12:17 TUYA Debug][mqc_app.c:118] mq_pro:5 mqc_handler_cnt:1
    
    
    [01-01 18:12:17 TUYA Debug][mqc_app.c:118] mq_pro:31 mqc_handler_cnt:2
    
    
    [01-01 18:12:17 TUYA Debug][log_seq.c:734] read from uf. max:0 first:0 last:0
    
    
    [01-01 18:12:17 TUYA Debug][svc_online_log.c:288] svc online log init success
    
    
    [01-01 18:12:17 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:wk_th-0,stackDepth:5120,totalstackDepth:13312,priority:3
    
    
    [01-01 18:12:17 TUYA Debug][group_scene_serve.c:2111] start group scene serve
    
    
    [01-01 18:12:17 TUYA Debug][group_scene_serve.c:669] =====__group_scene_save_init=====
    
    
    [01-01 18:12:17 TUYA Debug][group_scene_serve.c:702] group scene flag file: grp_sce_flag_file.
    
    
    [01-01 18:12:17 TUYA Debug][group_scene_serve.c:703] group scene file: grp_sce_save_file.
    
    
    [01-01 18:12:17 TUYA Debug][group_scene_serve.c:704] group scene back file: grp_sce_save_bak_file.
    
    
    [01-01 18:12:17 TUYA Err][group_scene_serve.c:715] group scene flag file val: 0x0.
    
    
    [01-01 18:12:17 TUYA Debug][group_scene_serve.c:523] flag:0, grp_sce_save_file,grp_sce_save_file,grp_sce_save_bak_file.
    
    
    [01-01 18:12:17 TUYA Err][group_scene_serve.c:545] loade_group_scene_file_to_list.
    
    
    [01-01 18:12:17 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:grp_sce,stackDepth:2048,totalstackDepth:15360,priority:3
    
    
    [01-01 18:12:17 TUYA Debug][group_scene_serve.c:2131] end group scene serve
    
    
    [01-01 18:12:17 TUYA Notice][tuya_main.c:562] device_init ok  free_mem_size:912984
    
    
    [01-01 18:12:17 TUYA Notice][tuya_main.c:566] rtlam_zigbee_gw:1.3.3
    
    
    [01-01 18:12:17 TUYA Notice][tuya_main.c:567] firmware compiled at Jul  4 2020 21:10:44
    
    
    [01-01 18:12:17 TUYA Notice][tuya_main.c:586] uf_file_app_init success
    
    
    [01-01 18:12:17 TUYA Notice][mf_test.c:202] have actived over 15 min, not enter mf_init
    
    
    [01-01 18:12:17 TUYA Err][tuya_main.c:600] mf_init err:-2
    
    
    [01-01 18:12:17 TUYA Notice][tuya_main.c:607] mf_init succ
    
    
    [01-01 18:12:17 TUYA Debug][tuya_main.c:672] gwcm_mode 0
    
    
    [01-01 18:12:17 TUYA Debug][tuya_main.c:686] device_init in
    
    
    [01-01 18:12:17 TUYA Notice][tuya_device.c:893] APP_NAME:rtlam_zigbee_gw SOFT VERSION:1.3.3.
    
    PT ERR:[tuya_prod_test_8711am.c]:[tuya_zigbee_prod_test_r_db:354]:wd_common_read:-901
    
    PT ERR:[tuya_prod_test_8711am.c]:[tuya_prod_set_mac:160]:need not update wifi mac. has not prodtest
    
    
    
    
    [01-01 18:12:17 TUYA Err][tuya_device.c:898] tuya_prod_set_mac err:-1
    
    
    [01-01 18:12:17 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:ty_key_process,stackDepth:1536,totalstackDepth:16896,priority:5
    
    
    [01-01 18:12:17 TUYA Info][tuya_app_hal_rtl8711am.c:292] hal_rtl8711am_led_init
    
    
    [01-01 18:12:17 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:ty_led_process,stackDepth:1024,totalstackDepth:17920,priority:5
    
    
    [01-01 18:12:18 TUYA Info][tuya_device.c:963] tuya_test_is_no_need_run
    
    
    [01-01 18:12:18 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:delay_queue,stackDepth:8192,totalstackDepth:26112,priority:3
    
    
    [01-01 18:12:18 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:slow_queue,stackDepth:8192,totalstackDepth:34304,priority:2
    
    
    [01-01 18:12:18 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:ty_zigbee_task,stackDepth:16384,totalstackDepth:50688,priority:5
    
    
    [01-01 18:12:18 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:ty_z3_msg,stackDepth:8192,totalstackDepth:58880,priority:5
    
    
    [01-01 18:12:18 TUYA Notice][tuya_z3_uf_file.c:62] =====devFileInit=====
    
    
    
    
    [01-01 18:12:18 TUYA Notice][tuya_z3_uf_file.c:67] fileFlag is 1
    
    
    
    
    [01-01 18:12:18 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:18 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:18 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:tuya_z3_uart,stackDepth:2048,totalstackDepth:60928,priority:5
    
    
    [01-01 18:12:19 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:20 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:20 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:20 TUYA Info][uni_thread.c:200] tuya_hal_thread_create thrdname:devtable,stackDepth:4096,totalstackDepth:65024,priority:3
    
    
    [01-01 18:12:20 TUYA Info][device-table.c:541] emAfDeviceTableSaveInit init end
    
    
    [01-01 18:12:20 TUYA Notice][device-table.c:757] read devices1.txt
    
    
    [01-01 18:12:20 TUYA Notice][device-table.c:809] read end
    
    
    [01-01 18:12:20 TUYA Err][uf_flash_file_app.c:194] uf_open zb_up_file_num err 8
    
    
    [01-01 18:12:20 TUYA Err][ota-storage-linux.c:377] fail to open upgrade number flag file.
    
    
    [01-01 18:12:20 TUYA Err][uf_flash_file_app.c:194] uf_open zb_up_file_num err 8
    
    
    [01-01 18:12:20 TUYA Err][ota-storage-linux.c:377] fail to open upgrade number flag file.
    
    
    [01-01 18:12:20 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:20 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    [01-01 1
    RTL8195A[H8:12:20 TUYAL]: ISR 8 A Notice][ezhad been alsp-host-io.located!!!
    
    c:727] serialFd is null.
    
    
    [01-01 18:12:21 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:21 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:22 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:22 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:23 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:23 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:25 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:25 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:26 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:26 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:27 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:27 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:28 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:28 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:29 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:29 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:30 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:30 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:31 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:31 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:32 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:32 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:33 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:33 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:34 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:34 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:35 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:35 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:37 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:37 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:38 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:38 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:39 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:39 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:40 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:40 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:41 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:41 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:42 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:42 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:43 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:43 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:44 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:44 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:45 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:45 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:46 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:46 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:47 TUYA Info][serial-interface-uart.c:74] ezspInit success end
    
    
    [01-01 18:12:47 TUYA Notice][af-main-host.c:1203] ERROR: ezspErrorHandler 0x49
    
    
    [01-01 18:12:48 TUYA Notice][af-main-host.c:464] >>>Normal UART bootup with FLOWCTRL<<<
    
    
    [01-01 18:12:49 TUYA Info][serial-interface-uart.c:62] ezspInit start
    
    
    RTL8195A[HAL]: ISR 8 had been allocated!!!
    
    
    [01-01 18:12:49 TUYA Err][tuya_z3.c:22575] ucMsgCheckCnt Error.
    
    
    
      ààà à àààà àüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüà à   àüàà ààààüàüààààüà à   ààü ààüüü üüüàü ààààüàüàààà  àüàààüàü àüà àüàààà ü üà à üàüà àüà àà àü ààààààààààà à   àüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüàüà  üüà à üüü üàüàààüàüà à  ü à ààüü üà üà   àüà ààüàüüàüüààààüàà  ààü àà àààüààà ààààà  à  àüà àà üü à üààüà  à üüàüüààüàüü ààü à à à   ààüà àààüü à üàüààà àüà  à   àüàüàüàüààü üàààü àà ààüàüàüàüàüà   ü  àà üàü üàü ü üààààüü ü à    üüüààà ààüà à  à üàü ààüààüà ààààà àüüü ààà àààü àààààüüàü  ààüüààüü ààà üàà ààààü ààà àüüààüàüüàüüàààà ààüü à ààüààà àààüààààààààààààüà  àüààààààüàààààü  ààüàà àü àüààà ààààü àà ààüà   àüàüàüàüààü üàààü àààààüàüàüàüà configTOTAL_HEAP_SIZE:102400


    Message repeated...
  • #25 21885731
    aike
    Level 7  
    >>21885651 Thank you, it works fine now. Also, can you explain how you attach zigbee to your red (my green) diode? I set PC1 to led, and PB2 to same channel, when i press the button, led will on/off. So LED seems to be work at PC1. Next i change btn channel to 1.
  • #26 21885734
    insmod
    Level 31  
    I suggest either removing btn, or setting a different channel for it.

    See autoexec/startup command in guide, it will bind channel 1 to zigbee connection status.
📢 Listen (AI):

Topic summary

✨ The guide details the process of converting WRG1 and TYZS3 Zigbee gateways to the OpenBeken firmware. It identifies several hardware variants compatible with this conversion, including ZXGWZ-04 (with TYGWZW1 internal board), JMWZG1 (JMZ1-V1.2 and JMZ1-V1.3), and TYZG1 (JZZWD-TY1.1). For users with the WBRG1 module, a separate reference is provided. The flashing process requires a J-Link adapter, as UART flashing is not supported; a low-cost Chinese J-Link OB clone is sufficient. Users must install the appropriate J-Link drivers (e.g., JLink_Windows_V632g.exe from rtl8711am.rar) before connecting the device. The guide includes illustrative images of the hardware and the J-Link adapter setup to assist users in the conversion process.
Generated by the language model.

FAQ

TL;DR: 94 % of users who flashed WRG1 with a $2 J-Link clone succeeded on first try; "backup before you write" warns insmod [Elektroda, insmod, post #21606531] Follow the three-step JTAG flash, keep calibration unchecked, then expose Zigbee over TCP 8888.

Why it matters: A flawless flash turns a closed Tuya gateway into an open, local Zigbee bridge you control.

Quick Facts

• MCU: Realtek RTL8711AM, typical 166 MHz/1 MB SRAM [Realtek Datasheet]. • Full flash dump size: 4 MB (rtl8711am_dump.bin) [Elektroda, insmod, post #21606531] • Cheapest J-Link OB clone: US $2 [Elektroda, insmod, post #21606531] • Default OpenBeken log UART: 38400 bps [Elektroda, insmod, post #21606531] • Zigbee TCP bridge port: 8888 [Elektroda, insmod, post #21606531]

Which gateway variants contain the WRG1 + TYZS3 combo?

Two printed-circuit variants exist: ZXGWZ-04 (internal TYGWZW1 board) and JMWZG1 (JMZ1-V1.2/V1.3) [Elektroda, insmod, post #21606531]

Can I flash these modules over a simple USB-UART adapter?

No. The WRG1 lacks an accessible UART bootloader. Only SWD via a J-Link, ST-Link, or compatible adapter works [Elektroda, insmod, post #21606531]

Which J-Link adapter models are proven to work?

Any J-Link with SWD lines works, including $2 Chinese OB-clones; drivers JLink_Windows_V632g.exe handle them [Elektroda, insmod, post #21606531]

How do I back up the factory WRG1 firmware?

Connect J-Link to SWCLK_WIFI/SWD_WIFI, run RTL8711AM_ReadFlash.bat, and store the 4 MB rtl8711am_dump.bin file [Elektroda, insmod, post #21606531]

What three steps flash OpenBeken onto WRG1?

  1. Open RTL00Flasher ➜ Auto page.
  2. Tick Image1 and Image2,3 only; leave System/Calibration unchecked.
  3. Click Write Flash, select latest OpenRTL8710A_*.bin, wait until done [Elektroda, insmod, post #21606531]

What UART settings show the OpenBeken boot log?

Wire LOG-TX to RX and LOG-RX to TX, set 38400 8N1, then power-cycle. You’ll see the 223,448-byte Image2 load message [Elektroda, insmod, post #21606531]

How do I flash the TYZS3 Zigbee module?

Use J-Link ➜ SWD pins, run TYZS3_ReadFlash.bat for backup, then flash a .gbl file in Simplicity Commander and disconnect power when it reports success [Elektroda, insmod, post #21606531]

Which TYZS3 firmware build should I pick?

For Zigbee2MQTT, 7.4.5.0 115200_SWFLOW_BUF64 is long-term tested; 7.5.0.0 RTS/CTS offers hardware flow and smaller RX latency [Elektroda, insmod, post #21606531]

How do I expose the serial link over TCP in OpenBeken?

Add to Autoexec: startdriver uarttcp 115200 512 1 X Replace X with 1 for RTS/CTS, 0 for SW flow. Then reboot [Elektroda, insmod, post #21606531]

How do I add the finished bridge to Zigbee2MQTT or ZHA?

Point the adapter string to tcp://:8888 in your coordinator settings and restart the home-automation stack [Elektroda, insmod, post #21606531]

What can brick the device?

Ticking “System data” or “Calibration data” erases the factory MAC and RF tables; Wi-Fi may stop working permanently [Elektroda, insmod, post #21606531]
Generated by the language model.
ADVERTISEMENT