Xedge>> ESP32_C3_TimerInterrupt>> 返回
项目作者： khoih-prog

项目描述 ：
This library enables you to use Interrupt from Hardware Timers on an ESP32-C3-based board. These ESP32-C3 Hardware Timers, using Interrupt, still work even if other functions are blocking. Moreover, they are much more precise (certainly depending on clock frequency accuracy) than other software timers using millis() or micros(). That's mandatory if you need to measure some data requiring better accuracy. It now supports 16 ISR-based Timers, while consuming only 1 Hardware Timer. Timers' interval is very long (ulong millisecs). The most important feature is they're ISR-based Timers. Therefore, their executions are not blocked by bad-behaving functions or tasks. This important feature is absolutely necessary for mission-critical tasks.
高级语言： C++
项目地址: git://github.com/khoih-prog/ESP32_C3_TimerInterrupt.git
创建时间： 2021-07-29T18:39:46Z
项目社区：https://github.com/khoih-prog/ESP32_C3_TimerInterrupt
开源协议：MIT License
下载


ESP32_C3_TimerInterrupt Library

arduino-library-badge
GitHub release
GitHub
contributions welcome
GitHub issues

Donate to my libraries using BuyMeACoffee

—-

Table of Contents

—-

Important Change from v1.5.0

Please have a look at HOWTO Fix Multiple Definitions Linker Error

Why do we need this ESP32_C3_TimerInterrupt library

Features

This library enables you to use Interrupt from Hardware Timers on an ESP32_C3-based board.

The ESP32_C3 timer Interrupt control is different from that of ESP32, at least with the ESP32_C3 core v2.0.0-rc1. While the examples of current ESP32TimerInterrupt library can be compiled OK, they can’t run yet. That’s why this new ESP32_C3_TimerInterrupt library has been created.

As Hardware Timers are rare, and very precious assets of any board, this library now enables you to use up to 16 ISR-based Timers, while consuming only 1 Hardware Timer. Timers’ interval is very long (ulong millisecs).

Now with these new 16 ISR-based timers, the maximum interval is practically unlimited (limited only by unsigned long milliseconds) while the accuracy is nearly perfect compared to software timers.

The most important feature is they’re ISR-based timers. Therefore, their executions are not blocked by bad-behaving functions / tasks. This important feature is absolutely necessary for mission-critical tasks.

The ISR_Timer_Complex example will demonstrate the nearly perfect accuracy compared to software timers by printing the actual elapsed millisecs of each type of timers.

Being ISR-based timers, their executions are not blocked by bad-behaving functions / tasks, such as connecting to WiFi, Internet and Blynk services. You can also have many (up to 16) timers to use.

This non-being-blocked important feature is absolutely necessary for mission-critical tasks.

You’ll see blynkTimer Software is blocked while system is connecting to WiFi / Internet / Blynk, as well as by blocking task
in loop(), using delay() function as an example. The elapsed time then is very unaccurate

Why using ISR-based Hardware Timer Interrupt is better

Imagine you have a system with a mission-critical function, measuring water level and control the sump pump or doing something much more important. You normally use a software timer to poll, or even place the function in loop(). But what if another function is blocking the loop() or setup().

So your function might not be executed, and the result would be disastrous.

You’d prefer to have your function called, no matter what happening with other functions (busy loop, bug, etc.).

The correct choice is to use a Hardware Timer with Interrupt to call your function.

These hardware timers, using interrupt, still work even if other functions are blocking. Moreover, they are much more precise (certainly depending on clock frequency accuracy) than other software timers using millis() or micros(). That’s necessary if you need to measure some data requiring better accuracy.

Functions using normal software timers, relying on loop() and calling millis(), won’t work if the loop() or setup() is blocked by certain operation. For example, certain function is blocking while it’s connecting to WiFi or some services.

The catch is your function is now part of an ISR (Interrupt Service Routine), and must be lean / mean, and follow certain rules. More to read on:

HOWTO Attach Interrupt

Currently supported Boards

  1. ESP32_C3-based boards, such as ESP32C3_DEV, LOLIN_C3_MINI, DFROBOT_BEETLE_ESP32_C3, ADAFRUIT_QTPY_ESP32C3, AirM2M_CORE_ESP32C3, XIAO_ESP32C3, etc.

