42/42_EXT_03_42chips
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

mod04 ex00 ok

Browse Source
This commit is contained in:
hugo LAMY
2025-03-10 18:38:24 +01:00
parent 9bae6d3f49
commit e16552b4bc
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
module04/ex00/main.c
View File

@@ -13,10 +13,10 @@ typedef enum {
volatile uint8_t button_state = UP;
// Table 13-2 : interrupt types
#define INT0_LOW ((0 << ISC01) | (0 << ISC01))
#define INT0_LOGICAL ((0 << ISC01) | (1 << ISC01))
#define INT0_FALLING ((1 << ISC01) | (0 << ISC01))
#define INT0_RAISING ((1 << ISC01) | (1 << ISC01))
#define INT0_LOW ((0 << ISC01) | (0 << ISC00))
#define INT0_LOGICAL ((0 << ISC01) | (1 << ISC00))
#define INT0_FALLING ((1 << ISC01) | (0 << ISC00))
#define INT0_RAISING ((1 << ISC01) | (1 << ISC00))
// use interruption to change led1 state when button1 is pressed
int main() {
@@ -34,10 +34,10 @@ int main() {
}
ISR(INT0_vect) {
_delay_ms(50);
button_state = (button_state == UP) ? DOWN : UP;
if (button_state == UP) {
TOGGLE_ELEM(LED1);
}
// EIFR = (1 << INTF0); // 13.2.3 : clear flag, why ? i think it only indicates that a trigger event has occured
_delay_ms(50); // for debounce, bad idea to put it here in more complexe codes, it is blocking
EIFR |= (1 << INTF0); // 13.2.3 : clear flag, when the flag is set it triggers the interrupt, and eventhough it should be clear by the trigger, it can be set again by the bouncing
}