Repository navigation
Blocks for Interrupts bad generated code #136
Description
i think there is quite another problem. Blockly picks up the wrong C++ statement causing the interrupt not seen.
\the statement for interrupt in blockly should translate int: attachInterrupt (digitalPinToInterrupt (BUTTON), switchPressed, CHANGE);
The statement should be of the form " attachInterrupt (digitalPinToInterrupt (BUTTON), switchPressed, CHANGE);" .
Issue is that the nano and uno interrupt handling is not that flexible.
to do some Realtime event handling with Otto (and nano) you must have good interrupt handling.
a. the setup should include digitalWrite (BUTTON, HIGH), this has to do with internal pullup resistor. I don't know exactly why, Arduino reference may have more info. However this is not relevant for the attach issue.
b. the interrupt attach should definitely be of the form:
attachInterrupt (digitalPinToInterrupt (BUTTON), switchPressed, CHANGE);
the attach statement which currently is in the bloc does not work for some reason. This one does. I added
8000
a buzzer with two tones to check if it really works, it does. I forgot to save that one. I don't know WHY your original attach doesn't work, requires more study or testing.
c. within the ISR you included a statement Read Digital state Pin (BUTTON) = 10 , THAT SHOULD BE 1 , OR HIGH. The 10 doesn't work. This is also not relevant to the attach issue as its inside the ISR which can be anything.
But of course the main thing is b. above, to change the attachInterrupt statement in your interrupt block. There is also info on that in the Arduino reference site.
Perhaps its possible to make two versions of your bloc, in case there is a dependency i am not aware off.
Activity
logix5 commentedon Jan 13, 2022
[-]Interrupts blocks bad generated code[/-][+]Blocks for Interrupts bad generated code[/+]