Important Notes about ISR

  1. Inside the attached function, delay() won’t work and the value returned by millis() will not increment. Serial data received while in the function may be lost. You should declare as volatile any variables that you modify within the attached function.

  2. Typically global variables are used to pass data between an ISR and the main program. To make sure variables shared between an ISR and the main program are updated correctly, declare them as volatile.

—-

Prerequisites

  1. Arduino IDE 1.8.19+ for Arduino. GitHub release
  2. ESP32 Core 2.0.5+ for ESP32-S2-based boards. Latest release
  3. To use with certain example

—-

Installation

Use Arduino Library Manager

The best and easiest way is to use Arduino Library Manager. Search for ESP32_C3_TimerInterrupt, then select / install the latest version.
You can also use this link arduino-library-badge for more detailed instructions.

Manual Install

Another way to install is to:

  1. Navigate to ESP32_C3_TimerInterrupt page.
  2. Download the latest release ESP32_C3_TimerInterrupt-main.zip.
  3. Extract the zip file to ESP32_C3_TimerInterrupt-main directory
  4. Copy whole ESP32_C3_TimerInterrupt-main folder to Arduino libraries’ directory such as ~/Arduino/libraries/.

VS Code & PlatformIO

  1. Install VS Code
  2. Install PlatformIO
  3. Install ESP32_C3_TimerInterrupt library by using Library Manager. Search for ESP32_C3_TimerInterrupt in Platform.io Author’s Libraries
  4. Use included platformio.ini file from examples to ensure that all dependent libraries will installed automatically. Please visit documentation for the other options and examples at Project Configuration File

—-

Note for Platform IO using ESP32 LittleFS

Necessary only for esp32 core v1.0.6-

From esp32 core v1.0.6+, LittleFS_esp32 v1.0.6 has been included and this step is not necessary anymore.

In Platform IO, to fix the error when using LittleFS_esp32 v1.0 for ESP32-based boards with ESP32 core v1.0.4- (ESP-IDF v3.2-), uncomment the following line

from

  1. //#define CONFIG_LITTLEFS_FOR_IDF_3_2   /* For old IDF - like in release 1.0.4 */

to

  1. #define CONFIG_LITTLEFS_FOR_IDF_3_2   /* For old IDF - like in release 1.0.4 */

It’s advisable to use the latest LittleFS_esp32 v1.0.5+ to avoid the issue.

Thanks to Roshan to report the issue in Error esp_littlefs.c ‘utime_p’

—-

HOWTO Fix Multiple Definitions Linker Error

The current library implementation, using xyz-Impl.h instead of standard xyz.cpp, possibly creates certain Multiple Definitions Linker error in certain use cases.

You can include these .hpp or .h files

  1. // Can be included as many times as necessary, without `Multiple Definitions` Linker Error
  2. #include "ESP32_C3_TimerInterrupt.h"     //https://github.com/khoih-prog/ESP32_C3_TimerInterrupt
  4. // Can be included as many times as necessary, without `Multiple Definitions` Linker Error
  5. #include "ESP32_C3_ISR_Timer.hpp"         //https://github.com/khoih-prog/ESP32_C3_TimerInterrupt

in many files. But be sure to use the following .h file in just 1 .h, .cpp or .ino file, which must not be included in any other file, to avoid Multiple Definitions Linker Error

  1. // To be included only in main(), .ino with setup() to avoid `Multiple Definitions` Linker Error
  2. #include "ESP32_C3_ISR_Timer.h"           //https://github.com/khoih-prog/ESP32_C3_TimerInterrupt

Check the new multiFileProject example for a HOWTO demo.

—-

HOWTO Use analogRead() with ESP32 running WiFi and/or BlueTooth (BT/BLE)

Please have a look at ESP_WiFiManager Issue 39: Not able to read analog port when using the autoconnect example to have more detailed description and solution of the issue.

1. ESP32 has 2 ADCs, named ADC1 and ADC2

2. ESP32 ADCs functions

  • ADC1 controls ADC function for pins GPIO32-GPIO39
  • ADC2 controls ADC function for pins GPIO0, 2, 4, 12-15, 25-27

