Search found 2344 matches
- Thu Dec 19, 2019 11:13 pm
- Forum: ESP-IDF
- Topic: OTA failure
- Replies: 6
- Views: 6363
Re: OTA failure
I'll check if the Bluetooth team has any suggestions as well. Bluetooth team says that BLE disconnects can happen for a number of reasons, so without logs it's not possible to debug further. They agree with the suggestion of tracking the file length and number of transferred bytes as part of the OT...
- Thu Dec 19, 2019 10:56 pm
- Forum: General Discussion
- Topic: Migrating from legacy to CMake build
- Replies: 8
- Views: 7391
Re: Migrating from legacy to CMake build
Hi PeterR, Looks like it's tripping up on some whitespace in the COMPONENT_PATHS list generated by Make, there must be two spaces between one of the entries. Could you please try applying the following patch and see if it starts working as expected? diff --git a/tools/cmake/convert_to_cmake.py b/too...
- Thu Dec 19, 2019 10:38 pm
- Forum: General Discussion
- Topic: std::thread not usuable in ESP-IDF 4.1 legacy build
- Replies: 13
- Views: 11351
Re: std::thread not usuable in ESP-IDF 4.1 legacy build
Hi Peter, Thanks for your help with the extra details. I just retried with your .cpp file and could reproduce once, but the problem went away on a clean rebuild. Which is frustrating, as I didn't keep the details of the failed build (oops). This suggests to me that it's something to do with the orde...
- Thu Dec 19, 2019 5:58 am
- Forum: ESP IoT Solution
- Topic: Failure to provision with 4.x IDF but works with 3.3 IDF
- Replies: 15
- Views: 17874
Re: Failure to provision with 4.x IDF but works with 3.3 IDF
Thanks jsam589, good idea providing logs from the working session also. So there is no difference in firmware/config between the working and non-working, except for ESP-IDF version? I looked at the logs and it seems like the server is closing the connection after receiving the TLS "Client Hello" mes...
- Thu Dec 19, 2019 4:22 am
- Forum: General Discussion
- Topic: std::thread not usuable in ESP-IDF 4.1 legacy build
- Replies: 13
- Views: 11351
Re: std::thread not usuable in ESP-IDF 4.1 legacy build
Hi PeterR, Thanks for the details. ESP-IDF provides its own pthread support wrappers, so you shouldn't need to add anything for this to work. I wasn't able to reproduce this building the code shown above (plus the necessary headers), using IDF's current GitHub master commit (v4.1-dev-1572-g30372f5a4...
- Thu Dec 19, 2019 4:12 am
- Forum: General Discussion
- Topic: Migrating from legacy to CMake build
- Replies: 8
- Views: 7391
Re: Migrating from legacy to CMake build
Hi Peter, The automatic conversion script and the docs page chegewara linked are good places to start. But also: (ESP-IDF 4.1 legacy build seems C++11 broken). We still support the legacy build system. If you open a github issue or something to report exactly what's broken then we will fix it. EDIT:...
- Wed Dec 18, 2019 3:10 am
- Forum: ESP IoT Solution
- Topic: Failure to provision with 4.x IDF but works with 3.3 IDF
- Replies: 15
- Views: 17874
Re: Failure to provision with 4.x IDF but works with 3.3 IDF
Hi jsam589, Here is the error I got this time. Notice that the error is followed by "Certificate verified". Does this shed any new light? Thanks! D (23848) esp-tls: handshake in progress... E (23848) esp-tls: mbedtls_ssl_handshake returned -0x7280 I (23848) esp-tls: Certificate verified. Interesting...
- Tue Dec 17, 2019 10:42 pm
- Forum: ESP-ADF
- Topic: why isn't ESP-ADF components in ESP-IDF
- Replies: 3
- Views: 6428
Re: why isn't ESP-ADF components in ESP-IDF
Hi username, There are a few reasons, but they include: Not everyone needs ADF components, but IDF projects will build all the IDF components by default. Our long term plan is to move more non-essential high level components out of IDF, so IDF is just a "core" of commonly used components. (Before we...
- Tue Dec 17, 2019 10:37 pm
- Forum: ESP-IDF
- Topic: OTA failure
- Replies: 6
- Views: 6363
Re: OTA failure
Hi Gibson, Sorry for the confusing OTA error. Can confirm the root cause of "esp_image: invalid segment length 0xfffffff" is almost always a truncated image (the transfer completed before all bytes transferred). We have an open ticket internally to make this message more user friendly. If it's possi...
- Tue Dec 17, 2019 10:31 pm
- Forum: ESP-IDF
- Topic: LWIP - threadsafe
- Replies: 3
- Views: 3931
Re: LWIP - threadsafe
You can use either but we recommend calling the standard functions - ie accept(). But they compile to the same thing.