forked from khoih-prog/TimerInterrupt_Generic
-
Notifications
You must be signed in to change notification settings - Fork 0
/
SwitchDebounce.ino
193 lines (156 loc) · 7.3 KB
/
SwitchDebounce.ino
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
/****************************************************************************************************************************
SwitchDebounce.ino
For STM32 boards
Written by Khoi Hoang
Built by Khoi Hoang https://github.com/khoih-prog/TimerInterrupt_Generic
Licensed under MIT license
Now even you use all these new 16 ISR-based timers,with their maximum interval practically unlimited (limited only by
unsigned long miliseconds), you just consume only one STM32 timer and avoid conflicting with other cores' tasks.
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.
*****************************************************************************************************************************/
/*
Notes:
Special design is necessary to share data between interrupt code and the rest of your program.
Variables usually need to be "volatile" types. Volatile tells the compiler to avoid optimizations that assume
variable can not spontaneously change. Because your function may change variables while your program is using them,
the compiler needs this hint. But volatile alone is often not enough.
When accessing shared variables, usually interrupts must be disabled. Even with volatile,
if the interrupt changes a multi-byte variable between a sequence of instructions, it can be read incorrectly.
If your data is multiple variables, such as an array and a count, usually interrupts need to be disabled
or the entire sequence of your code which accesses the data.
Switch Debouncing uses high frequency hardware timer 50Hz == 20ms) to measure the time from the SW is pressed,
debouncing time is 100ms => SW is considered pressed if timer count is > 5, then call / flag SW is pressed
When the SW is released, timer will count (debounce) until more than 50ms until consider SW is released.
We can set to flag or call a function whenever SW is pressed more than certain predetermined time, even before
SW is released.
*/
#if !( defined(STM32F0) || defined(STM32F1) || defined(STM32F2) || defined(STM32F3) ||defined(STM32F4) || defined(STM32F7) || \
defined(STM32L0) || defined(STM32L1) || defined(STM32L4) || defined(STM32H7) ||defined(STM32G0) || defined(STM32G4) || \
defined(STM32WB) || defined(STM32MP1) || defined(STM32L5) )
#error This code is designed to run on STM32F/L/H/G/WB/MP1 platform! Please check your Tools->Board setting.
#endif
// These define's must be placed at the beginning before #include "TimerInterrupt_Generic.h"
// _TIMERINTERRUPT_LOGLEVEL_ from 0 to 4
// Don't define _TIMERINTERRUPT_LOGLEVEL_ > 0. Only for special ISR debugging only. Can hang the system.
// Don't define TIMER_INTERRUPT_DEBUG > 2. Only for special ISR debugging only. Can hang the system.
#define TIMER_INTERRUPT_DEBUG 0
#define _TIMERINTERRUPT_LOGLEVEL_ 0
#include "TimerInterrupt_Generic.h"
#ifndef LED_BUILTIN
#define LED_BUILTIN PB0 // Pin 33/PB0 control on-board LED_GREEN on F767ZI
#endif
#ifndef LED_BLUE
#define LED_BLUE PB7 // Pin 73/PB7 control on-board LED_BLUE on F767ZI
#endif
#ifndef LED_RED
#define LED_RED PB14 // Pin 74/PB14 control on-board LED_BLUE on F767ZI
#endif
unsigned int SWPin = D7;
#define TIMER1_INTERVAL_MS 20
#define DEBOUNCING_INTERVAL_MS 100
#define LONG_PRESS_INTERVAL_MS 5000
#define LOCAL_DEBUG 1
// Depending on the board, you can select STM32 Hardware Timer from TIM1-TIM22
// For example, F767ZI can select Timer from TIM1-TIM14
// If you select a Timer not correctly, you'll get a message from ci[ompiler
// 'TIMxx' was not declared in this scope; did you mean 'TIMyy'?
// Init STM32 timer TIM1
STM32Timer ITimer(TIM1);
volatile bool SWPressed = false;
volatile bool SWLongPressed = false;
void TimerHandler()
{
static unsigned int debounceCountSWPressed = 0;
static unsigned int debounceCountSWReleased = 0;
#if (TIMER_INTERRUPT_DEBUG > 1)
static unsigned long SWPressedTime;
static unsigned long SWReleasedTime;
unsigned long currentMillis = millis();
#endif
static bool started = false;
if (!started)
{
started = true;
pinMode(SWPin, INPUT_PULLUP);
}
if ( (!digitalRead(SWPin)) )
{
// Start debouncing counting debounceCountSWPressed and clear debounceCountSWReleased
debounceCountSWReleased = 0;
if (++debounceCountSWPressed >= DEBOUNCING_INTERVAL_MS / TIMER1_INTERVAL_MS)
{
// Call and flag SWPressed
if (!SWPressed)
{
#if (TIMER_INTERRUPT_DEBUG > 1)
SWPressedTime = currentMillis;
Serial.print("SW Press, from millis() = "); Serial.println(SWPressedTime - DEBOUNCING_INTERVAL_MS);
#endif
SWPressed = true;
// Do something for SWPressed here in ISR
// But it's better to use outside software timer to do your job instead of inside ISR
//Your_Response_To_Press();
}
if (debounceCountSWPressed >= LONG_PRESS_INTERVAL_MS / TIMER1_INTERVAL_MS)
{
// Call and flag SWLongPressed
if (!SWLongPressed)
{
#if (TIMER_INTERRUPT_DEBUG > 1)
Serial.print("SW Long Pressed, total time ms = "); Serial.print(currentMillis);
Serial.print(" - "); Serial.print(SWPressedTime - DEBOUNCING_INTERVAL_MS);
Serial.print(" = "); Serial.println(currentMillis - SWPressedTime + DEBOUNCING_INTERVAL_MS);
#endif
SWLongPressed = true;
// Do something for SWLongPressed here in ISR
// But it's better to use outside software timer to do your job instead of inside ISR
//Your_Response_To_Long_Press();
}
}
}
}
else
{
// Start debouncing counting debounceCountSWReleased and clear debounceCountSWPressed
if ( SWPressed && (++debounceCountSWReleased >= DEBOUNCING_INTERVAL_MS / TIMER1_INTERVAL_MS))
{
#if (TIMER_INTERRUPT_DEBUG > 1)
SWReleasedTime = currentMillis;
// Call and flag SWPressed
Serial.print("SW Released, from millis() = "); Serial.println(SWReleasedTime);
#endif
SWPressed = false;
SWLongPressed = false;
// Do something for !SWPressed here in ISR
// But it's better to use outside software timer to do your job instead of inside ISR
//Your_Response_To_Release();
// Call and flag SWPressed
#if (TIMER_INTERRUPT_DEBUG > 1)
Serial.print("SW Pressed total time ms = "); Serial.println(SWReleasedTime - SWPressedTime);
#endif
debounceCountSWPressed = 0;
}
}
}
void setup()
{
Serial.begin(115200);
while (!Serial);
delay(100);
Serial.print(F("\nStarting SwitchDebounce on ")); Serial.println(BOARD_NAME);
Serial.println(STM32_TIMER_INTERRUPT_VERSION);
Serial.println(TIMER_INTERRUPT_GENERIC_VERSION);
Serial.print(F("CPU Frequency = ")); Serial.print(F_CPU / 1000000); Serial.println(F(" MHz"));
// Interval in microsecs
if (ITimer.attachInterruptInterval(TIMER1_INTERVAL_MS * 1000, TimerHandler))
{
Serial.print(F("Starting ITimer OK, millis() = ")); Serial.println(millis());
}
else
Serial.println(F("Can't set ITimer. Select another freq. or timer"));
}
void loop()
{
}