3.. ESP32 WiFi uses ADC2 for WiFi functions

Look in file adc_common.c

In ADC2, there’re two locks used for different cases:

  1. lock shared with app and Wi-Fi:
    ESP32:

    1.  When Wi-Fi using the `ADC2`, we assume it will never stop, so app checks the lock and returns immediately if failed.

    ESP32S2:

    1.  The controller's control over the ADC is determined by the arbiter. There is no need to control by lock.

  2. lock shared between tasks:
    when several tasks sharing the ADC2, we want to guarantee
    all the requests will be handled.
    Since conversions are short (about 31us), app returns the lock very soon,
    we use a spinlock to stand there waiting to do conversions one by one.

adc2_spinlock should be acquired first, then adc2_wifi_lock or rtc_spinlock.

  • In order to use ADC2 for other functions, we have to acquire complicated firmware locks and very difficult to do
  • So, it’s not advisable to use ADC2 with WiFi/BlueTooth (BT/BLE).
  • Use ADC1, and pins GPIO32-GPIO39
  • If somehow it’s a must to use those pins serviced by ADC2 (GPIO0, 2, 4, 12, 13, 14, 15, 25, 26 and 27), use the fix mentioned at the end of ESP_WiFiManager Issue 39: Not able to read analog port when using the autoconnect example to work with ESP32 WiFi/BlueTooth (BT/BLE).

—-

More useful Information

The ESP32_C3 has two timer groups, each one with only one general purpose hardware timer. All the timers are based on 64 bits counters and 16 bit prescalers.

The timer counters can be configured to count up or down and support automatic reload and software reload.

They can also generate alarms when they reach a specific value, defined by the software. The value of the counter can be read by
the software program.

Now with these new 16 ISR-based timers (while consuming only 1 hardware timer), the maximum interval is practically unlimited (limited only by unsigned long milliseconds). The accuracy is nearly perfect compared to software timers. The most important feature is they’re ISR-based timers Therefore, their executions are not blocked by bad-behaving functions / tasks.
This important feature is absolutely necessary for mission-critical tasks.

The ISR_Timer_Complex example will demonstrate the nearly perfect accuracy compared to software timers by printing the actual elapsed millisecs of each type of timers.
Being ISR-based timers, their executions are not blocked by bad-behaving functions / tasks, such as connecting to WiFi, Internet and Blynk services. You can also have many (up to 16) timers to use.
This non-being-blocked important feature is absolutely necessary for mission-critical tasks.
You’ll see blynkTimer Software is blocked while system is connecting to WiFi / Internet / Blynk, as well as by blocking task
in loop(), using delay() function as an example. The elapsed time then is very unaccurate

—-

How to use

Before using any Timer, you have to make sure the Timer has not been used by any other purpose.

Timer0, Timer1 are supported for ESP32_C3.

Using as follows:

  1. // Can be included as many times as necessary, without `Multiple Definitions` Linker Error
  2. #include "ESP32_C3_TimerInterrupt.h"
  4. // Init ESP32_C3 timer 0 and 1
  5. ESP32Timer ITimer0(0);
  6. ESP32Timer ITimer1(1);
  8. void setup()
  9. {
  10.   Serial.begin(115200);
  11.   while (!Serial);
  13.   delay(100);
  14.   ...
  16.   // Using ESP32  => 80 / 160 / 240MHz CPU clock ,
  17.   // For 64-bit timer counter
  18.   // For 16-bit timer prescaler up to 1024
  20.   // Interval in microsecs
  21.   if (ITimer0.attachInterruptInterval(TIMER0_INTERVAL_MS * 1000, TimerHandler0))
  22.   {
  23.     Serial.print(F("Starting  ITimer0 OK, millis() = ")); Serial.println(millis());
  24.   }
  25.   else
  26.     Serial.println(F("Can't set ITimer0. Select another freq. or timer"));
  28.   // Interval in microsecs
  29.   if (ITimer1.attachInterruptInterval(TIMER1_INTERVAL_MS * 1000, TimerHandler1))
  30.   {
  31.     Serial.print(F("Starting  ITimer1 OK, millis() = ")); Serial.println(millis());
  32.   }
  33.   else
  34.     Serial.println(F("Can't set ITimer1. Select another freq. or timer"));
  35. }

—-

Examples:

  1. Argument_None
  2. RPM_Measure
  3. SwitchDebounce
  4. TimerInterruptTest
  5. Change_Interval.
  6. ISR_16_Timers_Array
  7. ISR_16_Timers_Array_Complex
  8. multiFileProject. New

—-

Example TimerInterruptTest

https://github.com/khoih-prog/ESP32_C3_TimerInterrupt/blob/c593e912cd7a5c0d48b08cde15704aa916c1b1b9/examples/TimerInterruptTest/TimerInterruptTest.ino#L40-L179

—-

Debug Terminal Output Samples

1. ISR_16_Timers_Array_Complex on ESP32C3_DEV

The following is the sample terminal output when running example ISR_16_Timers_Array_Complex on ESP32C3_DEV to demonstrate of ISR Hardware Timer, especially when system is very busy or blocked. The 16 independent ISR timers are programmed to be activated repetitively after certain intervals, is activated exactly after that programmed interval !!!

  1. Starting ISR_16_Timers_Array_Complex on ESP32C3_DEV
  2. ESP32_C3_TimerInterrupt v1.8.0
  3. CPU Frequency = 160 MHz
  4. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 1, TIM_CLOCK_FREQ = 1000000.00
  5. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  6. [TISR] _timerIndex = 0, _timerGroup = 1
  7. [TISR] Timer freq = 100.00, _count = 0-10000
  8. [TISR] timer_set_alarm_value = 10000.00
  9. Starting ITimer OK, millis() = 2100
  10. SimpleTimer : 2, ms : 12116, Dms : 10004
  11. Timer : 0, programmed : 5000, actual : 5008
  12. Timer : 1, programmed : 10000, actual : 0
  13. Timer : 2, programmed : 15000, actual : 0
  14. Timer : 3, programmed : 20000, actual : 0
  15. Timer : 4, programmed : 25000, actual : 0
  16. Timer : 5, programmed : 30000, actual : 0
  17. Timer : 6, programmed : 35000, actual : 0
  18. Timer : 7, programmed : 40000, actual : 0
  19. Timer : 8, programmed : 45000, actual : 0
  20. Timer : 9, programmed : 50000, actual : 0
  21. Timer : 10, programmed : 55000, actual : 0
  22. Timer : 11, programmed : 60000, actual : 0
  23. Timer : 12, programmed : 65000, actual : 0
  24. Timer : 13, programmed : 70000, actual : 0
  25. Timer : 14, programmed : 75000, actual : 0
  26. Timer : 15, programmed : 80000, actual : 0
  27. SimpleTimer : 2, ms : 22196, Dms : 10080
  28. Timer : 0, programmed : 5000, actual : 5000
  29. Timer : 1, programmed : 10000, actual : 10000
  30. Timer : 2, programmed : 15000, actual : 15008
  31. Timer : 3, programmed : 20000, actual : 20008
  32. Timer : 4, programmed : 25000, actual : 0
  33. Timer : 5, programmed : 30000, actual : 0
  34. Timer : 6, programmed : 35000, actual : 0
  35. Timer : 7, programmed : 40000, actual : 0
  36. Timer : 8, programmed : 45000, actual : 0
  37. Timer : 9, programmed : 50000, actual : 0
  38. Timer : 10, programmed : 55000, actual : 0
  39. Timer : 11, programmed : 60000, actual : 0
  40. Timer : 12, programmed : 65000, actual : 0
  41. Timer : 13, programmed : 70000, actual : 0
  42. Timer : 14, programmed : 75000, actual : 0
  43. Timer : 15, programmed : 80000, actual : 0
  44. SimpleTimer : 2, ms : 32276, Dms : 10080
  45. Timer : 0, programmed : 5000, actual : 5000
  46. Timer : 1, programmed : 10000, actual : 10000
  47. Timer : 2, programmed : 15000, actual : 15000
  48. Timer : 3, programmed : 20000, actual : 20008
  49. Timer : 4, programmed : 25000, actual : 25008
  50. Timer : 5, programmed : 30000, actual : 30008
  51. Timer : 6, programmed : 35000, actual : 0
  52. Timer : 7, programmed : 40000, actual : 0
  53. Timer : 8, programmed : 45000, actual : 0
  54. Timer : 9, programmed : 50000, actual : 0
  55. Timer : 10, programmed : 55000, actual : 0
  56. Timer : 11, programmed : 60000, actual : 0
  57. Timer : 12, programmed : 65000, actual : 0
  58. Timer : 13, programmed : 70000, actual : 0
  59. Timer : 14, programmed : 75000, actual : 0
  60. Timer : 15, programmed : 80000, actual : 0
  61. SimpleTimer : 2, ms : 42356, Dms : 10080
  62. Timer : 0, programmed : 5000, actual : 5000
  63. Timer : 1, programmed : 10000, actual : 10000
  64. Timer : 2, programmed : 15000, actual : 15000
  65. Timer : 3, programmed : 20000, actual : 20000
  66. Timer : 4, programmed : 25000, actual : 25008
  67. Timer : 5, programmed : 30000, actual : 30008
  68. Timer : 6, programmed : 35000, actual : 35008
  69. Timer : 7, programmed : 40000, actual : 40008
  70. Timer : 8, programmed : 45000, actual : 0
  71. Timer : 9, programmed : 50000, actual : 0
  72. Timer : 10, programmed : 55000, actual : 0
  73. Timer : 11, programmed : 60000, actual : 0
  74. Timer : 12, programmed : 65000, actual : 0
  75. Timer : 13, programmed : 70000, actual : 0
  76. Timer : 14, programmed : 75000, actual : 0
  77. Timer : 15, programmed : 80000, actual : 0
  78. SimpleTimer : 2, ms : 52436, Dms : 10080
  79. Timer : 0, programmed : 5000, actual : 5000
  80. Timer : 1, programmed : 10000, actual : 10000
  81. Timer : 2, programmed : 15000, actual : 15000
  82. Timer : 3, programmed : 20000, actual : 20000
  83. Timer : 4, programmed : 25000, actual : 25000
  84. Timer : 5, programmed : 30000, actual : 30008
  85. Timer : 6, programmed : 35000, actual : 35008
  86. Timer : 7, programmed : 40000, actual : 40008
  87. Timer : 8, programmed : 45000, actual : 45008
  88. Timer : 9, programmed : 50000, actual : 50008
  89. Timer : 10, programmed : 55000, actual : 0
  90. Timer : 11, programmed : 60000, actual : 0
  91. Timer : 12, programmed : 65000, actual : 0
  92. Timer : 13, programmed : 70000, actual : 0
  93. Timer : 14, programmed : 75000, actual : 0
  94. Timer : 15, programmed : 80000, actual : 0
  95. SimpleTimer : 2, ms : 62516, Dms : 10080
  96. Timer : 0, programmed : 5000, actual : 5000
  97. Timer : 1, programmed : 10000, actual : 10000
  98. Timer : 2, programmed : 15000, actual : 15000
  99. Timer : 3, programmed : 20000, actual : 20000
  100. Timer : 4, programmed : 25000, actual : 25000
  101. Timer : 5, programmed : 30000, actual : 30000
  102. Timer : 6, programmed : 35000, actual : 35008
  103. Timer : 7, programmed : 40000, actual : 40008
  104. Timer : 8, programmed : 45000, actual : 45008
  105. Timer : 9, programmed : 50000, actual : 50008
  106. Timer : 10, programmed : 55000, actual : 55008
  107. Timer : 11, programmed : 60000, actual : 60008
  108. Timer : 12, programmed : 65000, actual : 0
  109. Timer : 13, programmed : 70000, actual : 0
  110. Timer : 14, programmed : 75000, actual : 0
  111. Timer : 15, programmed : 80000, actual : 0
  112. SimpleTimer : 2, ms : 72596, Dms : 10080
  113. Timer : 0, programmed : 5000, actual : 5000
  114. Timer : 1, programmed : 10000, actual : 10000
  115. Timer : 2, programmed : 15000, actual : 15000
  116. Timer : 3, programmed : 20000, actual : 20000
  117. Timer : 4, programmed : 25000, actual : 25000
  118. Timer : 5, programmed : 30000, actual : 30000
  119. Timer : 6, programmed : 35000, actual : 35000
  120. Timer : 7, programmed : 40000, actual : 40008
  121. Timer : 8, programmed : 45000, actual : 45008
  122. Timer : 9, programmed : 50000, actual : 50008
  123. Timer : 10, programmed : 55000, actual : 55008
  124. Timer : 11, programmed : 60000, actual : 60008
  125. Timer : 12, programmed : 65000, actual : 65008
  126. Timer : 13, programmed : 70000, actual : 70008
  127. Timer : 14, programmed : 75000, actual : 0
  128. Timer : 15, programmed : 80000, actual : 0
  129. SimpleTimer : 2, ms : 82676, Dms : 10080
  130. Timer : 0, programmed : 5000, actual : 5000
  131. Timer : 1, programmed : 10000, actual : 10000
  132. Timer : 2, programmed : 15000, actual : 15000
  133. Timer : 3, programmed : 20000, actual : 20000
  134. Timer : 4, programmed : 25000, actual : 25000
  135. Timer : 5, programmed : 30000, actual : 30000
  136. Timer : 6, programmed : 35000, actual : 35000
  137. Timer : 7, programmed : 40000, actual : 40000
  138. Timer : 8, programmed : 45000, actual : 45008
  139. Timer : 9, programmed : 50000, actual : 50008
  140. Timer : 10, programmed : 55000, actual : 55008
  141. Timer : 11, programmed : 60000, actual : 60008
  142. Timer : 12, programmed : 65000, actual : 65008
  143. Timer : 13, programmed : 70000, actual : 70008
  144. Timer : 14, programmed : 75000, actual : 75008
  145. Timer : 15, programmed : 80000, actual : 80008

2. TimerInterruptTest on ESP32C3_DEV

The following is the sample terminal output when running example TimerInterruptTest to demonstrate how to start/stop Hardware Timers.

  1. Starting TimerInterruptTest on ESP32C3_DEV
  2. ESP32_C3_TimerInterrupt v1.8.0
  3. CPU Frequency = 160 MHz
  4. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 0, TIM_CLOCK_FREQ = 1000000.00
  5. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  6. [TISR] _timerIndex = 0, _timerGroup = 0
  7. [TISR] Timer freq = 1.00, _count = 0-1000000
  8. [TISR] timer_set_alarm_value = 1000000.00
  9. Starting  ITimer0 OK, millis() = 212
  10. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 1, TIM_CLOCK_FREQ = 1000000.00
  11. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  12. [TISR] _timerIndex = 0, _timerGroup = 1
  13. [TISR] Timer freq = 0.33, _count = 0-3000000
  14. [TISR] timer_set_alarm_value = 3000000.00
  15. Starting  ITimer1 OK, millis() = 237
  16. Stop ITimer0, millis() = 5001
  17. Start ITimer0, millis() = 10002
  18. Stop ITimer1, millis() = 15001
  19. Stop ITimer0, millis() = 15003
  20. Start ITimer0, millis() = 20004
  21. Stop ITimer0, millis() = 25005
  22. Start ITimer1, millis() = 30002
  23. Start ITimer0, millis() = 30006

