Hi
1. How to switch off debug info form libnet80211 ?
eg.
add 0
aid 5
pm open phy_2,type:2 0 0
cnt
2. os_printf vs ets_uart_print - can we use them simultaneously ?
3. Is wdt working ? I have only info "wdt reset" but ESP12 module stay in this state, there is no real reset
4. why when starting ESP up so much garbage is sent to the serial port ?
Thanks
Mariusz
serial us debug, wdt reset
Re: serial us debug, wdt reset
Postby ESP_Faye » Tue Jun 16, 2015 4:25 pm
Hi,
1. you can call system_set_os_print(0); to disable all os_printf log except the ROM log (startup log)
2. we recommend to use os_printf
3. please make sure that your hardware settings is correct.
While downloading, it is MTDO: 0, GPIO0: 0, GPIO2: 1
While boot up from flash, it is MTDO: 0, GPIO0: 1, GPIO2: 1
4. it is the ROM log (startup log) we can't remove or disable it . But you could call system_uart_swap to use MTCK & MTDO as UART0
Thanks for your interest in ESP8266 !
1. you can call system_set_os_print(0); to disable all os_printf log except the ROM log (startup log)
2. we recommend to use os_printf
3. please make sure that your hardware settings is correct.
While downloading, it is MTDO: 0, GPIO0: 0, GPIO2: 1
While boot up from flash, it is MTDO: 0, GPIO0: 1, GPIO2: 1
4. it is the ROM log (startup log) we can't remove or disable it . But you could call system_uart_swap to use MTCK & MTDO as UART0
Thanks for your interest in ESP8266 !
Re: serial us debug, wdt reset
Postby mariuszb » Fri Jun 19, 2015 2:37 am
Hi,
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
Thanks for fast answer, however ..
1. if they are logs that can never be off a little bit less professional

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

Who is online
Users browsing this forum: No registered users and 2 guests
Login
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
Latest SDK
Documentation
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!
- All times are UTC+08:00
- Top
- Delete all board cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. We are the manufacturer of ESP8266EX.