Gosh,
I made so many checks and so many tries for such a stupid mistake
Thanks a lot!
Search found 12 matches
- Tue Mar 04, 2025 12:26 pm
- Forum: ESP-IDF
- Topic: UART2 RX interrupt how to do it?
- Replies: 16
- Views: 14385
- Tue Mar 04, 2025 9:22 am
- Forum: ESP-IDF
- Topic: UART2 RX interrupt how to do it?
- Replies: 16
- Views: 14385
Re: UART2 RX interrupt how to do it?
Ok!
Then it means I have a bad parameter in the uart driver installation then because the esp keeps looping at hi frequency on the below.
NoBytesRead = uart_read_bytes(UART_NUM_2, serBufIn, NoBytesRead, 200 / portTICK_PERIOD_MS)
With what you explained above I will check for my mistake and revert ...
Then it means I have a bad parameter in the uart driver installation then because the esp keeps looping at hi frequency on the below.
NoBytesRead = uart_read_bytes(UART_NUM_2, serBufIn, NoBytesRead, 200 / portTICK_PERIOD_MS)
With what you explained above I will check for my mistake and revert ...
- Tue Mar 04, 2025 8:51 am
- Forum: ESP-IDF
- Topic: UART2 RX interrupt how to do it?
- Replies: 16
- Views: 14385
Re: UART2 RX interrupt how to do it?
Thank you!!!
It indeed now makes a lot more sense!
Gosh a few simple things like that are not trivial to catch.
Now I fully get it .
Thanks again
It indeed now makes a lot more sense!
Gosh a few simple things like that are not trivial to catch.
Now I fully get it .
Thanks again
- Mon Mar 03, 2025 5:09 pm
- Forum: ESP-IDF
- Topic: UART2 RX interrupt how to do it?
- Replies: 16
- Views: 14385
Re: UART2 RX interrupt how to do it?
Hi,
There is something I do not get in all the above examples. You either have a while (1) loop to wait for an event to occur or a for (;;) which is for me the same.
The whole point of the interrupt is precisely to not have such types of infinite loops that do eat cpu time.
After looking all over ...
There is something I do not get in all the above examples. You either have a while (1) loop to wait for an event to occur or a for (;;) which is for me the same.
The whole point of the interrupt is precisely to not have such types of infinite loops that do eat cpu time.
After looking all over ...
- Mon Mar 03, 2025 4:35 pm
- Forum: ESP-IDF
- Topic: UART2 RX interrupt how to do it?
- Replies: 16
- Views: 14385
Re: UART2 RX interrupt how to do it?
Hi,
There is something I do not get in all the above examples. You either have a while (1) loop to wait for an event to occur or a for (;;) which is for me the same.
The whole point of the interrupt is precisely to not have such types of infinite loops that do eat cpu time.
After looking all over ...
There is something I do not get in all the above examples. You either have a while (1) loop to wait for an event to occur or a for (;;) which is for me the same.
The whole point of the interrupt is precisely to not have such types of infinite loops that do eat cpu time.
After looking all over ...
- Sun Mar 02, 2025 9:37 pm
- Forum: Hardware
- Topic: ESP32H2 global performance
- Replies: 0
- Views: 1463
ESP32H2 global performance
Hi!
I was looking to get informations about the ESP32H2 adc performance / Linearity.
I am looking to acquire data at a relatively slow rate , 3000Hz, and I wonder is that ESP32 flavor has a better ADC converter than the ESP32D or S3.
I could not find any information regarding this.
Thanks!
I was looking to get informations about the ESP32H2 adc performance / Linearity.
I am looking to acquire data at a relatively slow rate , 3000Hz, and I wonder is that ESP32 flavor has a better ADC converter than the ESP32D or S3.
I could not find any information regarding this.
Thanks!
- Sun Feb 23, 2025 9:05 am
- Forum: ESP-IDF
- Topic: Error compiling a fresh update of espidf / Platformio : i2c_master.c
- Replies: 0
- Views: 549
Error compiling a fresh update of espidf / Platformio : i2c_master.c
Hello,
Just updated espidf in platformio version 6.10.0, and I get the following error at compile time, in debug mode:
C:\Users\Utilisateur\.platformio\packages\framework-espidf\components\esp_driver_i2c\i2c_master.c:871:23: error: 'ops_current' may be used uninitialized [-Werror=maybe ...
Just updated espidf in platformio version 6.10.0, and I get the following error at compile time, in debug mode:
C:\Users\Utilisateur\.platformio\packages\framework-espidf\components\esp_driver_i2c\i2c_master.c:871:23: error: 'ops_current' may be used uninitialized [-Werror=maybe ...
- Sat Feb 22, 2025 10:18 am
- Forum: General Discussion
- Topic: Code links in debug mode but not in release
- Replies: 3
- Views: 968
Re: Code links in debug mode but not in release
Hi again
If I go in menuconfig, and selects the o2 directive for the compiler it does compile and link.
If I go in platformio.ini and write build_type=debug it compiles and link. If I write build_type=release it compiles but linker fails with iram overflow.
I suspect the linker script generated ...
If I go in menuconfig, and selects the o2 directive for the compiler it does compile and link.
If I go in platformio.ini and write build_type=debug it compiles and link. If I write build_type=release it compiles but linker fails with iram overflow.
I suspect the linker script generated ...
- Sat Feb 22, 2025 7:30 am
- Forum: General Discussion
- Topic: Code links in debug mode but not in release
- Replies: 3
- Views: 968
Re: Code links in debug mode but not in release
To be more precise I compile the code using vscode and pkatformio. In platformio.ini you have a flag for build_type and I either set it to debug and the code links and runs or release and then I get a linker error with iram overflow.
This seems redundant with menu config where we can also select ...
This seems redundant with menu config where we can also select ...
- Sat Feb 22, 2025 1:38 am
- Forum: General Discussion
- Topic: Code links in debug mode but not in release
- Replies: 3
- Views: 968
Code links in debug mode but not in release
Hi,
I tried to search on the forum but could not find the info.
I wrote a code for the esp32d that works well in debug mode. I try to compile in release mode and I get an error message about iram overflow. I was always thinking that a code for debug was always bigger than a release one… ? There ...
I tried to search on the forum but could not find the info.
I wrote a code for the esp32d that works well in debug mode. I try to compile in release mode and I get an error message about iram overflow. I was always thinking that a code for debug was always bigger than a release one… ? There ...