3. Change_Interval on ESP32C3_DEV

The following is the sample terminal output when running example Change_Interval to demonstrate how to change Timer Interval on-the-fly

  1. Starting Change_Interval on ESP32C3_DEV
  2. ESP32_C3_TimerInterrupt v1.8.0
  3. CPU Frequency = 160 MHz
  4. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 0, TIM_CLOCK_FREQ = 1000000.00
  5. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  6. [TISR] _timerIndex = 0, _timerGroup = 0
  7. [TISR] Timer freq = 0.50, _count = 0-2000000
  8. [TISR] timer_set_alarm_value = 2000000.00
  9. Starting  ITimer0 OK, millis() = 212
  10. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 1, TIM_CLOCK_FREQ = 1000000.00
  11. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  12. [TISR] _timerIndex = 0, _timerGroup = 1
  13. [TISR] Timer freq = 0.20, _count = 0-5000000
  14. [TISR] timer_set_alarm_value = 5000000.00
  15. Starting  ITimer1 OK, millis() = 237
  16. Time = 10001, Timer0Count = 5, Timer1Count = 2
  17. Time = 20002, Timer0Count = 10, Timer1Count = 4
  18. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 0, TIM_CLOCK_FREQ = 1000000.00
  19. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  20. [TISR] _timerIndex = 0, _timerGroup = 0
  21. [TISR] Timer freq = 0.25, _count = 0-4000000
  22. [TISR] timer_set_alarm_value = 4000000.00
  23. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 1, TIM_CLOCK_FREQ = 1000000.00
  24. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  25. [TISR] _timerIndex = 0, _timerGroup = 1
  26. [TISR] Timer freq = 0.10, _count = 0-10000000
  27. [TISR] timer_set_alarm_value = 10000000.00
  28. Changing Interval, Timer0 = 4000,  Timer1 = 10000
  29. Time = 30003, Timer0Count = 12, Timer1Count = 4

