Thanks for fast answer, however ..
1. if they are logs that can never be off a little bit less professional
, especially if someone wanted to use this port for another purpose
2. In this situation ets_uart_printf only introduces confusion, especially eg. as it do not use the function uart_tx_one_char from uart driver
3. in 80% of cases wdt working properly, but in the rest of the log looks like below - and the system hangs. Valid port level (MTDO: 0, GPIO0: 1, GPIO2: 1) was checked more than twice
btw. boot mode:(3,7) - 3 means that MTDO: 0, GPIO0: 1, GPIO2: 1 are correct, yes ??
ets Jan 8 2013,rst cause:4, boot mode:(3,7)
wdt reset
load 0x40100000, len 27964, room 16
tail 12
chksum 0x3b
ho 0 tail 12 room 4
load 0x3ffe8000, len 2524, room 12
tail 0
chksum 0xb9
load 0x3ffe89e0, len 4420, room 8
tail 12
chksum 0x9e
csum 0x9e
any additional suggestions?
In total, ESP8266X a very cool system 
Statistics: Posted by mariuszb — Fri Jun 19, 2015 2:37 am
]]>