{"id":1355,"date":"2024-06-25T13:22:26","date_gmt":"2024-06-25T13:22:26","guid":{"rendered":"https:\/\/iotthinghub.com\/?p=1355"},"modified":"2024-08-11T15:34:39","modified_gmt":"2024-08-11T15:34:39","slug":"external-interrupt","status":"publish","type":"post","link":"https:\/\/iotthinghub.com\/?p=1355","title":{"rendered":"External interrupt"},"content":{"rendered":"\n
\n
\n

An interrupt is a hardware initiated procedure that interrupts whatever program is currently executing. In AVR an interrupt is a service routine that executed when it is called and back to the main program where it is halted after executing service routine. In AVR there are two types of interrupts.<\/p>\n\n\n\n

i. External interrupts<\/p>\n\n\n\n

In external interrupt external source causes interrupt. Some pins are defined as external pin for generating Interrupt, whenever any eternal pin is pressed if active, then the corresponding service routine will execute first halting the main program. After the executing the interrupt service routine the main program will continue with where it has been halting. <\/p>\n<\/div>\n\n\n\n

\n
\"\"
External Interrupt PIN<\/figcaption><\/figure>\n<\/div>\n<\/div>\n\n\n\n

ii. Internal interrupts<\/p>\n\n\n\n

Those interrupts can be occurred by using program. In interrupts there is an important factor which is purity. Each interrupt will execute according to there purity. Suppose both INT0 and INT1 external interrupt pin has been pressed at the same time, then only INT0 will be executed. Lets look at the purity according to the datasheet of ATmega32 provide-<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In this article we begin our journey with external interrupt only. Internal interrupt will be discussed later but the fundamental remain the same. Before we discuss about the register available and our task lets discuss about the bits of a register and there operation.<\/p>\n\n\n\n

Bit Operation -> SREG(Status Register)<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the Status Register there is 8bit=1byte. To enable all interrupt we need to set the bit 7 i.e. I bit. Since according to C program to set a particular bit<\/p>\n\n\n

\n      variable_name |=(1<<bit position); \/\/ To set a particular bit\n<\/pre><\/div>\n\n\n
And to clear a particular bit<\/p>\n\n\n
\n      variable_name &=~(1<<bit position); \/\/ To clear a particular bit\n<\/pre><\/div>\n\n\n
We need to set the I bit of Status register without affecting the other bits. So we use C control logic to all of our register section. So that the condition to<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
The R\/W indicates that those bits can be both read and write. Note that the initial value indicates that the default value is 0, means that initially the bit is clear. So no need to clears the bits first. Now looks at the registers that are available for external interrupts<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
To work with interrupts three steps must be setup<\/p>\n\n\n\n
    \n
  1. Set the global Interrupt Enable bit in SREG Register.<\/li>\n\n\n\n
  2. Initialize the interrupt by appropriate configuring the MCUCR, MCUCSR and GICR register.<\/li>\n\n\n\n
  3. Define the appropriate Interrupt Service Routine (ISR) for interrupt.<\/li>\n<\/ol>\n\n\n\n
    Step1:<\/strong>  To set the Global Interrupt Enable bit<\/p>\n\n\n
    \n    #include<avr\/interrupt.h>\n    sei(); or SREG|=(1<<I);\n<\/pre><\/div>\n\n\n
    To clear Global Interrupt Enable bit<\/p>\n\n\n
    \n    #include<avr\/interrupt.h>\n    cli(); or SREG&=~(1<<I);\n<\/pre><\/div>\n\n\n
    Note that to use an interrupt we should need a header file- #include<avr\/interrupt.h><\/p>\n\n\n\n
    Step2:<\/strong> Lets make a simple program that set PORTC of Atmega 32 from up to down and when an interrupt occur it set PORTC from down to up. In this case we use INT0 pin and the control logic is a rising edge of INT0 generates an interrupt. In first case we already enable the Global interrupt enable bit. So our target is to enable the INT0 (External Interrupt request 0) bit and then the control logic.<\/p>\n\n\n
    \nsei();   \/\/SREG|=(1<<I);\t\t\t    \/\/Global interrupt enable\nGICR |=(1<<INT0);\t\t\t\t\t\t\/\/External Interrupt Request 0 Enable\nMCUCR|=(1<<ISC00)|(1<<ISC01);\t\t  \/\/The rising edge of INT0 generates an interrupt request\n<\/pre><\/div>\n\n\n
    PORTC from up to down<\/p>\n\n\n
    \n   void uptodown(void)\n   {\n      for(int16_t i=0;i<=7;i++){\n          PORTC |=(1<<i);  _delay_ms(50);\n          PORTC &=(~(1<<i));_delay_ms(50);\n          }\n  }\n<\/pre><\/div>\n\n\n
    PORT from down to up <\/p>\n\n\n
    \n   void downtoup(void)\n   {\n      for(int16_t i=7;i>=0;i--){\n          PORTC |=(1&lt;&lt;i); _delay_ms(50);\n          PORTC &amp;=(~(1&lt;&lt;i)); _delay_ms(50);\n          }\n   }\n<\/pre><\/div>\n\n\n
    Step3:<\/strong> In this step we have to define appropriate Interrupt service routine (ISR). An interrupt routine is defined with ISR(). This micro register and () mark the routine as an interrupt handler for the specific peripheral. The following is an example definition of a handler for the INT0 interrupt.<\/p>\n\n\n
    \n #include<avr\/interrupt.h>\n ISR(INT0_vect)\n {\n   ;\/\/user defined code here\n  }   \n<\/pre><\/div>\n\n\n
    \n
    \n
    \"\"<\/a>
    download<\/figcaption><\/figure>\n<\/div>\n\n\n\n
    \n
    ISR Vector.pdf<\/a> OR ISR Vector.doc<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n
    OR simply open any internet browser and go to: <\/p>\n\n\n\n
    file:\/\/\/C:\/WinAVR-20100110\/doc\/avr-libc\/avr-libc-user-manual\/index.html<\/a><\/p>\n\n\n\n
    OR open it in your computer -> C:\/WinAVR-20100110\/doc\/avr-libc\/avr-libc-user-manual\/index.html<\/p>\n\n\n\n
                            –>Library Reference<\/p>\n\n\n\n
                            –><avr\/interrupt.h>: Interrupts  <\/p>\n\n\n\n
    Download the int0.c and int0.h files. The main program as follow –<\/p>\n\n\n
    \n\/************************************************************************************************\n*************************************************************************************************\nThis program will set PORTC form up-to-down and down-to-up when external trigger to INT0 bit\n************************************************************************************************\n***********************************************************************************************\/\n#include<avr\/io.h>\n#include<util\/delay.h>\n#include<avr\/interrupt.h>\n#include"int0.h"\nuint16_t sample=0;\nint main(void)\n{\n  DDRC=0xFF;\t\t\t\/\/ port c for output\n  int_int0(); \t\t\/\/INT0 interrupt enable call\n  while(1)\n  {\n    sample ? uptodown() : downtoup();\n  }\n  return 0;\n}\nISR(INT0_vect)\n{\n   sample^=0x01;\t\t\/\/Toggle condition\n}\n<\/pre><\/div>\n\n\n
    Note that in header file we include #include<avr\/interrupt.h> , that is because in INT0 initialization we include sei(); function that is the function of #include<avr\/interrupt.h> header file<\/p>\n\n\n\n
    \n
    \n
    \n
    download<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
    \n
    Download the full program with proteus simulation<\/a><\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
    An interrupt is a hardware initiated procedure that interrupts whatever program is currently executing. In AVR an interrupt is a service routine that executed when it is called and back to the main program where it is halted after executing service routine. In AVR there are two types of interrupts. i. External interrupts In external […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-1355","post","type-post","status-publish","format-standard","hentry","category-eternal-interrupts"],"_links":{"self":[{"href":"https:\/\/iotthinghub.com\/index.php?rest_route=\/wp\/v2\/posts\/1355","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/iotthinghub.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/iotthinghub.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/iotthinghub.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/iotthinghub.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1355"}],"version-history":[{"count":43,"href":"https:\/\/iotthinghub.com\/index.php?rest_route=\/wp\/v2\/posts\/1355\/revisions"}],"predecessor-version":[{"id":2569,"href":"https:\/\/iotthinghub.com\/index.php?rest_route=\/wp\/v2\/posts\/1355\/revisions\/2569"}],"wp:attachment":[{"href":"https:\/\/iotthinghub.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1355"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/iotthinghub.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1355"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/iotthinghub.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}