You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The device looks hardware wise awfully similar to the Theengs Bridge. So I used that configuration as the starting base and adapted the pinout and LEDs to match the GL.iNet one.
config
[env:gl-s10]platform = ${com.esp32_platform}
board = esp32dev
extra_scripts = ${com-esp32.extra_scripts}
board_build.partitions = min_spiffs.csv
lib_deps =
${com-esp32.lib_deps}
${libraries.ble}
${libraries.decoder}
build_flags =
${com-esp32.build_flags}
'-DZgatewayBT="BT"'; use the power led as inverted error (on when no error is present)'-DLED_ERROR=14''-DLED_ERROR_ON=1''-DLED_INFO=32''-DLED_INFO_ON=0''-DLED_SEND_RECEIVE=12''-DLED_SEND_RECEIVE_ON=0''-DTRIGGER_GPIO=33''-DESP32_ETHERNET=true''-DETH_PHY_TYPE=ETH_PHY_IP101''-DETH_PHY_ADDR=1''-DETH_PHY_POWER=5''-DETH_PHY_MDC=23''-DETH_PHY_MDIO=18''-DETH_CLK_MODE=ETH_CLOCK_GPIO0_IN''-DAttemptBLEConnect=false''-DUSE_MAC_AS_GATEWAY_NAME''-DGATEWAY_MANUFACTURER="GL.iNet"''-DGATEWAY_MODEL="GL-S10"''-UZwebUI="WebUI"'; Disable WebUIcustom_description = IoT gateway device that supports BLE and Wi-Fi
custom_hardware = GL.iNet GL-S10 gateway ethernet
If that would have worked, I had made a pull request, but unfortunately we're here at the issues section :)
The compilation goes alright, and on boot the device recognizes the ethernet interface. It does also bring the physical link up.
However it does not seem to get a IP from DHCP, and will soon start complaining about "insufficient TX buffer size", which happens when the device is not connected.
logs
rst:0x1 (POWERON_RESET),boot:0x12 (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:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13192
load:0x40080400,len:3028
entry 0x400805e4
N:
************* WELCOME TO OpenMQTTGateway **************
[ 135][E][Preferences.cpp:50] begin(): nvs_open failed: NOT_FOUND
N: SYS config not found
N: OpenMQTTGateway Version: version_tag
N: no config file found defining default values
N: Ethernet Connected
N: No config in flash, launching wifi manager
N: OTA Hostname: OMG_1097.local
N: Attempting Wifi connection with saved AP: 0
[ 5889][E][WiFiSTA.cpp:317] begin(): connect failed! 0x300a
N: Attempting Wifi connection with saved AP: 1
[ 6896][E][WiFiSTA.cpp:317] begin(): connect failed! 0x300a
N: Attempting Wifi connection with saved AP: 2
[ 7903][E][WiFiSTA.cpp:317] begin(): connect failed! 0x300a
N: Attempting Wifi connection with saved AP: 3
[ 8910][E][WiFiSTA.cpp:317] begin(): connect failed! 0x300a
N: Attempting Wifi connection with saved AP: 4
[ 9917][E][WiFiSTA.cpp:317] begin(): connect failed! 0x300a
N: Connect your phone to WIFI AP: OMG_1097 with PWD:
*wm:AutoConnect
*wm:No wifi saved, skipping
*wm:AutoConnect: FAILED
*wm:StartAP with SSID: OMG_1097
*wm:AP IP address: 192.168.4.1
*wm:Starting Web Portal
E (79124) esp.emac: emac_esp32_transmit(229): insufficient TX buffer size
E (94125) esp.emac: emac_esp32_transmit(229): insufficient TX buffer size
Any pointers to how I can troubleshoot this further would be welcome.
I did test this device with ESPhome which did work with the ethernet device. I don't know if it helps any, but that boot log is more verbose on the phy side:
[D][esp-idf:000]: I (1281) system_api: Base MAC address is not set
[D][esp-idf:000]: I (1289) system_api: read default base MAC address from EFUSE
[D][esp-idf:000]: I (1302) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07
[D][esp32_ble:042]: BLE setup complete
[D][esp32_ble_tracker:246]: Starting scan...
[C][ethernet:028]: Setting up Ethernet...
[D][esp-idf:000]: I (2261) esp_eth.netif.netif_glue: aa:bb:cc:dd:ee:ff
[D][esp-idf:000]: I (2262) esp_eth.netif.netif_glue: ethernet attached to netif
[I][ethernet:108]: Starting ethernet connection
The text was updated successfully, but these errors were encountered:
Hi,
I've been trying to get OMG (latest dev 46160c6) running on a GL.iNet GL-S10 device. This uses a ESP32-WROOM under the hood, together with a IP101 ethernet phy.
Full specs: https://docs.gl-inet.com/iot/en/ble_proxy/gl-s10/hardware/
The device looks hardware wise awfully similar to the Theengs Bridge. So I used that configuration as the starting base and adapted the pinout and LEDs to match the GL.iNet one.
config
If that would have worked, I had made a pull request, but unfortunately we're here at the issues section :)
The compilation goes alright, and on boot the device recognizes the ethernet interface. It does also bring the physical link up.
However it does not seem to get a IP from DHCP, and will soon start complaining about "insufficient TX buffer size", which happens when the device is not connected.
logs
Any pointers to how I can troubleshoot this further would be welcome.
I did test this device with ESPhome which did work with the ethernet device. I don't know if it helps any, but that boot log is more verbose on the phy side:
The text was updated successfully, but these errors were encountered: