I have been trying to program a Wireless Tag WT32-ETH01 with ESPHome to create a Bluetooth proxy.
I used this thread as my reference for programming the chip. And the ESPHome configuration from here.
I confirmed the configuration for the ethernet configuration for the WT32-ETH01 here.
I have tried programming the device “plug into this computer” and directly plugged into the “Blue”.
It appears to compile and program correctly.
I power down the board.
I remove the programing jumper on GPIO01
I connect and eithernet cable.
I power up the chip via the USB to TTL programmer.
I don’t see the device on the network
If I try to look at the logs via either connection, I get something like shown below.
It scrolls similar for a few seconds then locks up. I have to restart the ESPHome add-on.
[17:12:46]rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[17:12:46]configsip: 0, SPIWP:0xee
[17:12:46]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[17:12:46]mode:QIO, clock div:1
[17:12:46]load:0x3fff0030,len:6608
[17:12:46]load:0xb0f45050,len:1481642069
[17:12:46]1162 mmu set 00010000, pos 00010000
[17:12:46]1162 mmu set 00020000, pos 00020000
[17:12:46]1162 mmu set 00030000, pos 00030000
[17:12:46]1162 mmu set 00040000, pos 00040000
[17:12:46]1162 mmu set 00050000, pos 00050000
[17:12:46]1162 mmu set 00060000, pos 00060000
[17:12:46]1162 mmu set 00070000, pos 00070000
[17:12:46]1162 mmu set 00080000, pos 00080000
[17:12:46]1162 mmu set 00090000, pos 00090000
[17:12:46]1162 mmu set 000a0000, pos 000a0000
[17:12:46]1162 mmu set 000b0000, pos 000b0000
[17:12:46]1162 mmu set 000c0000, pos 000c0000
[17:12:46]1162 mmu set 000d0000, pos 000d0000
[17:12:46]1162 mmu set 000e0000, pos 000e0000
[17:12:46]1162 mmu set 000f0000, pos 000f0000
[17:12:46]1162 mmu set 00100000, pos 00100000
[17:12:46]1162 mmu set 00110000, pos 00110000
[17:12:46]1162 mmu set 00120000, pos 00120000
[17:12:46]1162 mmu set 00130000, pos 00130000
[17:12:46]1162 mmu set 00140000, pos 00140000
[17:12:46]1162 mmu set 00150000, pos 00150000
[17:12:46]1162 mmu set 00160000, pos 00160000
[17:12:46]ets Jun 8 2016 00:22:57
[17:12:46]
[17:12:46]rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
What I’ve tried:
#1, I purchased a new FTDI adapter and a new WT32-ETH01 and had the same results as the first try.
#2 I commented out the esp32_ble_tracker: section of the config.
Once again, it appeared to program properly.
When the logs are displayed, it repeats this over and over.
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:QIO, clock div:1
load:0x3fff0030,len:6652
ho 0 tail 12 room 4
load:0x0242f03d,len:34879234
ets Jun 8 2016 00:22:57
Again, it I let this run it locks up the ESPHome page.
#3 I commented out the button: section
It appeared to program properly.
The logs repeated the same as the initial output as above continuously
#4 I commented out both the dashboard_import: and bluetooth_proxy: sections. It should do nothing now.
It appeared to program normally.
The logs repeated the same as the initial output as above continuously
#5 try pulling IO2 low to program. See here:
Same resutls as the first try
#6 try adding to ethernet configuration
# Optional manual IP
manual_ip:
static_ip: 192.168.1.59
gateway: 192.168.1.1
subnet: 255.255.255.0
Same results as the first try
My config file:
# Https://Github.Com/Esphome/Firmware/Blob/Main/Bluetooth-Proxy/Wt32-Eth01.Yaml
substitutions:
name: bluetooth-proxy
friendly_name: Bluetooth Proxy
esphome:
name: ${name}
friendly_name: ${friendly_name}
name_add_mac_suffix: true
project:
name: esphome.bluetooth-proxy
version: "1.0"
esp32:
board: wt32-eth01
framework:
type: esp-idf
ethernet:
type: LAN8720
mdc_pin: GPIO23
mdio_pin: GPIO18
clk_mode: GPIO0_IN
phy_addr: 1
power_pin: GPIO16
# Enable logging
logger:
# Enable Home Assistant API
api:
encryption:
key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
ota:
password: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
dashboard_import:
package_import_url: github://esphome/firmware/bluetooth-proxy/wt32-eth01.yaml@main
esp32_ble_tracker:
scan_parameters:
interval: 1100ms
window: 1100ms
active: true
bluetooth_proxy:
active: true
button:
- platform: safe_mode
name: Safe Mode Boot
entity_category: diagnostic