{"id":4677,"date":"2020-12-31T10:35:58","date_gmt":"2020-12-31T10:35:58","guid":{"rendered":"http:\/\/fastbitlab.com\/?p=4677"},"modified":"2022-11-22T17:28:18","modified_gmt":"2022-11-22T11:58:18","slug":"stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6","status":"publish","type":"post","link":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/","title":{"rendered":"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6"},"content":{"rendered":"
\n
\n
\n
\n

 <\/p>\n<\/div>\n

\n

I2C IRQ handler implementation Part 6<\/span><\/h1>\n
\n
\n
\n
<\/div>\n

 <\/p>\n<\/div>\n<\/div>\n<\/div>\n

In this article, let\u2019s handle the interrupt generated by the setting of the RXNE flag.<\/span><\/p>\n

Handling steps for the interrupt generated by the RXNE flag is similar to the handling of an interrupt generated by the TXE flag.<\/span><\/p>\n

Steps to be followed when the RXNE flag is set:<\/b><\/span><\/p>\n

    \n
  • When an RXNE flag is set, you have to do the data reception. <\/span><\/li>\n
  • Before starting the data reception, first, confirm the application\u2019s state. The data reception must begin only if the application state is busy in RX. Let\u2019s check the application\u2019s state by using the if statement, as shown in Figure 1.<\/span><\/li>\n<\/ul>\n
    \"I2C
    Figure 1. Code to check the application\u2019s state.<\/span><\/figcaption><\/figure>\n

     <\/p>\n

    In the case of blocking API or receive data API, there are two separate cases for the data reception.<\/span><\/p>\n

      \n
    1. Case 1: Length is equal to 1 (Figure 2).<\/span><\/li>\n
    2. Case 2: Length is greater than 1 (Figure 3).<\/span><\/li>\n<\/ol>\n
      \"I2C
      Figure 2. Code to data reception when length=1.<\/span><\/figcaption><\/figure>\n

       <\/p>\n

      \"I2C
      Figure 3. Code to data reception when length > 1.<\/span><\/figcaption><\/figure>\n

       <\/p>\n

      Similarly, you have to perform the data reception when the RXNE flag is set.<\/span><\/p>\n

        \n
      • Steps for the data reception is as follows:<\/span><\/li>\n<\/ul>\n

        1. Check whether the length (RxSize) is equal to 1 (Figure 4). <\/span><\/p>\n

        \"I2C
        Figure 4. Code to check whether the RxSize = 1.<\/span><\/figcaption><\/figure>\n

         <\/p>\n

        2. Refer to the master receive data API in Figure 5. Before the data reception begins, you have disabled the Acking and then cleared the address flag.<\/span><\/p>\n

        \"I2C
        Figure 5. Master receive data API.<\/span><\/figcaption><\/figure>\n

        In a similar way, you have to implement the non-blocking API.<\/span><\/p>\n

        3. When the transmission begins, the first flag which is going to be set is SB (start bit), which means first, the control will execute the block shown in Figure 6. After that ADDR flag is set, and the block shown in Figure 7 will get executed.<\/span><\/span><\/p>\n

        \"I2C
        Figure 6. Handle for the interrupt generated by the SB flag.<\/span><\/figcaption><\/figure>\n

         <\/p>\n

        \"I2C
        Figure 7. Handle for the interrupt generated by the ADDR flag.<\/span><\/figcaption><\/figure>\n

         <\/p>\n

        4.  Observe Figure 7. The ADDR flag is cleared while handling the interrupt generated by the ADDR flag, which is actually wrong because before clearing the ADDR flag, you need to disable the Acking. To overcome this problem, you need to change the I2C_ClearADDRFlag() function as follows:<\/span><\/span><\/p>\n

          \n
        • Change the parameters of I2C_ClearADDRFlag() to a pointer to the handle instead of a pointer to the base address of the peripheral (Figure 8) because we have to access the member elements of the handle structure.<\/span><\/li>\n<\/ul>\n
          \"I2C
          Figure 8. Definition of I2C_ClearADDRFlag().<\/span><\/figcaption><\/figure>\n

           <\/p>\n

            \n
          • Change the parameters of the I2C_ClearADDRFlag() prototype, as shown in Figure 9.<\/span><\/li>\n<\/ul>\n
            \"I2C
            Figure 9. Prototype of I2C_ClearADDRFlag().<\/span><\/figcaption><\/figure>\n

             <\/p>\n

              \n
            • Check for the device mode: Since we are going to code according to the mode of the device, first check whether the device is in master mode or slave mode. For that, you have to check the 0th bit of the SR2 register, as shown in Figure 10.<\/span><\/li>\n<\/ul>\n
              \"I2C
              Figure 10. Code to check the device mode.<\/span><\/figcaption><\/figure>\n

               <\/p>\n

                \n
              • If the device is in master mode (Figure 11), then check for the application\u2019s state. If the application\u2019s state is busy in RX and the RxSize = 1, then disable the ack. Once you disable the ack, the next step is to clear the ADDR flag. Look at Figure 11. The unused variable dummy_read is typecast to void. Otherwise, the compiler will issue warnings saying that the variable dummy_read is unused.<\/span><\/li>\n<\/ul>\n
                \"I2C
                Figure 11. Tasks to be performed when the device is in master mode and the application\u2019s state is busy in RX.<\/span><\/figcaption><\/figure>\n

                 <\/p>\n

                  \n
                • If the device is in master mode and the application\u2019s state is not busy in RX, then you can straight away clear the ADDR flag, as shown in Figure 12.<\/span><\/li>\n<\/ul>\n
                  \"I2C
                  Figure 12. Tasks to be performed when the device is in master mode, and the application\u2019s state is not busy in RX.<\/span><\/figcaption><\/figure>\n

                   <\/p>\n

                    \n
                  • If the device is in slave mode, then straight away clear the ADDR flag, as shown in Figure 13.<\/span><\/li>\n<\/ul>\n
                    \"I2C
                    Figure 13. Tasks to be performed when the device is in slave mode.<\/span><\/figcaption><\/figure>\n

                     <\/p>\n

                    5. Go back to the ISR handling of the RXNE. When RxSize=1, read one byte into the RxBuffer from the DR and then reduce the length, as shown in Figure 14.<\/span><\/span><\/p>\n

                    \"I2C
                    Figure 14. Code for the data reception when RxSize=1.<\/span><\/figcaption><\/figure>\n

                     <\/p>\n

                    6. Refer to the master receive data API in Figure 15. When the length is greater than 1, we have done the following things:<\/span><\/span><\/p>\n

                      \n
                    1. Clear the ADDR flag.<\/span><\/li>\n
                    2. Read the data into the buffer.<\/span><\/li>\n
                    3. When length reaches 2, disable the Acking.<\/span><\/li>\n
                    4. Generate the stop condition.<\/span><\/li>\n<\/ol>\n
                      \"I2C
                      Figure 15. Master receive data API.<\/span><\/figcaption><\/figure>\n

                       <\/p>\n

                      Now, you have to do the same things in the case of interrupt mode, as shown in Figure 16. When the length reaches 2, you can turn off the Acking. Otherwise, keep on reading the data into the data buffer and decrementing the RX length.<\/span><\/p>\n

                      \"I2C
                      Figure 16. Code for the data reception when RxSize > 1.<\/span><\/figcaption><\/figure>\n

                       <\/p>\n

                      7. When the RX length is equal to zero, then that is the indication for us to close the I2C data reception.<\/span><\/span><\/p>\n

                          Steps to close the I2C data reception:<\/span><\/span><\/p>\n

                        \n
                      • Generate the stop condition (Figure 17).<\/span><\/li>\n<\/ul>\n
                        \"I2C
                        Figure 17. Generation of the stop condition.<\/span><\/figcaption><\/figure>\n

                         <\/p>\n

                          \n
                        • Close the I2C RX: To close the I2C RX, implement an API called I2C_CloseReceiveData(), as shown in Figure 18.<\/span><\/li>\n<\/ul>\n
                          \"I2C
                          Figure 18. I2C_CloseReceiveData() API.<\/span><\/figcaption><\/figure>\n

                           <\/p>\n

                            \n
                          • Notify the application (Figure 19).<\/span><\/li>\n<\/ul>\n
                            \"I2C
                            Figure 19. Code to notify the application.<\/span><\/figcaption><\/figure>\n

                             <\/p>\n

                            8. All the tasks in Figure 14, Figure 16, Figure 17, Figure 18, and Figure 19 must be performed only when the device is master because we are creating the API for I2C master receive data. Therefore, before performing these tasks, you should confirm whether the device is master or not. You can ensure the device mode by checking the MSL bit of the status register at any point in time. If the MSL bit is set, you can say that the device is behaving as a master. Otherwise, the device will be in slave mode. This bit is set by the hardware as soon as the interface is in Master mode (SB=1) and cleared by the hardware after detecting the stop condition on the bus or loss of arbitration or when PE=0.<\/span><\/span><\/p>\n

                            Now let\u2019s check the device mode, as shown in Figure 20.<\/span><\/p>\n

                            \"I2C
                            Figure 20. Modified handle for the interrupt generated by the RXNE flag.<\/span><\/figcaption><\/figure>\n

                             <\/p>\n

                            9. The code in Figure 20 is quite long. In order to understand properly, you can create a new helper function (I2C_MasterHandleRXNEInterrupt()) by removing all the codes written for data reception, as shown in Figure 21, and the function argument will be a handle variable.<\/span><\/span><\/p>\n

                            \"I2C
                            Figure 21. Creation of helper function for the data reception.<\/span><\/figcaption><\/figure>\n

                             <\/p>\n

                            10.  All the code required for the data reception is pasted inside the definition part of the helper function, as shown in Figure 22.<\/span><\/span><\/p>\n

                            \"I2C
                            Figure 22. Implementation of helper function for handling RXNE interrupt.<\/span><\/figcaption><\/figure>\n

                             <\/p>\n

                            11.  Similarly, create one more helper function in order to handle the TXE interrupt (Figure 23).<\/span><\/span><\/p>\n

                            \"I2C
                            Figure 23. Implementation of helper function for handling TXE interrupt.<\/span><\/figcaption><\/figure>\n

                             <\/p>\n

                            12.  Call the helper function (I2C_MasterHandleTXEInterrupt()) from the IRQ handling, as shown in Figure 24.<\/span><\/span><\/p>\n

                            \"I2C
                            Figure 24. Call for helper function I2C_MasterHandleTXEInterrupt().<\/span><\/figcaption><\/figure>\n

                             <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

                              I2C IRQ handler implementation Part 6   In this article, let\u2019s handle the interrupt generated by the setting of the RXNE flag. Handling steps for the interrupt generated by the RXNE flag is similar to the handling of an interrupt generated by the TXE flag. Steps to be followed when the RXNE flag is […]<\/p>\n","protected":false},"author":1,"featured_media":4679,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ocean_post_layout":"","ocean_both_sidebars_style":"","ocean_both_sidebars_content_width":0,"ocean_both_sidebars_sidebars_width":0,"ocean_sidebar":"0","ocean_second_sidebar":"0","ocean_disable_margins":"enable","ocean_add_body_class":"","ocean_shortcode_before_top_bar":"","ocean_shortcode_after_top_bar":"","ocean_shortcode_before_header":"","ocean_shortcode_after_header":"","ocean_has_shortcode":"","ocean_shortcode_after_title":"","ocean_shortcode_before_footer_widgets":"","ocean_shortcode_after_footer_widgets":"","ocean_shortcode_before_footer_bottom":"","ocean_shortcode_after_footer_bottom":"","ocean_display_top_bar":"default","ocean_display_header":"default","ocean_header_style":"","ocean_center_header_left_menu":"0","ocean_custom_header_template":"0","ocean_custom_logo":0,"ocean_custom_retina_logo":0,"ocean_custom_logo_max_width":0,"ocean_custom_logo_tablet_max_width":0,"ocean_custom_logo_mobile_max_width":0,"ocean_custom_logo_max_height":0,"ocean_custom_logo_tablet_max_height":0,"ocean_custom_logo_mobile_max_height":0,"ocean_header_custom_menu":"0","ocean_menu_typo_font_family":"0","ocean_menu_typo_font_subset":"","ocean_menu_typo_font_size":0,"ocean_menu_typo_font_size_tablet":0,"ocean_menu_typo_font_size_mobile":0,"ocean_menu_typo_font_size_unit":"px","ocean_menu_typo_font_weight":"","ocean_menu_typo_font_weight_tablet":"","ocean_menu_typo_font_weight_mobile":"","ocean_menu_typo_transform":"","ocean_menu_typo_transform_tablet":"","ocean_menu_typo_transform_mobile":"","ocean_menu_typo_line_height":0,"ocean_menu_typo_line_height_tablet":0,"ocean_menu_typo_line_height_mobile":0,"ocean_menu_typo_line_height_unit":"","ocean_menu_typo_spacing":0,"ocean_menu_typo_spacing_tablet":0,"ocean_menu_typo_spacing_mobile":0,"ocean_menu_typo_spacing_unit":"","ocean_menu_link_color":"","ocean_menu_link_color_hover":"","ocean_menu_link_color_active":"","ocean_menu_link_background":"","ocean_menu_link_hover_background":"","ocean_menu_link_active_background":"","ocean_menu_social_links_bg":"","ocean_menu_social_hover_links_bg":"","ocean_menu_social_links_color":"","ocean_menu_social_hover_links_color":"","ocean_disable_title":"default","ocean_disable_heading":"default","ocean_post_title":"","ocean_post_subheading":"","ocean_post_title_style":"","ocean_post_title_background_color":"","ocean_post_title_background":0,"ocean_post_title_bg_image_position":"","ocean_post_title_bg_image_attachment":"","ocean_post_title_bg_image_repeat":"","ocean_post_title_bg_image_size":"","ocean_post_title_height":0,"ocean_post_title_bg_overlay":0.5,"ocean_post_title_bg_overlay_color":"","ocean_disable_breadcrumbs":"default","ocean_breadcrumbs_color":"","ocean_breadcrumbs_separator_color":"","ocean_breadcrumbs_links_color":"","ocean_breadcrumbs_links_hover_color":"","ocean_display_footer_widgets":"default","ocean_display_footer_bottom":"default","ocean_custom_footer_template":"0","ocean_post_oembed":"","ocean_post_self_hosted_media":"","ocean_post_video_embed":"","ocean_link_format":"","ocean_link_format_target":"self","ocean_quote_format":"","ocean_quote_format_link":"post","ocean_gallery_link_images":"off","ocean_gallery_id":[],"footnotes":""},"categories":[8],"tags":[23],"class_list":["post-4677","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-stm32-i2c-lectures","entry","has-media"],"yoast_head":"\nSTM32 I2C Lecture 49: I2C IRQ handler implementation Part 6<\/title>\n<meta name=\"description\" content=\"I2C IRQ handler implementation Part 6.In this article, let\u2019s handle the interrupt generated by the setting of the RXNE flag. Handling steps for the\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6\" \/>\n<meta property=\"og:description\" content=\"I2C IRQ handler implementation Part 6.In this article, let\u2019s handle the interrupt generated by the setting of the RXNE flag. Handling steps for the\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/\" \/>\n<meta property=\"og:site_name\" content=\"FastBit EBA\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/fastbiteba\/\" \/>\n<meta property=\"article:published_time\" content=\"2020-12-31T10:35:58+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-11-22T11:58:18+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2020\/12\/Figure-1-36.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1915\" \/>\n\t<meta property=\"og:image:height\" content=\"1021\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"FastBitLab\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@fastbiteba\" \/>\n<meta name=\"twitter:site\" content=\"@fastbiteba\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"FastBitLab\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/\"},\"author\":{\"name\":\"FastBitLab\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#\\\/schema\\\/person\\\/e32b38e733a0d76ffa7e6bc998652e5d\"},\"headline\":\"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6\",\"datePublished\":\"2020-12-31T10:35:58+00:00\",\"dateModified\":\"2022-11-22T11:58:18+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/\"},\"wordCount\":1357,\"commentCount\":3,\"publisher\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/Figure-1-36.png\",\"keywords\":[\"STM32 I2C Lectures\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/\",\"url\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/\",\"name\":\"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/Figure-1-36.png\",\"datePublished\":\"2020-12-31T10:35:58+00:00\",\"dateModified\":\"2022-11-22T11:58:18+00:00\",\"description\":\"I2C IRQ handler implementation Part 6.In this article, let\u2019s handle the interrupt generated by the setting of the RXNE flag. Handling steps for the\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/#primaryimage\",\"url\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/Figure-1-36.png\",\"contentUrl\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/Figure-1-36.png\",\"width\":1915,\"height\":1021,\"caption\":\"Figure 1. Code to check the application\u2019s state.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/\",\"name\":\"FastBit EBA\",\"description\":\"Your Online Academy of Embedded Systems\",\"publisher\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#organization\",\"name\":\"FastBit EBA\",\"url\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/logo-EzNrEnyr.png\",\"contentUrl\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/logo-EzNrEnyr.png\",\"width\":640,\"height\":640,\"caption\":\"FastBit EBA\"},\"image\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/fastbiteba\\\/\",\"https:\\\/\\\/x.com\\\/fastbiteba\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/fastbit-embedded-brain-academy-b3167b124\\\/\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UCa1REBV9hyrzGp2mjJCagBg\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#\\\/schema\\\/person\\\/e32b38e733a0d76ffa7e6bc998652e5d\",\"name\":\"FastBitLab\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9230d0f9bdef28b63a01e7ca274ee7b2e8ed9abe932ee564af8809caaf52a0c8?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9230d0f9bdef28b63a01e7ca274ee7b2e8ed9abe932ee564af8809caaf52a0c8?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9230d0f9bdef28b63a01e7ca274ee7b2e8ed9abe932ee564af8809caaf52a0c8?s=96&d=mm&r=g\",\"caption\":\"FastBitLab\"},\"description\":\"The FastBit Embedded Brain Academy uses the power of internet to bring the online courses related to the field of embedded system programming, Real time operating system, Embedded Linux systems, etc at your finger tip with very low cost. Backed with strong experience of industry, we have produced lots of courses with the customer enrolment over 3000+ across 100+ countries.\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6","description":"I2C IRQ handler implementation Part 6.In this article, let\u2019s handle the interrupt generated by the setting of the RXNE flag. Handling steps for the","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/","og_locale":"en_US","og_type":"article","og_title":"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6","og_description":"I2C IRQ handler implementation Part 6.In this article, let\u2019s handle the interrupt generated by the setting of the RXNE flag. Handling steps for the","og_url":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/","og_site_name":"FastBit EBA","article_publisher":"https:\/\/www.facebook.com\/fastbiteba\/","article_published_time":"2020-12-31T10:35:58+00:00","article_modified_time":"2022-11-22T11:58:18+00:00","og_image":[{"width":1915,"height":1021,"url":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2020\/12\/Figure-1-36.png","type":"image\/png"}],"author":"FastBitLab","twitter_card":"summary_large_image","twitter_creator":"@fastbiteba","twitter_site":"@fastbiteba","twitter_misc":{"Written by":"FastBitLab","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/#article","isPartOf":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/"},"author":{"name":"FastBitLab","@id":"https:\/\/fastbitlab.com\/blog\/#\/schema\/person\/e32b38e733a0d76ffa7e6bc998652e5d"},"headline":"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6","datePublished":"2020-12-31T10:35:58+00:00","dateModified":"2022-11-22T11:58:18+00:00","mainEntityOfPage":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/"},"wordCount":1357,"commentCount":3,"publisher":{"@id":"https:\/\/fastbitlab.com\/blog\/#organization"},"image":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/#primaryimage"},"thumbnailUrl":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2020\/12\/Figure-1-36.png","keywords":["STM32 I2C Lectures"],"articleSection":["Blog"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/","url":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/","name":"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6","isPartOf":{"@id":"https:\/\/fastbitlab.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/#primaryimage"},"image":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/#primaryimage"},"thumbnailUrl":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2020\/12\/Figure-1-36.png","datePublished":"2020-12-31T10:35:58+00:00","dateModified":"2022-11-22T11:58:18+00:00","description":"I2C IRQ handler implementation Part 6.In this article, let\u2019s handle the interrupt generated by the setting of the RXNE flag. Handling steps for the","breadcrumb":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/#primaryimage","url":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2020\/12\/Figure-1-36.png","contentUrl":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2020\/12\/Figure-1-36.png","width":1915,"height":1021,"caption":"Figure 1. Code to check the application\u2019s state."},{"@type":"BreadcrumbList","@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-49-i2c-irq-handler-implementation-part-6\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/fastbitlab.com\/blog\/"},{"@type":"ListItem","position":2,"name":"STM32 I2C Lecture 49: I2C IRQ handler implementation Part 6"}]},{"@type":"WebSite","@id":"https:\/\/fastbitlab.com\/blog\/#website","url":"https:\/\/fastbitlab.com\/blog\/","name":"FastBit EBA","description":"Your Online Academy of Embedded Systems","publisher":{"@id":"https:\/\/fastbitlab.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fastbitlab.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/fastbitlab.com\/blog\/#organization","name":"FastBit EBA","url":"https:\/\/fastbitlab.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/fastbitlab.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2026\/04\/logo-EzNrEnyr.png","contentUrl":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2026\/04\/logo-EzNrEnyr.png","width":640,"height":640,"caption":"FastBit EBA"},"image":{"@id":"https:\/\/fastbitlab.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/fastbiteba\/","https:\/\/x.com\/fastbiteba","https:\/\/www.linkedin.com\/in\/fastbit-embedded-brain-academy-b3167b124\/","https:\/\/www.youtube.com\/channel\/UCa1REBV9hyrzGp2mjJCagBg"]},{"@type":"Person","@id":"https:\/\/fastbitlab.com\/blog\/#\/schema\/person\/e32b38e733a0d76ffa7e6bc998652e5d","name":"FastBitLab","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/9230d0f9bdef28b63a01e7ca274ee7b2e8ed9abe932ee564af8809caaf52a0c8?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/9230d0f9bdef28b63a01e7ca274ee7b2e8ed9abe932ee564af8809caaf52a0c8?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9230d0f9bdef28b63a01e7ca274ee7b2e8ed9abe932ee564af8809caaf52a0c8?s=96&d=mm&r=g","caption":"FastBitLab"},"description":"The FastBit Embedded Brain Academy uses the power of internet to bring the online courses related to the field of embedded system programming, Real time operating system, Embedded Linux systems, etc at your finger tip with very low cost. Backed with strong experience of industry, we have produced lots of courses with the customer enrolment over 3000+ across 100+ countries."}]}},"_links":{"self":[{"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/posts\/4677","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/comments?post=4677"}],"version-history":[{"count":5,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/posts\/4677\/revisions"}],"predecessor-version":[{"id":12580,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/posts\/4677\/revisions\/12580"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/media\/4679"}],"wp:attachment":[{"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/media?parent=4677"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/categories?post=4677"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/tags?post=4677"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}