Just updated to 1.0.4 libraries/tools and WiFi/BLE dont' play together anymore
Posted: Sat Apr 18, 2020 12:21 pm
I've just upgraded from 1.0.2 libraries to 1.0.4.
My application (On a HELTEC kit32 with OLED) talks to a BLE OBD sensor. It is configured as a large app (No OTA).
It also has an SD card attached, a GPS on serial, a BME280 and a 9DOF device on I2C and finally an IR sensor with remote keypad.
It all worked fine on 1.0.2. APART from : When I finished logging and came to email (using smtp2go) the file from the SD card, it would lock up for 8s seconds at a time on client.write() statements completely at random and cause smpt2go to close the connection.
I use CORE 1 for the main loop() and CORE 0 for writing to the SD card. There are no writes to the SD card when trying to email.
On 1.0.4 libraries, I can no longer connect to WiFi once the BLE is running. If I connect to the WiFi first, then when I try to do a readValue() of a characteristic on the BLE device, the ESP32 hangs. It doesn't crash. It seems to be waiting for a blocking semaphore on
readCharEvt().
Does anyone have any ideas? I know it's a complex situation and usually I can solve my own problems, but this one has me stumped.
My application (On a HELTEC kit32 with OLED) talks to a BLE OBD sensor. It is configured as a large app (No OTA).
It also has an SD card attached, a GPS on serial, a BME280 and a 9DOF device on I2C and finally an IR sensor with remote keypad.
It all worked fine on 1.0.2. APART from : When I finished logging and came to email (using smtp2go) the file from the SD card, it would lock up for 8s seconds at a time on client.write() statements completely at random and cause smpt2go to close the connection.
I use CORE 1 for the main loop() and CORE 0 for writing to the SD card. There are no writes to the SD card when trying to email.
On 1.0.4 libraries, I can no longer connect to WiFi once the BLE is running. If I connect to the WiFi first, then when I try to do a readValue() of a characteristic on the BLE device, the ESP32 hangs. It doesn't crash. It seems to be waiting for a blocking semaphore on
readCharEvt().
Does anyone have any ideas? I know it's a complex situation and usually I can solve my own problems, but this one has me stumped.
- lockup.png (9.98 KiB) Viewed 2512 times