logo elektroda
logo elektroda
X
logo elektroda

RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

divadiow 40155 409
ADVERTISEMENT
  • Helpful post

    Bluetooth appears in hcitool but stays down

    #271 21491102
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    Currently trying to get bluetooth working (amebad only).
    I can at least get it to show in hcitool, but cannot get it up.
    This is done via a variant of uart-tcp bridge.
    sudo socat pty,link=/dev/virtualcom0,b115200,raw,echo=0 TCP:192.168.1.19:8721
    sudo btattach -B /dev/virtualcom0 -S 115200 -P h4

    hciconfig -a
    hci0:   Type: Primary  Bus: UART
            BD Address: 94:C9:60:E2:39:AB  ACL MTU: 0:0  SCO MTU: 0:0
            DOWN
            RX bytes:256 acl:0 sco:0 events:12 errors:0
            TX bytes:530 acl:0 sco:0 commands:12 errors:0
            Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
            Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
            Link policy:
            Link mode: PERIPHERAL ACCEPT
    

    
    hcitool[1529994]: @ RAW Open: hcitool (privileged) version 2.22                                    {0x0002} 1818.467367
    hcitool[1529994]: @ RAW Close: hcitool                                                             {0x0002} 1818.467378
    hciconfig[1530015]: @ RAW Open: hciconfig (privileged) version 2.22                                {0x0002} 1822.803105
    = Open Index: 94:C9:60:E2:39:AB                                                                      [hci0] 1822.803117
    = Index Info: 94:C9:60:E2:39:AB (Realtek Semiconductor Corporation)                                  [hci0] 1822.803118
    < HCI Command: Reset (0x03|0x0003) plen 0                                                       #111 [hci0] 1822.803150
    > HCI Event: Command Complete (0x0e) plen 4                                                     #112 [hci0] 1822.813042
          Reset (0x03|0x0003) ncmd 3
            Status: Success (0x00)
    < HCI Command: Read Local Supported Features (0x04|0x0003) plen 0                               #113 [hci0] 1822.813190
    > HCI Event: Command Complete (0x0e) plen 12                                                    #114 [hci0] 1822.832294
          Read Local Supported Features (0x04|0x0003) ncmd 2
            Status: Success (0x00)
            Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
              3 slot packets
              5 slot packets
              Encryption
              Slot offset
              Timing accuracy
              Role switch
              Hold mode
              Sniff mode
              Park state
              Power control requests
              Channel quality driven data rate (CQDDR)
              SCO link
              HV2 packets
              HV3 packets
              u-law log synchronous data
              A-law log synchronous data
              CVSD synchronous data
              Paging parameter negotiation
              Power control
              Transparent synchronous data
              Flow control lag (least significant bit)
              Flow control lag (middle bit)
              Flow control lag (most significant bit)
              Broadcast Encryption
              Enhanced Data Rate ACL 2 Mbps mode
              Enhanced Data Rate ACL 3 Mbps mode
              Enhanced inquiry scan
              Interlaced inquiry scan
              Interlaced page scan
              RSSI with inquiry results
              Extended SCO link (EV3 packets)
              EV4 packets
              EV5 packets
              AFH capable peripheral
              AFH classification peripheral
              LE Supported (Controller)
              3-slot Enhanced Data Rate ACL packets
              5-slot Enhanced Data Rate ACL packets
              Sniff subrating
              Pause encryption
              AFH capable central
              AFH classification central
              Enhanced Data Rate eSCO 2 Mbps mode
              Enhanced Data Rate eSCO 3 Mbps mode
              3-slot Enhanced Data Rate eSCO packets
              Extended Inquiry Response
              Simultaneous LE and BR/EDR (Controller)
              Secure Simple Pairing
              Encapsulated PDU
              Erroneous Data Reporting
              Non-flushable Packet Boundary Flag
              Link Supervision Timeout Changed Event
              Inquiry TX Power Level
              Enhanced Power Control
              Extended features
    < HCI Command: Read Local Version Information (0x04|0x0001) plen 0                              #115 [hci0] 1822.832551
    > HCI Event: Command Complete (0x0e) plen 12                                                    #116 [hci0] 1822.849989
          Read Local Version Information (0x04|0x0001) ncmd 2
            Status: Success (0x00)
            HCI version: Bluetooth 5.0 (0x09) - Revision 56870 (0xde26)
            LMP version: Bluetooth 5.0 (0x09) - Subversion 58706 (0xe552)
            Manufacturer: Realtek Semiconductor Corporation (93)
    < HCI Command: Read BD ADDR (0x04|0x0009) plen 0                                                #117 [hci0] 1822.850128
    > HCI Event: Command Complete (0x0e) plen 10                                                    #118 [hci0] 1822.869119
          Read BD ADDR (0x04|0x0009) ncmd 2
            Status: Success (0x00)
            Address: 94:C9:60:E2:39:AB (Zhongshan B&T technology.co.,ltd)
    < HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0                               #119 [hci0] 1822.869373
    > HCI Event: Command Complete (0x0e) plen 68                                                    #120 [hci0] 1822.888391
          Read Local Supported Commands (0x04|0x0002) ncmd 2
            Status: Success (0x00)
            Commands: 157 entries
              Inquiry (Octet 0 - Bit 0)
              Inquiry Cancel (Octet 0 - Bit 1)
              Create Connection (Octet 0 - Bit 4)
              Disconnect (Octet 0 - Bit 5)
              Create Connection Cancel (Octet 0 - Bit 7)
              Accept Connection Request (Octet 1 - Bit 0)
              Reject Connection Request (Octet 1 - Bit 1)
              Link Key Request Reply (Octet 1 - Bit 2)
              Link Key Request Negative Reply (Octet 1 - Bit 3)
              PIN Code Request Reply (Octet 1 - Bit 4)
              PIN Code Request Negative Reply (Octet 1 - Bit 5)
              Change Connection Packet Type (Octet 1 - Bit 6)
              Authentication Requested (Octet 1 - Bit 7)
              Set Connection Encryption (Octet 2 - Bit 0)
              Change Connection Link Key (Octet 2 - Bit 1)
              Remote Name Request (Octet 2 - Bit 3)
              Remote Name Request Cancel (Octet 2 - Bit 4)
              Read Remote Supported Features (Octet 2 - Bit 5)
              Read Remote Version Information (Octet 2 - Bit 7)
              Read Clock Offset (Octet 3 - Bit 0)
              Read LMP Handle (Octet 3 - Bit 1)
              QoS Setup (Octet 4 - Bit 6)
              Role Discovery (Octet 4 - Bit 7)
              Read Link Policy Settings (Octet 5 - Bit 1)
              Write Link Policy Settings (Octet 5 - Bit 2)
              Read Default Link Policy Settings (Octet 5 - Bit 3)
              Write Default Link Policy Settings (Octet 5 - Bit 4)
              Flow Specification (Octet 5 - Bit 5)
              Set Event Mask (Octet 5 - Bit 6)
              Reset (Octet 5 - Bit 7)
              Set Event Filter (Octet 6 - Bit 0)
              Flush (Octet 6 - Bit 1)
              Read PIN Type (Octet 6 - Bit 2)
              Write PIN Type (Octet 6 - Bit 3)
              Create New Unit Key (Octet 6 - Bit 4)
              Read Stored Link Key (Octet 6 - Bit 5)
              Write Stored Link Key (Octet 6 - Bit 6)
              Delete Stored Link Key (Octet 6 - Bit 7)
              Write Local Name (Octet 7 - Bit 0)
              Read Local Name (Octet 7 - Bit 1)
              Read Connection Accept Timeout (Octet 7 - Bit 2)
              Write Connection Accept Timeout (Octet 7 - Bit 3)
              Read Page Timeout (Octet 7 - Bit 4)
              Write Page Timeout (Octet 7 - Bit 5)
              Read Scan Enable (Octet 7 - Bit 6)
              Write Scan Enable (Octet 7 - Bit 7)
              Read Page Scan Activity (Octet 8 - Bit 0)
              Write Page Scan Activity (Octet 8 - Bit 1)
              Read Inquiry Scan Activity (Octet 8 - Bit 2)
              Write Inquiry Scan Activity (Octet 8 - Bit 3)
              Read Authentication Enable (Octet 8 - Bit 4)
              Write Authentication Enable (Octet 8 - Bit 5)
              Read Class of Device (Octet 9 - Bit 0)
              Write Class of Device (Octet 9 - Bit 1)
              Read Voice Setting (Octet 9 - Bit 2)
              Write Voice Setting (Octet 9 - Bit 3)
              Read Automatic Flush Timeout (Octet 9 - Bit 4)
              Write Automatic Flush Timeout (Octet 9 - Bit 5)
              Read Num Broadcast Retransmissions (Octet 9 - Bit 6)
              Write Num Broadcast Retransmissions (Octet 9 - Bit 7)
              Read Transmit Power Level (Octet 10 - Bit 2)
              Read Sync Flow Control Enable (Octet 10 - Bit 3)
              Write Sync Flow Control Enable (Octet 10 - Bit 4)
              Set Controller To Host Flow Control (Octet 10 - Bit 5)
              Host Buffer Size (Octet 10 - Bit 6)
              Host Number of Completed Packets (Octet 10 - Bit 7)
              Read Link Supervision Timeout (Octet 11 - Bit 0)
              Write Link Supervision Timeout (Octet 11 - Bit 1)
              Read Number of Supported IAC (Octet 11 - Bit 2)
              Read Current IAC LAP (Octet 11 - Bit 3)
              Write Current IAC LAP (Octet 11 - Bit 4)
              Read Page Scan Mode (Octet 11 - Bit 7)
              Write Page Scan Mode (Octet 12 - Bit 0)
              Set AFH Host Channel Classification (Octet 12 - Bit 1)
              Read Inquiry Scan Type (Octet 12 - Bit 4)
              Write Inquiry Scan Type (Octet 12 - Bit 5)
              Read Inquiry Mode (Octet 12 - Bit 6)
              Write Inquiry Mode (Octet 12 - Bit 7)
              Read Page Scan Type (Octet 13 - Bit 0)
              Write Page Scan Type (Octet 13 - Bit 1)
              Read AFH Channel Assessment Mode (Octet 13 - Bit 2)
              Write AFH Channel Assessment Mode (Octet 13 - Bit 3)
              Read Local Version Information (Octet 14 - Bit 3)
              Read Local Supported Features (Octet 14 - Bit 5)
              Read Buffer Size (Octet 14 - Bit 7)
              Read BD ADDR (Octet 15 - Bit 1)
              Read Failed Contact Counter (Octet 15 - Bit 2)
              Reset Failed Contact Counter (Octet 15 - Bit 3)
              Read Link Quality (Octet 15 - Bit 4)
              Read RSSI (Octet 15 - Bit 5)
              Read AFH Channel Map (Octet 15 - Bit 6)
              Read Clock (Octet 15 - Bit 7)
              Read Loopback Mode (Octet 16 - Bit 0)
              Write Loopback Mode (Octet 16 - Bit 1)
              Enable Device Under Test Mode (Octet 16 - Bit 2)
              Read Extended Inquiry Response (Octet 17 - Bit 0)
              Write Extended Inquiry Response (Octet 17 - Bit 1)
              Refresh Encryption Key (Octet 17 - Bit 2)
              Read Simple Pairing Mode (Octet 17 - Bit 5)
              Write Simple Pairing Mode (Octet 17 - Bit 6)
              Read Local OOB Data (Octet 17 - Bit 7)
              Read Inquiry Response TX Power Level (Octet 18 - Bit 0)
              Write Inquiry Transmit Power Level (Octet 18 - Bit 1)
              IO Capability Request Reply (Octet 18 - Bit 7)
              User Confirmation Request Reply (Octet 19 - Bit 0)
              User Confirmation Request Neg Reply (Octet 19 - Bit 1)
              User Passkey Request Reply (Octet 19 - Bit 2)
              User Passkey Request Negative Reply (Octet 19 - Bit 3)
              Remote OOB Data Request Reply (Octet 19 - Bit 4)
              Write Simple Pairing Debug Mode (Octet 19 - Bit 5)
              Enhanced Flush (Octet 19 - Bit 6)
              Remote OOB Data Request Neg Reply (Octet 19 - Bit 7)
              Send Keypress Notification (Octet 20 - Bit 2)
              IO Capability Request Negative Reply (Octet 20 - Bit 3)
              Read Encryption Key Size (Octet 20 - Bit 4)
              Read Enhanced Transmit Power Level (Octet 24 - Bit 0)
              Read LE Host Supported (Octet 24 - Bit 5)
              Write LE Host Supported (Octet 24 - Bit 6)
              LE Set Event Mask (Octet 25 - Bit 0)
              LE Read Buffer Size (Octet 25 - Bit 1)
              LE Read Local Supported Features (Octet 25 - Bit 2)
              LE Set Random Address (Octet 25 - Bit 4)
              LE Set Advertising Parameters (Octet 25 - Bit 5)
              LE Read Advertising Channel TX Power (Octet 25 - Bit 6)
              LE Set Advertising Data (Octet 25 - Bit 7)
              LE Set Scan Response Data (Octet 26 - Bit 0)
              LE Set Advertise Enable (Octet 26 - Bit 1)
              LE Set Scan Parameters (Octet 26 - Bit 2)
              LE Set Scan Enable (Octet 26 - Bit 3)
              LE Create Connection (Octet 26 - Bit 4)
              LE Create Connection Cancel (Octet 26 - Bit 5)
              LE Read Accept List Size (Octet 26 - Bit 6)
              LE Clear Accept List (Octet 26 - Bit 7)
              LE Add Device To Accept List (Octet 27 - Bit 0)
              LE Remove Device From Accept List (Octet 27 - Bit 1)
              LE Connection Update (Octet 27 - Bit 2)
              LE Set Host Channel Classification (Octet 27 - Bit 3)
              LE Read Channel Map (Octet 27 - Bit 4)
              LE Read Remote Used Features (Octet 27 - Bit 5)
              LE Encrypt (Octet 27 - Bit 6)
              LE Rand (Octet 27 - Bit 7)
              LE Start Encryption (Octet 28 - Bit 0)
              LE Long Term Key Request Reply (Octet 28 - Bit 1)
              LE Long Term Key Request Neg Reply (Octet 28 - Bit 2)
              LE Read Supported States (Octet 28 - Bit 3)
              LE Receiver Test (Octet 28 - Bit 4)
              LE Transmitter Test (Octet 28 - Bit 5)
              LE Test End (Octet 28 - Bit 6)
              LE Set Data Length (Octet 33 - Bit 6)
              LE Read Suggested Default Data Length (Octet 33 - Bit 7)
              LE Write Suggested Default Data Length (Octet 34 - Bit 0)
              LE Read Maximum Data Length (Octet 35 - Bit 3)
              LE Read PHY (Octet 35 - Bit 4)
              LE Set Default PHY (Octet 35 - Bit 5)
              LE Set PHY (Octet 35 - Bit 6)
              LE Enhanced Receiver Test (Octet 35 - Bit 7)
              LE Enhanced Transmitter Test (Octet 36 - Bit 0)
    < HCI Command: Write Extended Inquiry Response (0x03|0x0052) plen 241                           #121 [hci0] 1822.888608
            FEC: Not required (0x00)
    > HCI Event: Command Complete (0x0e) plen 4                                                     #122 [hci0] 1822.923086
          Write Extended Inquiry Response (0x03|0x0052) ncmd 2
            Status: Unknown HCI Command (0x01)
    = Close Index: 94:C9:60:E2:39:AB                                                                     [hci0] 1822.923258
    [1530015]: @ RAW Close: hciconfig                                                                  {0x0002} 1822.923764
    


    It seems that some opcodes are not implemented.
    Bluetooth: hci0: Opcode 0x0c52 failed: -56

    And realtek library is built to support only LE mode, not BR/EDR(legacy).
    Unsure if i'll manage to get it to work, but at least i'll report what i've done and if someone might figure out what to do in the future.
    I should also note that this is done via hci_driver from Tuya rtl8721cs source.

    Added after 2 [hours] 32 [minutes]:

    I wasn't able to fix it in sdk code, so i had to adapt linux bluetooth driver.
    I was able to get it running, but no tests were done.
    hci0:   Type: Primary  Bus: UART
            BD Address: 94:C9:60:E2:39:AB  ACL MTU: 0:0  SCO MTU: 0:0
            UP RUNNING
            RX bytes:500 acl:0 sco:0 events:19 errors:0
            TX bytes:99 acl:0 sco:0 commands:19 errors:0
            Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
            Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
            Link policy:
            Link mode: PERIPHERAL ACCEPT
            Name: 'RTK_BT_5.0'
    Can't read class of device on hci0: Input/output error (5)

    But while i can somewhat control it via hcitool, bluetoothctl doesn't see it.
  • ADVERTISEMENT
  • #272 21491178
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    cool work dude. what's your aim/end goal for its use?
  • ADVERTISEMENT
  • #273 21491193
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    >>21491178 I originally intended to use it as a sort of 'wireless' bluetooth adapter for HA.
    But that won't work now, since i've had to modify kernel module code. And even now, while it responds to some commands, i can't perform a scan, hcitool lescan just prints "LE Scan ...", and btmgmt find prints "Unable to start discovery. status 0x11 (Invalid Index)"
  • Tuya Realtek SDK download links for rtl8720cf_ameba

    #274 21521468
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    hard links for Tuya Realtek SDK resources

    rtl8720cf_ameba
    Spoiler:

    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_1.0.33.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_1.0.34.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_1.0.35.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_1.0.36.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_1.0.37.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_1.0.38.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_1.0.39.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_2.0.0.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_2.3.0.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_2.3.1.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_2.3.2.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_2.3.3.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_2.3.4.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_2.3.5.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_2.3.7.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.11.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.12.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.13.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.14.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.15.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.16.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.17.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.18.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.19.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.20.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_2.3.22.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_3.1.0.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_3.1.1.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_3.6.1.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_3.8.0.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_3.8.3.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_3.8.5.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_3.8.6.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/rtl8720cf_ameba_3.8.9.zip
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_3.8.16.zip

    rtl8720cm_ameba

    rtl8720dn
    Spoiler:

    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.0.68.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.0.69.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.1.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.2.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.3.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.4.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.5.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.6.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.7.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.8.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.2.9.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.10.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.11.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.12.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.13.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.14.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.15.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.16.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.17.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.18.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.19.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.20.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.21.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.22.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.23.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.24.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.27.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8720dn_1.2.29.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.3.1.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8720dn_1.3.2.zip

    rtl8721cs

    rtl8710bn
    Spoiler:

    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.18.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.19.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.20.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.21.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.22.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.23.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.24.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.25.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.26.zip
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8710bn_1.0.27.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8710bn_2.0.0.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8710bn_2.0.1.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8710bn_2.0.4.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8710bn_2.0.5.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8710bn_2.0.6.zip
    https://airtake-public-data-1254153901.cos.ap...d.com/smart/embed/pruduct/rtl8710bn_2.0.7.zip
  • ADVERTISEMENT
  • Firmware links for rtl8711am and rtl8720dn

    #275 21552308
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    rtl8711am
    Code: Text
    Log in, to see the code


    Added after 8 [hours] 57 [minutes]:

    test_rtl8720dn
    Spoiler:

    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.36.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.37.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.38.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.39.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.40.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.41.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.42.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.43.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.44.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.45.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.46.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.47.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.48.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.49.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.50.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.51.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.52.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.53.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.54.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.55.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.56.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.57.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.58.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.64.zip
    https://airtake-public-data-1254153901.cos.ap...smart/embed/pruduct/test_rtl8720dn_1.0.65.zip


    Added after 29 [minutes]:

    new April 2025 RTL8720CF
    https://airtake-public-data-1254153901.cos.ap...mart/embed/pruduct/rtl8720cf_ameba_3.8.23.zip

    I think I should put these all in text files on GH in one place or something, better than all these random posts around.
  • #276 21552880
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    rtl8720cf_ameba_3.8.23.zip contains hci_driver similar to the one in rtl8721cs archives.
    Though it will probably work even worse that in amebad, since there are less flags enabled in bt_flags.h
    And only RTL8720E lib contains support for bluetooth classic (BR/EDR), that is required for bluetooth initialization in linux kernel.
  • #278 21583204
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    insmod wrote:
    . BW16, when connecting to my server with MT7925 card in 5ghz AP mode, crashes driver so 'hard', that i cannot sigkill hostapd and properly reboot, forcing me to cut power.


    @naimoctal in answer to your DM, I don't believe 5Ghz support was fixed for OpenRTL8720DN. I can check later with device unless someone else confirms in the meantime
  • #279 21583215
    naimoctal
    Level 1  
    Posts: 1
    >>21583204 Thank you, I am waiting to see 5GHz. I am Bangladeshi, please pardon my mistakes.
  • Helpful post

    AmebaDplus boots with OpenBeken-compatible firmware logs

    #280 21598547
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    A little progress with AmebaDplus
    ROM:[V1.1]
    FLASH RATE:1, Pinmux:0
    IMG1(OTA1) VALID, ret: 0
    IMG1 ENTRY[f800731:0]
    [BOOT-I] KM4 BOOT REASON 0: Initial Power on
    [BOOT-I] KM4 CPU CLK: 262000000 Hz
    [BOOT-I] KM0 CPU CLK: 104800000 Hz
    [BOOT-I] PSRAM Ctrl CLK: 262000000 Hz 
    [BOOT-I] IMG1 ENTER MSP:[30009FE4]
    [BOOT-I] Build Time: Jul  5 2025 20:35:34
    [BOOT-I] IMG1 SECURE STATE: 1
    [FLASH-I] Flash ID: 20-40-16 (Capacity: 32M-bit)
    [FLASH-I] Flash Read 4IO
    [FLASH-I] FLASH HandShake[0x2 OK]
    [BOOT-I] KM0 XIP IMG[0c000000:559a0]
    [BOOT-I] KM0 SRAM[20068000:3060]
    [BOOT-I] KM0 PSRAM[0c058a00:20]
    [BOOT-I] KM0 ENTRY[20004d00:60]
    [BOOT-I] KM4 XIP IMG[0e000000:8c6a0]
    [BOOT-I] KM4 SRAM[2000b000:28c0]
    [BOOT-I] KM4 PSRAM[0e08ef60:20]
    [BOOT-I] KM4 ENTRY[20004d80:40]
    [BOOT-I] IMG2 BOOT from OTA 1, Version: 1.1 
    [BOOT-I] Image2Entry @ 0xe02cbc5 ...
    [APP-I] KM4 APP START 
    [LOCKS-I] KM0 init_retarget_l[ocAkPsP-I
    ] VTOR: 30007000, VTOR_NS:30007000
    [APP-I] VTOR: 30007000, VTOR_NS:30007000
    [MAI[ANP-PI-I]]  IIMWGD2G  rSeECfUrReEsh S oTnAT!E
    : 1
    [MAIN-I] KM0 OS START 
    [CLK-I] [CAL4M]: delta:2 target:320 PPM: 6250 PPM_Limit:30000 
    [CLK-I] [CAL131K]: delta:22 target:2441 PPM: 9012 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
    [MAIN-I] KM4 START SCHEDULER 
    interface 0 is initialized
    interface 1 is initialized
    [WLAN-I] LWIP consume heap 1312
    [WLAN-A] Init WIFI
    [WLAN-A] Band=2.4G&5G
    [WLAN-I] NP consume heap 20304
    [FAST_CONNECT] Fast connect profile is not exist
    [WLAN-I] AP consume heap 10656
    [WLAN-I] Available heap after wifi init 289888
    OpenRTL8721DX, version 
    Entering initLog()...
    Commands registered!
    initLog() done!
    Main_Init_Before_Delay done
    Main_Init_Delay
    Main_Init_Delay done
    Info:MAIN:Main_Init_Before_Delay
    Warn:CFG:CFG_InitAndLoad: Config crc or ident mismatch. Default config will be loaded.
    Info:CFG:CFG_SetDefaultLEDCorrectionTable: setting defaults
    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:Using SSID []
    Info:MAIN:Using Pass []
    Info:HTTP:TCP server listening
    Info:MQTT:MQTT_RegisterCallback called for bT rtl8721dx00000000/ subT rtl8721dx00000000/+/set
    Info:MQTT:MQTT_RegisterCallback called for bT obks/ subT obks/+/set
    Info:MQTT:MQTT_RegisterCallback called for bT cmnd/rtl8721dx00000000/ subT cmnd/rtl8721dx00000000/+
    Info:MQTT:MQTT_RegisterCallback called for bT cmnd/obks/ subT cmnd/obks/+
    Info:MQTT:MQTT_RegisterCallback called for bT rtl8721dx00000000/ subT rtl8721dx00000000/+/get
    Info:CMD:CMD_StartScript: started @startup at the beginning
    Info:CMD:CMD_StartScript: failed to get file autoexec.bat
    Info:MAIN:Main_Init_After_Delay done
    
  • #281 21599099
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    >>21598547
    nice
    have you seen AmebaD+ in devices?
    I'll probably grab a board from Ali if OpenRTLD+ is on the cards.
  • AmebaDplus port needs ImageTool and 0x08000000 flash offset

    #282 21600357
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    >>21599099
    No devices yet, but Tuya uses it in WR11-series modules.
    There are two available variants of AmebaDplus that are cheap.
    First is BW20, and that is what i use.
    Second is PKM8721DAF.

    I personally encountered a lot of problems.
    DHCP server in AP mode and DHCP client in STA mode is not working for me. But at least manual assignment for AP mode works fine.
    It connects to my AP fine, and i see that it gets DHCP address, but is ignored. Even if manually assigned in code, it still wasn't pingable.
    No LFS. Since i've not made any modification to SDK, there is simply no space for it.
    KV storage uses littlefs... Why??? Not EF, not FlashDB, but LittleFS. And it can't be disabled without SDK patches.
    WiFi api is very different.

    Didn't bother with rest OTA. Added untested HTTP.
    https://github.com/NonPIayerCharacter/OpenBK7...actions/runs/16133465728/artifacts/3482549917
    Needs imagetool from here: https://github.com/Ameba-AIoT/ameba-rtos/tree/release/v1.1/tools/ameba/ImageTool
    With this config file: https://github.com/Ameba-AIoT/ameba-rtos/blob...Devices/Profiles/AmebaDplus_FreeRTOS_NOR.rdev
    Write OBK binary at 0x08000000
    Log baud rate is 1500000.
  • #283 21600370
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    https://airtake-public-data-1254153901.cos.ap....com/smart/embed/pruduct/rtl8711daf_0.0.5.zip

    Added after 1 [hours] 23 [minutes]:

    insmod wrote:

    Realtek seem to have quite a few different tools...

    Added after 2 [minutes]:

    added https://github.com/openshwprojects/FlashTools/pull/9
  • ADVERTISEMENT
  • Helpful post

    Boot log confirms AmebaD Plus 8710_2M configuration

    #284 21601312
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    >>21600370
    KV_KEY_SEED is 8710_2M in rtl8711daf_0.0.5.zip\rtl8711daf_0.0.5_temp\rtl8711daf_os\component\soc\amebadplus\usrcfg\tuya_iot_config.h
    Boot log from km0_km4_app.bin in that archive
    ROM:[V1.1]
    FLASH RATE:1, Pinmux:0
    IMG1(OTA1) VALID, ret: 0
    IMG1 ENTRY[f8017d5:0]
    [BOOT-I] KM4 BOOT REASON: 0 
    [BOOT-I] KM4 CPU CLK: 260000000 Hz
    [BOOT-I] KM0 CPU CLK: 104000000 Hz
    [BOOT-I] PSRAM Ctrl CLK: 260000000 Hz 
    [BOOT-I] IMG1 ENTER MSP:[30009FE4]
    [BOOT-I] Build Time: Sep 11 2024 01:53:21
    [BOOT-I] IMG1 SECURE STATE: 1
    [FLASH-I] Flash ID: 20-40-16
    [FLASH-I] Flash Read 4IO
    [FLASH-I] FLASH HandShake[0x2 OK]
    [BOOT-I] KM0 XIP IMG[0c000000:51020]
    [BOOT-I] KM0 SRAM[20068000:1020]
    [BOOT-I] KM0 PSRAM[0c052040:20]
    [BOOT-I] KM0 ENTRY[20004d00:60]
    [BOOT-I] KM4 XIP IMG[0e000000:149e80]
    [BOOT-I] KM4 SRAM[2000b000:1b00]
    [BOOT-I] KM4 PSRAM[0e14b980:20]
    [BOOT-I] KM4 ENTRY[20004d80:40]
    [BOOT-I] IMG2 BOOT from OTA 1, Version: 1.1 
    [BOOT-I] Image2Entry @ 0xe000745 ...
    [APP-I] KM4 APP START 
    [LOCKS-I] KM0 init_retarget_locks
    [APP-I] VTOR: 30007000, VTOR_NS:30007000
    [APP-I] VTOR: 30007000, VTOR_NS:30007000
    [MAIN-I] IWDG refr[eAsPhP- Ion]! 
    IMG2 SECURE STAT[EM:A IN1-
    I] KM0 OS START 
    [CLK-I] [CAL4M]: delta:1 target:320 PPM: 3125 PPM_Limit:30000 
    [CLK-I] [CAL131K]: delta:19 target:2441 PPM: 7783 PPM_Limit:30000 
    [LOCKS-I] KM4 init_retarget_locks
    [MAIN-I] KM4 MAIN 
    [VER-I] AMEBA-RTOS SDK VERSION: 1.0.1
    [MAIN-I] File System Init Success
    [MAIN-I] KM4 START SCHEDULER 
    interface 0 is initialized
    interface 1 is initialized
    [WLAN-A] Init WIFI
    [WLAN-A] Band=2.4G&5G
    [WLAN-A] consume heap 19944 Bytes
    [WLAN-I] _init_thread(63), Available heap 288224
    [01-01 00:00:00 ty E][22a][uf_flash_file.c:140] magic 0xffffffff id1 65535  id2 1
    [01-01 00:00:00 ty E][22a][uf_flash_file.c:132] magic 0xffffffff id1 65535  id2 0
    [01-01 00:00:00 ty D][239][tal_thread.c:209] Thread:sys_timer Exec Start. Set to Running Stat 0x20023900
    [01-01 00:00:00 ty I][22a][tal_thread.c:185] thread_create name:sys_timer,stackDepth:8192,totalstackDepth:8192,priority:5
    [01-01 00:00:00 ty I][22a][tal_thread.c:185] thread_create name:wq_system,stackDepth:8192,totalstackDepth:16384,priority:3
    [01-01 00:00:00 ty I][22a][tal_thread.c:185] thread_create name:wq_highpri,stackDepth:8192,totalstackDepth:24576,priority:4
    [01-01 00:00:00 ty D][22a][tuya_svc_netmgr_linkage.c:86] link[9] is registered [0]
    [01-01 00:00:00 ty D][22a][tuya_svc_netmgr_linkage.c:86] link[2] is registered [1]
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:0
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:1
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:2
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:3
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:4
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:5
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:6
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:7
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:8
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:114] add new node,type:9
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:58] init watchdog, interval: 60
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:161] update type:7,period:20
    [01-01 00:00:00 ty D][22a][tuya_devos_health.c:491] watch_dog_interval:60, monitor_detect_interval:600
    [01-01 00:00:00 ty D][2c5][tal_thread.c:209] Thread:health_monitor Exec Start. Set to Running Stat 0x2002c520
    [01-01 00:00:00 ty D][241][tal_thread.c:209] Thread:wq_highpri Exec Start. Set to Running Stat 0x20024180
    [01-01 00:00:00 ty I][22a][tal_thread.c:185] thread_create name:health_monitor,stackDepth:4096,totalstackDepth:28672,priority:5
    [01-01 00:00:00 ty I][22a][mqc_app.c:490] mqc app init ...
    [01-01 00:00:00 ty D][22a][mqc_app.c:109] mq_pro:5 cnt:1
    [01-01 00:00:00 ty D][22a][mqc_app.c:109] mq_pro:31 cnt:2
    [01-01 00:00:00 ty D][22a][tuya_svc_online_log.c:291] svc online log init success
    [01-01 00:00:00 ty E][22a][log_seq.c:930] logseq empty
    [01-01 00:00:00 ty N][22a][tuya_device.c:133] < TuyaOS V:3.11.3 BS:40.00_PT:2.3_LAN:3.5_CAD:1.0.5_CD:1.0.0 >
    < BUILD AT:2025_01_14_23_27_06 BY aide.cheng FOR tuyaos-iot AT rtl8711daf >
    IOT DEFS < WIFI_GW:1 DEBUG:1 KV_FILE:0 LITTLE_END:1 SL:0 OPERATING_SYSTEM:98 RELIABLE_TRANSFER:0 >
    
    [01-01 00:00:00 ty N][22a][tuya_device.c:134] reset_reason:0
    [01-01 00:00:00 ty N][22a][tuya_device.c:135] rtl8711daf_common_user_config_ty sw ver:1.0.1
    [01-01 00:00:00 ty E][22a][simple_flash_protected.c:73] protected key data is not matched magic(0x3a2d3e45),crc32(0xe2d8782c)
    [01-01 00:00:00 ty N][22a][simple_flash.c:969] sf protected init err, need backup
    [01-01 00:00:00 ty N][22a][simple_flash.c:447] key_addr: 0x3d4000   block_sz 4096
    [01-01 00:00:00 ty E][22a][simple_flash.c:467] key data is not matched magic(0x3a2d3e45),crc32(0xe2d8782c)
    [01-01 00:00:00 ty E][22a][simple_flash.c:481] flash is encrypted or empty
    [01-01 00:00:00 ty N][22a][simple_flash.c:346] protected not valid
    [01-01 00:00:00 ty E][22a][simple_flash_app.c:344] create_flash_hand_and_init err 10
    [01-01 00:00:00 ty E][22a][tuya_ws_db.c:469] db init fails -1
    [01-01 00:00:00 ty E][22a][tuya_iot_com_api.c:88] db init fails -1
    [01-01 00:00:00 ty E][22a][ws_db_gw.c:84] wd_protected_read fails gw_bi -1
    [01-01 00:00:00 ty E][22a][mf_identify.c:163] ret:-1
    [01-01 00:00:00 ty N][22a][mf_test.c:334] mf identify init err -1
    [SERIAL-I] uart idx: 0
    [WIFI NOTICE]tuya_os_adapt_wifi_set_work_mode:2 now mode:5
    [01-01 00:00:00 ty N][22a][tuya_app_main.c:206] mf_init succ
    [01-01 00:00:00 ty E][22a][ws_db_gw.c:84] wd_protected_read fails gw_wsm -1
    [WIFI NOTICE]tuya_os_adapt_wifi_set_work_mode:1 now mode:2
    [WIFI ERROR]WWM_SNIFFER not support 
    PLT_E[tkl_wifi_set_cur_channel:823] 
    tkl_wifi_set_cur_channel , 823
    
    [01-01 00:00:01 ty N][22a][prod_test.c:350] cannot found prod ssid,ret:-6
    [01-01 00:00:01 ty E][1e0][ty_gfw_core.c:67] ret:-1
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    [WLAN-A] IPS in
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    [SERIAL-I] uart idx: 0
    

    This is what i get if BK7231N tuya config is flashed. 8710B is the same, but with different values. Ignored W800 and T3 configs (same as normal boot log).
    [01-01 00:00:00 ty E][22a][simple_flash_protected.c:73] protected key data is not matched magic(0x3a2d3e45),crc32(0xe2d8782c)
    [01-01 00:00:00 ty N][22a][simple_flash.c:969] sf protected init err, need backup
    [01-01 00:00:00 ty N][22a][simple_flash.c:447] key_addr: 0x3d4000   block_sz 4096
    [01-01 00:00:00 ty N][22a][simple_flash.c:533] get key:
    0xdb 0xe5 0xf5 0xde 0x2a 0x14 0x41 0x6a 0xbe 0x3e 0xfa 0x8d 0xb6 0x43 0xbe 0xf8 
    [01-01 00:00:00 ty E][22a][simple_flash_protected.c:128] protected key data is not matched magic(0x3a2d3e45),crc32(0xe2d8782c)
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=422863
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0xb30f7ee, block_id=27415, crc32=732549229
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=422863
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0xb30f7ee, block_id=27415, crc32=732549229
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=422863
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0xb30f7ee, block_id=27415, crc32=732549229
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=422863
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0xb30f7ee, block_id=27415, crc32=732549229
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=422863
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0xb30f7ee, block_id=27415, crc32=732549229
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=422863
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0xb30f7ee, block_id=27415, crc32=732549229
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=422863
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0xb30f7ee, block_id=27415, crc32=732549229
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=422863
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0xb30f7ee, block_id=27415, crc32=732549229
    [01-01 00:00:00 ty N][22a][simple_flash.c:1632] block head check error, expect:magic=0x98761234, or magic=0x135726ab, max block_id=[0, 15], crc32=454569
    [01-01 00:00:00 ty N][22a][simple_flash.c:1635] block head check error, real:magic=0x7835be01, block_id=13643, crc32=-762897667
    [01-01 00:00:00 ty N][22a][simple_flash.c:1116] block head check error, expect:magic=0x135726ab, max block_id=[0], 23], crc32=454569
    [01-01 00:00:00 ty N][22a][simple_flash.c:1118] block head check error, real:magic=0x7835be01, block_id=13643, crc32=-762897667
    [01-01 00:00:00 ty N][22a][simple_flash.c:1116] block head check error, expect:magic=0x135726ab, max block_id=[0], 23], crc32=473271
    [01-01 00:00:00 ty N][22a][simple_flash.c:1118] block head check error, real:magic=0xe04e0382, block_id=57331, crc32=248153529
    [01-01 00:00:00 ty N][22a][simple_flash.c:1173] kv not valid, use protected to recover
    [01-01 00:00:00 ty E][22a][simple_flash_app.c:344] create_flash_hand_and_init err 6
    [01-01 00:00:00 ty E][22a][tuya_ws_db.c:469] db init fails -1
    [01-01 00:00:00 ty E][22a][tuya_iot_com_api.c:88] db init fails -1
    [01-01 00:00:00 ty E][22a][ws_db_gw.c:84] wd_protected_read fails gw_bi -1
    [01-01 00:00:00 ty E][22a][mf_identify.c:163] ret:-1
    [01-01 00:00:00 ty N][22a][mf_test.c:334] mf identify init err -1
    [SERIAL-I] uart idx: 0
    [WIFI NOTICE]tuya_os_adapt_wifi_set_work_mode:2 now mode:5
    [01-01 00:00:00 ty N][22a][tuya_app_main.c:206] mf_init succ
    [01-01 00:00:00 ty E][22a][ws_db_gw.c:84] wd_protected_read fails gw_wsm -1
    [WIFI NOTICE]tuya_os_adapt_wifi_set_work_mode:1 now mode:2
    [WIFI ERROR]WWM_SNIFFER not support 
    PLT_E[tkl_wifi_set_cur_channel:823] 
    tkl_wifi_set_cur_channel , 823
    
    [01-01 00:00:01 ty N][22a][prod_test.c:350] cannot found prod ssid,ret:-6
    


    On another note, i fixed DHCP for OBK. It turns out enabling LWIP_NETIF_HOSTNAME breaks it, first time i've seen it.

    Added after 2 [hours] 12 [minutes]:

    HTTP OTA works.
    AmebaDplus and AmebaLite (8720E) builds:
    https://github.com/NonPIayerCharacter/OpenBK7231T_App/actions/runs/16159241985

    BW20-12F-Kit pins:
    
      "pins": {
        "49": "PWM;2",
        "50": "PWM;0",
        "51": "PWM;1",
        "52": "WifiLED;0",
        "53": "LED;3"
      },
    
  • Testing Tuya config flashes to infer KV_KEY_SEED values

    #285 21601398
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    insmod wrote:
    This is what i get if BK7231N tuya config is flashed. 8710B is the same, but with different values. Ignored W800 and T3 configs (same as normal boot log).

    very interesting. does this help with determining alternative KV_KEY_SEED values in other Tuya devices? What is the significance of these findings and the method used here cutting in tuya config to see how it errors or not?

    I have all Tuya SDK zips downloaded (that I've found) so could set an extensive search going for all files with KV_KEY_SEED in if you think that would be of value.
  • #286 21601404
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    >>21601398
    Doubtful, since it still failed at BK config decryption.
    There is probably something added on top of that.
  • #287 21601560
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    yep, sure.

    Have you tried any of the read scripts on AmebaDplus and AmebaLite to see if we can take backups?
  • #288 21601576
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    >>21601560
    Don't have AmebaLite.
    RTL8720D script with replaced floader failed.
    Protocol is the same (xmodem), just need to figure out internal parameters for python script.
  • #289 21601607
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    OK.

    YourCee resources for their BW20-12F-Kit

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    Attachments:
    • BW20 Combo-AT 固件最新版本(4MB flash) V4.18_P1.0.6 下载 (固件料号2775.zip (2.22 MB) You must be logged in to download this attachment.
    • BW20 低功耗测试固件.zip (555.52 KB) You must be logged in to download this attachment.
    • BW20-12F-Kit 开发板规格书(英文).pdf (945.79 KB) You must be logged in to download this attachment.
    • BW20 二次开发文档.zip (30.73 MB) You must be logged in to download this attachment.
    • BW20-12F-Kit 开发板原理图.pdf (457.79 KB) You must be logged in to download this attachment.
  • REST OTA added with LFS and hostname fixes

    #290 21602572
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    Pull request opened: https://github.com/openshwprojects/OpenBK7231T_App/pull/1718
    Implemented REST OTA, but not recommended for use - while it works for me, it depends on several uncertain things - when request is received, most of the times the body is already partially received - including POST header. So it is skipped. Plus there are some magic offset values (like writelen -= RevHdrLen + 5 - 384).

    LFS is at the end of APP1 partition, so if OBK grows too much - LFS would overwrite code.
    Fixed hostname, it seems that LWIP_NETIF_HOSTNAME wasn't applied globally. Same with TCP_MSL.

    And what's with simulator build? (/home/runner/work/_temp/4e33c5d8-060d-43f9-8b5b-9e55e860afb2.sh: line 2: 3513 Aborted (core dumped) ./build/win_main -runUnitTests 2)

    Added after 2 [hours] 11 [minutes]:

    Now including ESP BL0937 fix (tested on ESP32-C3)
  • #291 21602765
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    would you expect that fix to apply to ESP8266?
    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
  • MQTT discovery fails on BL0937 device

    #293 21602789
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    better. I haven't calib though.

    this is with cheap soldering iron powered on.
    seems to have same spikes as with new BK SDK(?), though it's not so obvious until later in this animated gif.

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

    Added after 14 [minutes]:

    insmod wrote:
    What about MQTT?


    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    connected but discovery eventually fails with

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?

    Added after 1 [hours] 16 [minutes]:

    @DeDaMrAz have you got any ESP8266 devices with BL0937 in?
  • Proposes HAL pin-change counter and counter GPIO role

    #294 21602923
    p.kaczmarek2
    Moderator Smart Home
    Posts: 14805
    Help: 659
    Rate: 12972
    Maybe it's a good time to revisit the "pin change counter" HAL idea? Move out setup from drv_bl0937.c to HAL and then introduce extra gpio role - "Counter".

    insmod wrote:

    And what's with simulator build? (/home/runner/work/_temp/4e33c5d8-060d-43f9-8b5b-9e55e860afb2.sh: line 2: 3513 Aborted (core dumped) ./build/win_main -runUnitTests 2)

    Fixed, it was my string buffer issue in my test code on Windows.
    Helpful post? Buy me a coffee.
  • Home Assistant discovery works on RTL8720DN

    #295 21603512
    insmod
    Level 31  
    Posts: 1432
    Help: 168
    Rate: 455
    Discovery works for me
    Info:HTTP:HASS counts: 0 rels, 0 pwms, 1 inps, 0 excluded
    Debug:HASS:hass_init_device_info=0x40109ae4
    Debug:HASS:root=0x4010a3dc
    Info:MQTT:Queued topic=homeassistant/binary_sensor/OpenESP8266_B507EDBD_binary_sensor_0/config, 1 items in queue
    Debug:HASS:hass_init_device_info=0x40109ae4
    Debug:HASS:root=0x4010a3dc
    Info:MQTT:Queued topic=homeassistant/sensor/OpenESP8266_B507EDBD_rssi/config, 2 items in queue
    Debug:HASS:hass_init_device_info=0x40109ae4
    Debug:HASS:root=0x4010a3dc
    Info:MQTT:Queued topic=homeassistant/sensor/OpenESP8266_B507EDBD_uptime/config, 3 items in queue
    Debug:HASS:hass_init_device_info=0x40109ae4
    Debug:HASS:root=0x4010a3dc
    Info:MQTT:Queued topic=homeassistant/sensor/OpenESP8266_B507EDBD_build/config, 4 items in queue
    Debug:HASS:hass_init_device_info=0x40109ae4
    Debug:HASS:root=0x4010a3dc
    Info:MQTT:Queued topic=homeassistant/sensor/OpenESP8266_B507EDBD_ssid/config, 5 items in queue
    Debug:HASS:hass_init_device_info=0x40109ae4
    Debug:HASS:root=0x4010a3dc
    Info:MQTT:Queued topic=homeassistant/sensor/OpenESP8266_B507EDBD_ip/config, 6 items in queue
    Info:MQTT:Channel has changed! Publishing 1 to channel 0 
    Info:MQTT:Publishing val 1 to esp8266B507EDBD/0/get retain=0
    Info:MAIN:Time 71, idle 0/s, free 18140, MQTT 1(4), bWifi 1, secondsWithNoPing 1, socks 0/0 
    Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic esp8266B507EDBD/0/get
    Debug:MQTT:channelSet topic 1073659888 with arg 1
    Info:MAIN:Time 72, idle 0/s, free 18140, MQTT 1(4), bWifi 1, secondsWithNoPing 2, socks 0/0 
    Info:MQTT:Publishing val (316 bytes) to homeassistant/binary_sensor/OpenESP8266_B507EDBD_binary_sensor_0/config retain=1
    Info:MQTT:Publishing val (387 bytes) to homeassistant/sensor/OpenESP8266_B507EDBD_rssi/config retain=1
    Info:MQTT:Publishing val (389 bytes) to homeassistant/sensor/OpenESP8266_B507EDBD_uptime/config retain=1
    Info:MAIN:Time 73, idle 0/s, free 18316, MQTT 1(4), bWifi 1, secondsWithNoPing 3, socks 0/0 
    Info:MQTT:Publishing val (316 bytes) to homeassistant/sensor/OpenESP8266_B507EDBD_build/config retain=1
    Info:MQTT:Publishing val (347 bytes) to homeassistant/sensor/OpenESP8266_B507EDBD_ssid/config retain=1
    Info:MQTT:Publishing val (331 bytes) to homeassistant/sensor/OpenESP8266_B507EDBD_ip/config retain=1
    Info:MAIN:Time 74, idle 0/s, free 18316, MQTT 1(4), bWifi 1, secondsWithNoPing 4, socks 0/0 
    Info:MQTT:Channel has changed! Publishing 1 to channel 0 
    Info:MQTT:Publishing val 1 to esp8266B507EDBD/0/get retain=0
    Info:MAIN:Time 75, idle 0/s, free 18316, MQTT 1(4), bWifi 1, secondsWithNoPing 5, socks 0/0 
    
  • BL0937 driver triggers crashes on new board

    #296 21603573
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    oh yeh, me too on new board with no bl0937 started. BUT with BL0937 driver started:

    Code: Text
    Log in, to see the code
  • #297 21603575
    p.kaczmarek2
    Moderator Smart Home
    Posts: 14805
    Help: 659
    Rate: 12972
    What about with BL0942 driver started?
    Helpful post? Buy me a coffee.
  • BP5758D works despite missing bl0942 driver

    #298 21603580
    divadiow
    Level 38  
    Posts: 5243
    Help: 451
    Rate: 921
    not in build currently
    Code: Text
    Log in, to see the code


    but trying with a driver running, BP5758D, that works

    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
  • rtltool.py flash failure on BW16E with RTL8720DN

    #300 21604605
    p.kaczmarek2
    Moderator Smart Home
    Posts: 14805
    Help: 659
    Rate: 12972
    @insmod @divadiow Guys, regarding rtltool.py and BW16E board:
    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    Was this ever working?
    
    python rtltool.py -p COM3 -b 1500000 wf 0 BW16E-RTL8720DN-factory-p.kaczmarek-20250712.bin
    pause
    

    It gives me:
    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    It fails every time.

    That being said, I started porting this to C# so we can add it to our flasher, and without SetFlashStatus, it seems to work both in my code and in Python???
    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    Well, checksum fails, so first obvious idea was that flash was still write protected and it didn't write, but, however...
    This is factory dump:
    RTL8720DN, RTL8710B, RTL8710BX Compatibility with OpenBeken?
    This is OBK RTL8720D OpenRTL8720D_1.18.135.bin ( not DN):
    
    #[MODULE_BOOT-LEVEL_INFO]:IMG1 ENTER ROMSUB:2
    [MODULE_BOOT-LEVEL_INFO]:OTA2 USE
    [MODULE_BOOT-LEVEL_INFO]:IMG2 DATA[0xc014830:9376:0x83000]
    [MODULE_BOOT-LEVEL_INFO]:IMG2 SIGN[RTKWin(8300c)]
    [MODULE_BOOT-LEVEL_INFO]:IMG2 ENTRY[0x83000:0xc002825]
    [MODULE_BOOT-LEVEL_INFO]:KM0 BOOT_IMG2 BOOT REASON: 0 
    calibration_ok:[2:19:11] 
    
    [MODULE_BOOT-LEVEL_INFO]:IMG1 ENTER MSP:[1007fffc]
    
    [MODULE_BOOT-LEVEL_INFO]:IMG2 DATA[0xe0d09b0:105824:0x10005000]
    
    [MODULE_BOOT-LEVEL_INFO]:IMG2 SIGN[RTKWin(1000500c)]
    
    [MODULE_BOOT-LEVEL_INFO]:IMG2 ENTRY[0x10005000:0xe0242c5]
    
    [MODULE_BOOT-LEVEL_INFO]:Start NonSecure @ 0xe0242c4 ...
    
    [MODULE_BOOT-LEVEL_INFO]:KM4 BOOT REASON: 0 
    
    
    at version:release/V4.18_P2.40.1 sdk version:amebad_v6.2C firmware version:release/V4.18_P6.3.1(Nov 17 2023-11:54:16)
    
    [AI_LoadConfigFromFlash()-670]load config success
    [AI_ComboInit()-212]load config ret=0
    [AI_ComboInit()-215]init AT uart ret=0
    interface 0 is initialized
    
    interface 1 is initialized
    
    
    
    Initializing WIFI ...[AI_WatchdogThread()-645]AI_HalWatchdogRefresh start
    [AI_WifiInitCallbak()-1058]
    
    
    
    WIFI initialized
    
    [wifi_set_country_code()-967]country code=5 value=48
    
    
    
    init_thread(58), Available heap 0x29c60trace task is needed to print trace log
    
    trace task is needed to print trace log
    
    ble_common_init 0 
    
    trace_uart_init: TRACE OPEN
    
    ***********this is BT NORMAL DRIVER*******,
    
     this cut is AmebaD C CUT
    BT BUILD Date: 2023/11/17-11:53:25 
    
    ==logic_efuse:==
    
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ff:
    
    ==bt phy_efuse 0x120~0x12F:==
    
     
    
    0:
    
    9e:
    
    fe:
    
    f8:
    
    0:
    
    4:
    
    0:
    
    14:
    
    19:
    
    4:
    
    ff:
    
    f:
    
    23:
    
    24:
    
    ff:
    
    ff:
    
    ==bt phy_efuse 0x1FD~0x1FF:==
    
     
    
    ff:
    
    ff:
    
    ff:BT FW LOG OPEN
    
    BT Reset...
    
    salve_add_server 
    
    GAP_INIT_STATE_STACK_READY 
    
    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 0xf8,
    
    the IQK_yy  data is 0x4,
    
    the QDAC  data is 0x23,
    
    the IDAC  data is 0x24,
    
    hci_read_rom_check: rom_version 0x0002, bt_hci_chip_id 0x0003
    
    
    We use DEBUG VAL:0x0
    
    
    We use BT ROM OTA1 PATCH ADDRESS:0x80f8000
    
    
    we use single patch
    
    
    not support single patch on rom
    
    
    
    hci_read_rom_check: error operate
    
    
    

    Why not boot? It should work as seen in post 231?
    https://www.elektroda.com/rtvforum/topic4093142-210.html#21448411

    And later I can restore factory flash:
    
    
    #calibration_ok:[2:19:11] 
    
    
    
    
    
    
    
    at version:release/V4.18_P2.40.1 sdk version:amebad_v6.2C firmware version:release/V4.18_P6.3.1(Nov 17 2023-11:54:16)
    
    
    
    
    
    [AI_LoadConfigFromFlash()-670]load config success
    [AI_ComboInit()-212]load config ret=0
    [AI_ComboInit()-215]init AT uart ret=0
    interface 0 is initialized
    
    interface 1 is initialized
    
    
    
    Initializing WIFI ...[AI_WatchdogThread()-645]AI_HalWatchdogRefresh start
    [AI_WifiInitCallbak()-1058]
    
    
    
    WIFI initialized
    
    [wifi_set_country_code()-967]country code=5 value=48
    
    
    
    init_thread(58), Available heap 0x29c60trace task is needed to print trace log
    
    trace task is needed to print trace log
    
    ble_common_init 0 
    
    
    
    BT BUILD Date: 2023/11/17-11:53:25 
    
    BT Reset...
    
    salve_add_server 
    
    GAP_INIT_STATE_STACK_READY 
    
    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 0xf8,
    
    the IQK_yy  data is 0x4,
    
    the QDAC  data is 0x23,
    
    the IDAC  data is 0x24,
    
    hci_read_rom_check: rom_version 0x0002, bt_hci_chip_id 0x0003
    
    hci_rtk_parse_config: BT ADDRESS 11 28 36 12 51 89, use the default config
    
    
    
     WRITE  physical FLATK=tx_flatk=fff 
    
    
    
    hci_tp_config:BT INIT success 7
    
    Start upperStack
    
    app_handle_gap_msg: subtype 1
    
    salve_handle_dev_state_evt: init state 1, adv state 0, cause 0x0
    
    
    [BLE peripheral] GAP stack ready
    
    
    app_handle_gap_msg: subtype 1
    
    salve_handle_dev_state_evt: init state 1, adv state 1, cause 0x0app_handle_gap_msg: subtype 1
    
    salve_handle_dev_state_evt: init state 1, adv state 2, cause 0x0
    
    
    GAP adv start
    
    ble_common_init success 
    
    [RTL_HalBleMacInit()-304]start ble success
    [RTL_HalBleMacInit()-320]BLE MAC init:895112362811
    
    [BLE Peripheral]BT Stack deinitalized
    
    [RTL_HalBleMacInit()-326]stop ble success
    
    
    
    WIFI is already running[AI_ProcessThread()-1108]wifi start success
    
    
    
    [rltk_wlan_statistic] tx stat: tx_packets=0, tx_dropped=0, tx_bytes=0
    
    
    [rltk_wlan_statistic] rx stat: rx_packets=0, rx_dropped=0, rx_bytes=0, rx_overflow=0
    
    
    [rltk_wlan_statistic] rx stat: rx_reorder_drop_cnt=0, rx_reorder_timeout_cnt=0
    
    
    [rltk_wlan_statistic] min_free_heap_size=144928, current heap free size=174688
    
    
    [rltk_wlan_statistic] max_skbbuf_used_num=0, skbbuf_used_num=0
    
    
    [rltk_wlan_statistic] max_skbdata_used_num=0, skbdata_used_num=0
    
    
    [rltk_wlan_statistic] max_timer_used_num=31[AI_AutoConnectOnboot()-973]wifi auto connect off
    [AI_AutoConnectOnboot()-1030]ble auto connect off
    
    
    Helpful post? Buy me a coffee.

Topic summary

LABEL_AI_GENERATED
The discussion confirms that OpenBeken support applies to the RTL8720CF-based Ameba Z2 family, including WBR3 and BW15 modules, but not to RTL8710BX, which belongs to a different AmebaZ/Ameba1 family and is unsupported by the RTL87x0C port. The port initially provides Wi‑Fi, GPIO, flash config/vars, LittleFS, WDT, OTA, and UART support, while several issues are investigated and fixed during development, including heap drain in TCP servers, MQTT authorization, PWM reboot freezes, static IP, and timing-sensitive sensor drivers such as DHT11 and DS18B20. Flashing procedures, UART pinouts, and tool compatibility are also discussed, including use of PG Tool, CH340G, and later BK7231GUIFlashTool for read/write support. The thread evolves into broader RTL87x0C port testing, Tuya config extraction, partition layout adjustments, and validation on WBR3/BW15 hardware.
AI summary based on the discussion. May contain errors.
ADVERTISEMENT