Could you please also post liblwip_536.a ? Thanks!
FYI for others: without this patch a fatal exception causing reset gets triggered if you call espconn_abort() on a connection that is actively receiving data.
Search found 123 matches
- Wed Dec 16, 2015 1:20 pm
- Forum: ESP8266 SDK
- Topic: Re: [SDK Patch] espconn_abort issue on ESP8266_NONOS_SDK_V1.5.0
- Replies: 1
- Views: 7158
- Sat Dec 05, 2015 1:19 pm
- Forum: ESP8266 HDK
- Topic: avoid clock-out on gpio0 at reset?
- Replies: 2
- Views: 8004
avoid clock-out on gpio0 at reset?
I am finding that in prototyping situations the fact that gpio0 outputs the 26Mhz clock can cause quite some noise issues. Cables, etc. Since gpio0 has to be pulled high or low in order to control the boot mode, it has to be connected to the programmer, often via a cable. Is there a way to toggle re...
- Sat Dec 05, 2015 11:50 am
- Forum: ESP8266 SDK
- Topic: at_register_uart_rx_intr(user_uart_rx_intr);
- Replies: 8
- Views: 6204
Re: at_register_uart_rx_intr(user_uart_rx_intr);
You're misunderstanding TOUT. A TOUT value of N means: "if you have not received any new character in N time units then an interrupt is fired. A time unit is the time it takes to receive 8 bits."
- Sun Nov 29, 2015 5:21 pm
- Forum: ESP8266 SDK
- Topic: at_register_uart_rx_intr(user_uart_rx_intr);
- Replies: 8
- Views: 6204
Re: at_register_uart_rx_intr(user_uart_rx_intr);
Your test is faulty...
You can get an interrupt when the fifo reaches a fill level you set or when there are characters in the fifo and nothing new has been received in a time period you set.
You can get an interrupt when the fifo reaches a fill level you set or when there are characters in the fifo and nothing new has been received in a time period you set.
- Sun Nov 29, 2015 2:21 am
- Forum: ESP8266 SDK
- Topic: SDK 1.5.0 bug bounty reward goes to...
- Replies: 3
- Views: 3329
Re: SDK 1.5.0 bug bounty reward goes to...
You should email to the bug bounty address (bugbounty@espressif.com), it's detailed in the bug bounty program write-up. I've always gotten a response with 2-3 days.
- Sat Nov 28, 2015 1:24 pm
- Forum: ESP8266 SDK
- Topic: SDK 1.5.0 & liblwip_536
- Replies: 1
- Views: 2406
SDK 1.5.0 & liblwip_536
SDK 1.5.0 is missing liblwip_536.a, can you please provide it? It's pretty critical in memory constrained firmwares that need to support many connections. Thank you!
- Thu Nov 19, 2015 2:17 am
- Forum: ESP8266 SDK
- Topic: mDNS "already freed" errors
- Replies: 2
- Views: 4218
Re: mDNS "already freed" errors
FYI: I was using lib1.4.1_pre7, I will see whether I can produce a small project that exhibits the problem.
NB: The lib1.4.1_pre7 archive is missing liblwip_536.a
NB: The lib1.4.1_pre7 archive is missing liblwip_536.a
- Wed Nov 18, 2015 1:24 pm
- Forum: ESP8266 SDK
- Topic: Problems running softAP -SDK 1.4.0 [SOLVED]
- Replies: 17
- Views: 15933
Re: Problems running softAP -SDK 1.4.0 [SOLVED]
@Espressif_Faye can you please provide liblwip_536.a for SDK v1.4.1_pre7 ?
Thanks!
Thanks!
- Tue Nov 17, 2015 1:16 pm
- Forum: ESP8266 SDK
- Topic: mDNS "already freed" errors
- Replies: 2
- Views: 4218
mDNS "already freed" errors
When I enable mDNS using SDK 1.4.1_pre7 I get "already freed" errors: 5658> ip:192.168.0.151,mask:255.255.255.0,gw:192.168.0.1 5658> Wifi got ip:192.168.0.151,mask:255.255.255.0,gw:192.168.0.1 5660> host_name = esp-link4 5663> server_name = _http._tcp.local 12525> pm open phy_2,type:2 0 0 ...
- Tue Nov 17, 2015 12:55 pm
- Forum: ESP8266 SDK
- Topic: [Resolved]SDK V1.4.0 连接路由器后再运行mDNS会输出很多3fff0280 already freed
- Replies: 4
- Views: 6494
Re: [Resolved]SDK V1.4.0 连接路由器后再运行mDNS会输出很多3fff0280 already freed
I have the same problem with the "already freed" errors using V1.4.1_pre7 from http://bbs.espressif.com/viewtopic.php?f=7&t=1257&start=10#p4505 Did the fix in the liblwip.a from this thread get lost in the _pre7 version? I am also seeing problems where mDNS does not reply to certai...