Wdt reset... too many of them

[traderlopez]

I hope I can get some help with this because it is taking me too long to debug it.

At this time there is only one device in the mesh network, which connects to a server, so it is ONLINE and sends information to the server each second in case there is information to be sent. The information is not blocking, because it is received from serial port and copied to an auxiliary array, where it is got by the sending timer callback function.

I am experiencing a lot of wdt resets. They don't seem to have anything to do with the transmission code because there are no debug strings around the wdt. They follow more or less the next pattern:

dhcp client start...
ip:192.168.0.101,mask:255.255.255.0,gw:192.168.0.1
Got IP, IP:192.168.0.101Mask:255.255.255.0GW:192.168.0.1
bcn 0
del if1
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
espconn_mesh_connect, ip:192.168.0.100,rport:7000, port:35958
espconn_mesh_pack_connect, idx:0, 12074616
rip:192.168.0.100rp:7000
con_cb IP:192.168.0.100 rp = 7000, lp = 35958
mesh_enable_cb
rip:192.168.0.100rp:7000, lp:35958
esp_mesh_con_cb

ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 1396, room 16
tail 4
chksum 0x89
load 0x3ffe8000, len 776, room 4
tail 4
chksum 0xe8
load 0x3ffe8308, len 540, room 4
tail 8
chksum 0xc0
csum 0xc0

2nd boot version : 1.4(b1)
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size & Map: 8Mbit(512KB+512KB)
jump to run user1 @ 1000

ESP-TOUCH FLOW INIT...
ESP-TOUCH SET STATION MODE ...
SC version: V2.5.4

[ESP_Alen]

I hope I can get some help with this because it is taking me too long to debug it.

At this time there is only one device in the mesh network, which connects to a server, so it is ONLINE and sends information to the server each second in case there is information to be sent. The information is not blocking, because it is received from serial port and copied to an auxiliary array, where it is got by the sending timer callback function.

I am experiencing a lot of wdt resets. They don't seem to have anything to do with the transmission code because there are no debug strings around the wdt. They follow more or less the next pattern:

dhcp client start...
ip:192.168.0.101,mask:255.255.255.0,gw:192.168.0.1
Got IP, IP:192.168.0.101Mask:255.255.255.0GW:192.168.0.1
bcn 0
del if1
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
espconn_mesh_connect, ip:192.168.0.100,rport:7000, port:35958
espconn_mesh_pack_connect, idx:0, 12074616
rip:192.168.0.100rp:7000
con_cb IP:192.168.0.100 rp = 7000, lp = 35958
mesh_enable_cb
rip:192.168.0.100rp:7000, lp:35958
esp_mesh_con_cb

ets Jan 8 2013,rst cause:4, boot mode:(3,7)

wdt reset
load 0x40100000, len 1396, room 16
tail 4
chksum 0x89
load 0x3ffe8000, len 776, room 4
tail 4
chksum 0xe8
load 0x3ffe8308, len 540, room 4
tail 8
chksum 0xc0
csum 0xc0

2nd boot version : 1.4(b1)
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size & Map: 8Mbit(512KB+512KB)
jump to run user1 @ 1000

ESP-TOUCH FLOW INIT...
ESP-TOUCH SET STATION MODE ...
SC version: V2.5.4

WDT reset means system is halt.
Please describe the detail task did in esp_mesh_con_cb.