Looking at the documentation for ESP-AT, it appears transparent/data mode operation requires a TCP socket be created before data mode is entered.
Typically, for a cellular modem, this is not the case. The modem registers on the network, enters data mode, then data is transparently transferred ...
Search found 5 matches
- Wed Apr 30, 2025 4:56 am
- Forum: ESP-AT
- Topic: ESP-AT data mode requires existing socket
- Replies: 1
- Views: 2576
- Tue May 09, 2023 5:53 am
- Forum: ESP-IDF
- Topic: IDF 5.0.1 on ESP32-S3 with CONFIG_ESP_TLS_USE_SECURE_ELEMENT
- Replies: 4
- Views: 32632
Re: IDF 5.0.1 on ESP32-S3 with CONFIG_ESP_TLS_USE_SECURE_ELEMENT
Hi Aditya,
Thank you, fixes for 1 and 3 will be very useful.
I had a quick look at the HAL code and saw there is already support for starting and stopping multiple devices, but only when they are on different I2C buses. Since there is a reference count and an array of configs maybe it would be ...
Thank you, fixes for 1 and 3 will be very useful.
I had a quick look at the HAL code and saw there is already support for starting and stopping multiple devices, but only when they are on different I2C buses. Since there is a reference count and an array of configs maybe it would be ...
- Fri May 05, 2023 4:28 am
- Forum: ESP-IDF
- Topic: IDF 5.0.1 on ESP32-S3 with CONFIG_ESP_TLS_USE_SECURE_ELEMENT
- Replies: 4
- Views: 32632
IDF 5.0.1 on ESP32-S3 with CONFIG_ESP_TLS_USE_SECURE_ELEMENT
Hello,
We are developing a product based on ESP32-S3 and IDF 5.0.1 (current stable). There is also a Microchip ATECC680A-TNGTLS on board, though we will be using ATECC608B-TNGTLS in production.
I have the board up and running, and I am able to access the secure element using ESP-CRYPTOAUTHLIB 3.5 ...
We are developing a product based on ESP32-S3 and IDF 5.0.1 (current stable). There is also a Microchip ATECC680A-TNGTLS on board, though we will be using ATECC608B-TNGTLS in production.
I have the board up and running, and I am able to access the secure element using ESP-CRYPTOAUTHLIB 3.5 ...
- Wed Jul 01, 2020 11:50 pm
- Forum: ESP-IDF
- Topic: Memory allocation failed hook
- Replies: 3
- Views: 7129
Re: Memory allocation failed hook
Hello,
Thank you for replying and I am sorry I did not get back to you sooner, but I have been distracted by other things :-(
Anyway, I was indeed including the correct headers. This morning I grabbed the latest ESP-IDF and recompiled to find that worked ok with no changes to my code, so I ...
Thank you for replying and I am sorry I did not get back to you sooner, but I have been distracted by other things :-(
Anyway, I was indeed including the correct headers. This morning I grabbed the latest ESP-IDF and recompiled to find that worked ok with no changes to my code, so I ...
- Wed Jun 03, 2020 4:07 am
- Forum: ESP-IDF
- Topic: Memory allocation failed hook
- Replies: 3
- Views: 7129
Memory allocation failed hook
Hello,
I am one of a team developing a commercial product based on the ESP_WROVER module. Up until now we have been using IDF v3.3, but are now moving to IDF v4, specifically I am currently using: ESP-IDF v4.2-dev-1320-g1aebfdf6a.
I have been seeing some malloc failures, so I thought I would ...
I am one of a team developing a commercial product based on the ESP_WROVER module. Up until now we have been using IDF v3.3, but are now moving to IDF v4, specifically I am currently using: ESP-IDF v4.2-dev-1320-g1aebfdf6a.
I have been seeing some malloc failures, so I thought I would ...