Search found 75 matches
- Tue Nov 20, 2018 12:37 pm
- Forum: ESP-IDF
- Topic: scanning after AP disappears -- errors: Now is connecting, user scan invalid now!
- Replies: 2
- Views: 5523
Re: scanning after AP disappears -- errors: Now is connecting, user scan invalid now!
Hi Jimbob, For what it's worth, I've run into the same issue. Our solution was to set a timeout, after which we will cancel the connecting state by reconfiguring WiFi in (AP)STA mode with blank ssid. Then a scan can succeed again. It's a sloppy and somewhat slow state-machine based on timeouts, but ...
- Mon Nov 19, 2018 8:16 pm
- Forum: ESP-IDF
- Topic: [SOLVED] Severe Limitation to APSTA Mode
- Replies: 7
- Views: 11840
Re: Severe Limitation to APSTA Mode
Thanks all for the replies on this. But Joe really nailed it: Check your event callback and see if you are issuing a esp_wifi_connect() in response to an event. If so, you may need to rethink exactly how you do that. LWIP may be giving more time constantly processing the STA connect that any AP conn...
- Sat Nov 17, 2018 1:02 am
- Forum: Hardware
- Topic: RMT Interrupt Delayed when WiFi STA Connect Failing
- Replies: 2
- Views: 4213
RMT Interrupt Delayed when WiFi STA Connect Failing
We use ESP32 in a real-time application, where we need RMT RX continuously running even while connecting to WiFi. We are seeing good accuracy of RMT RX, except when we attempt to connect to a WiFi access point which does not exist (wrong ssid). In this case, we get incorrect data from the RMT, appro...
- Fri Nov 16, 2018 9:01 pm
- Forum: ESP-IDF
- Topic: [SOLVED] Severe Limitation to APSTA Mode
- Replies: 7
- Views: 11840
[SOLVED] Severe Limitation to APSTA Mode
We are running into a rather severe limitation of APSTA mode. We expected to be able to keep the ESP in APSTA mode continuously, and rely on the AP-side for re-configuration. That does not seem to be viable. To Reproduce: Using esp-idf v3.1. 1. Configure ESP32 for APSTA mode, and set the sta config ...
- Thu Oct 25, 2018 11:12 pm
- Forum: ESP-IDF
- Topic: Closing a socket after recv timeout results in resource leak
- Replies: 1
- Views: 5327
Closing a socket after recv timeout results in resource leak
tl;dr: I get an error after closing 10x sockets, but only if they just experienced a recv() timeout. Note: I'm using SO_RECVTIMEO option set to 1 second. So a recv() call will return after 1 sec if no data is received. However, the socket seems to then be in a state where it is not closed properly w...
- Wed Oct 24, 2018 4:01 pm
- Forum: ESP-IDF
- Topic: [SOLVED] Boot Different Partition from Application
- Replies: 9
- Views: 15900
Re: Boot Different Partition from Application
Here's the solution we ended up using: 1. create a header file called xesp_rtc_defs.h which is shared between a custom bootloader component and our app. I've pasted the whole contents at the end of this post. 2. Use deepsleep instead of reboot from app, to preserve RTC mem. 3. When we want to use th...
- Mon Oct 22, 2018 3:28 pm
- Forum: ESP-IDF
- Topic: SYSTEM_EVENT_SCAN_DONE may not always arrive
- Replies: 0
- Views: 2394
SYSTEM_EVENT_SCAN_DONE may not always arrive
It is my understanding of the documentation (https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/wifi.html#esp32-wi-fi-scan) that after a successful call to esp_wifi_scan_start, we are guaranteed to get a SYSTEM_EVENT_SCAN_DONE event. However, I've found that if ESP32 is connecting to W...
- Thu Oct 04, 2018 2:51 pm
- Forum: ESP IoT Solution
- Topic: How to pass payload to a task
- Replies: 3
- Views: 7474
Re: How to pass payload to a task
Hi Blase, Often you can process the message within the mqtt_subscribe_callback. You just want to check that that callback is a normal task context and has a moderate priority. --- You wouldn't want to process the message from interrupt context, or within a task with very high priority. That said, if...
- Wed Oct 03, 2018 8:35 pm
- Forum: ESP-IDF
- Topic: NimBLE ESP32 Port
- Replies: 2
- Views: 4865
NimBLE ESP32 Port
Are there any near-term plans to port NimBLE to ESP32? The high RAM requirements of BlueDroid currently prevent me from taking advantage of Bluetooth in ESP32 (which was a major reason for selecting the SoC!). Porting NimBLE myself would be fun, but it would make more sense as either an Espressif or...
- Mon Aug 27, 2018 7:36 pm
- Forum: ESP-IDF
- Topic: [SOLVED] Boot Different Partition from Application
- Replies: 9
- Views: 15900
Re: Boot Different Partition from Application
Thanks! We will give that a try. Should be easy to accomplish with one if-statement in a customized bootloader.ESP_igrr wrote:Storing a pointer to the desired partition in RTC memory and rebooting to let the bootloader load that partition is probably going to be the easiest way.