Hello.
I am performing some tests to communicate an Espressif WiFi mesh network with an external agent, using standard UDP messages (by means of Berkeley sockets). In my tests, only the root of the mesh sends messages to the external agent, which listens on a port for the messages.
The weird case ...
Search found 10 matches
- Thu Jan 22, 2026 7:04 pm
- Forum: ESP-IDF
- Topic: UDP messages from mesh root to softAP
- Replies: 1
- Views: 403
- Sun Dec 24, 2023 12:01 am
- Forum: ESP-IDF
- Topic: esp_modem program build problem
- Replies: 3
- Views: 2505
Re: esp_modem program build problem
Solved. Weird enough, I tried and it was the reason. The two functions are missing from esp_modem_c_api.cpp
I created them
extern "C" esp_err_t esp_modem_resume_data_mode(esp_modem_dce_t *dce_wrap)
{
if (dce_wrap == nullptr || dce_wrap->dce == nullptr) {
return ESP_ERR_INVALID_ARG;
}
return ...
I created them
extern "C" esp_err_t esp_modem_resume_data_mode(esp_modem_dce_t *dce_wrap)
{
if (dce_wrap == nullptr || dce_wrap->dce == nullptr) {
return ESP_ERR_INVALID_ARG;
}
return ...
- Sat Dec 23, 2023 11:28 pm
- Forum: ESP-IDF
- Topic: esp_modem program build problem
- Replies: 3
- Views: 2505
Re: esp_modem program build problem
This is CMakelists.txt for my modem component. Everything has been working for months, until I used the two functions I mentioned.
idf_component_register(SRCS "modem.c" INCLUDE_DIRS "include" REQUIRES "driver" "esp_event" "esp_netif" "esp_modem")
Thank you for your answer.
idf_component_register(SRCS "modem.c" INCLUDE_DIRS "include" REQUIRES "driver" "esp_event" "esp_netif" "esp_modem")
Thank you for your answer.
- Sat Dec 23, 2023 1:10 pm
- Forum: ESP-IDF
- Topic: esp_modem program build problem
- Replies: 3
- Views: 2505
esp_modem program build problem
Hello all.
I am using the esp_modem component in my project, and I am having problems when using the esp_modem_set_command_mode() and esp_modem_resume_data_mode() functions. I have seen that they are C functions derived from their C++ counterparts set_command_mode() and resume_data_mode().
I do ...
I am using the esp_modem component in my project, and I am having problems when using the esp_modem_set_command_mode() and esp_modem_resume_data_mode() functions. I have seen that they are C functions derived from their C++ counterparts set_command_mode() and resume_data_mode().
I do ...
- Tue Aug 08, 2023 4:31 pm
- Forum: ESP-IDF
- Topic: Problem in intr_alloc.c module
- Replies: 6
- Views: 2968
Re: Problem in intr_alloc.c module
Hello.
I am back with this problem. My client redesigned the hardware and changed the modem module, so I have been out of this project for a while. But I am now back at it and the problem persists.
If I initialize the modem using this function
modem_t *modem_Init(int tx_pin, int rx_pin, int rts ...
I am back with this problem. My client redesigned the hardware and changed the modem module, so I have been out of this project for a while. But I am now back at it and the problem persists.
If I initialize the modem using this function
modem_t *modem_Init(int tx_pin, int rx_pin, int rts ...
- Tue May 23, 2023 7:42 am
- Forum: ESP-IDF
- Topic: Problem in intr_alloc.c module
- Replies: 6
- Views: 2968
Re: Problem in intr_alloc.c module
Any news about this problem?
- Thu May 18, 2023 1:43 pm
- Forum: ESP-IDF
- Topic: attachInterrupt not recognised
- Replies: 2
- Views: 1891
Re: attachInterrupt not recognised
As far as I know, attachInterrupt is a function used in the Arduino IDE (and PlatformIO) to attach a pseudo interrupt routine to an external (GPIO triggered) interrupt. It is not a generic function and not one supported by the Espressif IDE.
- Mon May 15, 2023 6:58 am
- Forum: ESP-IDF
- Topic: Problem in intr_alloc.c module
- Replies: 6
- Views: 2968
Re: Problem in intr_alloc.c module
Hello.
I have reduced the code to an absolute minimum. It is the pppos_client code but GPIO configuration and modem activation (via GPIO pin) is placed in functions in a component; modem management is placed in another component. Main app just calls the functions as required, then waits on the ...
I have reduced the code to an absolute minimum. It is the pppos_client code but GPIO configuration and modem activation (via GPIO pin) is placed in functions in a component; modem management is placed in another component. Main app just calls the functions as required, then waits on the ...
- Sun May 14, 2023 11:37 am
- Forum: ESP-IDF
- Topic: Problem in intr_alloc.c module
- Replies: 6
- Views: 2968
Re: Problem in intr_alloc.c module
Hello, and thank you for your reply.
The code is basically the same as the pppos_client example from the esp_modem component. I am continuing working around the problem and I am more puzzled each time.
As the mentioned example works with BLE enabled in menuconfig, I have tried the following: my app ...
The code is basically the same as the pppos_client example from the esp_modem component. I am continuing working around the problem and I am more puzzled each time.
As the mentioned example works with BLE enabled in menuconfig, I have tried the following: my app ...
- Fri May 12, 2023 8:47 am
- Forum: ESP-IDF
- Topic: Problem in intr_alloc.c module
- Replies: 6
- Views: 2968
Problem in intr_alloc.c module
Hello.
I have been working for several weeks in a project accessing MQTT servers using the pppos interface provided by the esp-modem component. Everything was working perfect, until I enabled BLE in menuconfig. From that moment, and with exactly the same code that worked perfectly, the system began ...
I have been working for several weeks in a project accessing MQTT servers using the pppos interface provided by the esp-modem component. Everything was working perfect, until I enabled BLE in menuconfig. From that moment, and with exactly the same code that worked perfectly, the system began ...