4. Argument_None on ESP32C3_DEV

The following is the sample terminal output when running example Argument_None

  1. Starting Argument_None on ESP32C3_DEV
  2. ESP32_C3_TimerInterrupt v1.8.0
  3. CPU Frequency = 160 MHz
  4. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 0, TIM_CLOCK_FREQ = 1000000.00
  5. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  6. [TISR] _timerIndex = 0, _timerGroup = 0
  7. [TISR] Timer freq = 1.00, _count = 0-1000000
  8. [TISR] timer_set_alarm_value = 1000000.00
  9. Starting  ITimer0 OK, millis() = 212
  10. [TISR] ESP32_C3_TimerInterrupt: _timerNo = 1, TIM_CLOCK_FREQ = 1000000.00
  11. [TISR] TIMER_BASE_CLK = 80000000, TIMER_DIVIDER = 80
  12. [TISR] _timerIndex = 0, _timerGroup = 1
  13. [TISR] Timer freq = 0.20, _count = 0-5000000
  14. [TISR] timer_set_alarm_value = 5000000.00
  15. Starting  ITimer1 OK, millis() = 237

—-

Debug

Debug is enabled by default on Serial.

You can also change the debugging level (TIMERINTERRUPT_LOGLEVEL) from 0 to 4

  1. // These define's must be placed at the beginning before #include "ESP32_C3_TimerInterrupt.h"
  2. // _TIMERINTERRUPT_LOGLEVEL_ from 0 to 4
  3. // Don't define _TIMERINTERRUPT_LOGLEVEL_ > 0. Only for special ISR debugging only. Can hang the system.
  4. #define TIMER_INTERRUPT_DEBUG         0
  5. #define _TIMERINTERRUPT_LOGLEVEL_     0

Troubleshooting

If you get compilation errors, more often than not, you may need to install a newer version of the core for Arduino boards.

Sometimes, the library will only work if you update the board core to the latest version because I am using newly added functions.

—-

Issues

Submit issues to: ESP32_C3_TimerInterrupt issues

TO DO

  1. Search for bug and improvement.

DONE

  1. Basic hardware timers for ESP32_C3.
  2. More hardware-initiated software-enabled timers
  3. Longer time interval
  4. Similar features for remaining Arduino boards such as SAMD21, SAMD51, SAM-DUE, nRF52, ESP8266, STM32, etc.
  5. Fix compiler errors due to conflict to some libraries.
  6. Add complex examples.
  7. Fix multiple-definitions linker error. Drop src_cpp and src_h directories
  8. Avoid deprecated functions.
  9. Optimize library code by using reference-passing instead of value-passing
    1. Suppress errors and warnings for new ESP32 core v2.0.4+
    2. Add support to
    • ESP32_C3 : LOLIN_C3_MINI, DFROBOT_BEETLE_ESP32_C3, ADAFRUIT_QTPY_ESP32C3, AirM2M_CORE_ESP32C3, XIAO_ESP32C3
    1. Use allman astyle and add utils

—-

Contributions and Thanks

Many thanks for everyone for bug reporting, new feature suggesting, testing and contributing to the development of this library.

Contributing

If you want to contribute to this project:

  • Report bugs and errors
  • Ask for enhancements
  • Create issues and pull requests
  • Tell other people about this library

License

  • The library is licensed under MIT

Copyright (C) 2021- Khoi Hoang