{"id":4795,"date":"2021-01-04T11:19:35","date_gmt":"2021-01-04T11:19:35","guid":{"rendered":"http:\/\/fastbitlab.com\/?p=4795"},"modified":"2022-11-23T09:52:15","modified_gmt":"2022-11-23T04:22:15","slug":"stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1","status":"publish","type":"post","link":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/","title":{"rendered":"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1"},"content":{"rendered":"
\n
\n
\n
\n

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

\n

Exercise : Testing I2C interrupt APIs part 1<\/span><\/h1>\n
\n
\n
\n

 <\/p>\n

<\/div>\n

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

\n
\n<\/div>\n

Now let\u2019s test the interrupt related code and APIs using an application.<\/span><\/p>\n

Consider the same exercise i2c_master_rx_testing (Figure 1) that we coded while testing our MasterSendData and MasterReceiveData APIs.<\/span><\/p>\n

\"Testing
Figure 1. Exercise i2c_master_rx_testing.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

Steps for <\/b>testing I2C interrupt APIs:<\/b><\/span><\/p>\n

1. Create a source file: Copy the i2c_master_rx_testing file shown in Figure 1 and paste it under the src. <\/span><\/p>\n

2. Change the name to 012i2c_master_rx_testingIT.c, as shown in Figure 2, and save it by pressing ok.<\/span><\/p>\n

\"Testing
Figure 2. Naming the exercise.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

3.Exclude the 011i2c_master_rx_testing.c file from the build: Right-click on the file, go to properties (Figure 3), tick the checkbox named exclude resource from the build, and click on apply (Figure 4).<\/span><\/span><\/p>\n

\"
Figure 3. Excluding the old source file from the build (Step 1).<\/span><\/figcaption><\/figure>\n

 <\/p>\n

\"Testing
Figure 4. Excluding the old source file from the build (step 2).<\/span><\/figcaption><\/figure>\n

 <\/p>\n

4.Change all the APIs to IT mode APIs.<\/span><\/p>\n

5.No need to change GPIO_ButtonInit(), I2C1_GPIOInits(), I2C1_Inits(), peripheral control and I2C_ManageAcking() APIs (Figure 5). You must keep the while statement used to wait till the button is pressed, the delay function, and the statement to send the command code 0x51 (Figure 6).<\/span><\/p>\n

\"Testing
Figure 5. Code that does not need modification.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

\"Testing
Figure 6. Code that does not need modification.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

6. Replace I2C_MasterSendData() API with I2C_MasterSendDataIT(), as shown in Figure 7. Remember that you have to check the return value of MasterSendDataIT() since it returns a busy state variable (Figure 8). If the busy state is BUSY_IN_TX or BUSY_IN_RX, then the application has to wait until the state becomes I2C ready.<\/span><\/span><\/p>\n

\"Testing
Figure 7. Replacing I2C_MasterSendData() API with I2C_MasterSendDataIT().<\/span><\/figcaption><\/figure>\n

 <\/p>\n

\"Testing
Figure 8. Definition of I2C_MasterSendDataIT().<\/span><\/figcaption><\/figure>\n

 <\/p>\n

7. Make the I2C_MasterSendDataIT() wait until the application\u2019s state becomes I2C_READY using a while loop, as shown in Figure 9.<\/span><\/span><\/p>\n

\"Testing
Figure 9. Code to make the I2C_MasterSendDataIT() wait.<\/span><\/figcaption><\/figure>\n

If the MasterSendDataIT() function returns a value not equal to I2C_READY, then the application hangs in the while loop. Otherwise, the application proceeds to the next statement.<\/span><\/p>\n

 <\/p>\n

8. Replace I2C_MasterReceiveData() API with I2C_MasterReceiveDataIT(), as shown in Figure 10.<\/span><\/span><\/p>\n

\"Testing
Figure 10. Replacing I2C_MasterReceiveData() API with I2C_MasterReceiveDataIT().<\/span><\/figcaption><\/figure>\n

 <\/p>\n

9. Using a while loop, wait till the application\u2019s state becomes I2C_READY (Figure 11).<\/span><\/span><\/p>\n

\"Testing
Figure 11. Code to make the I2C_MasterReceiveDataIT() wait.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

10.  Command code 0x52 is sent, as shown in Figure 12. Again, replace remaining I2C_MasterSendData() and I2C_MasterReceiveData() with I2C_MasterSendDataIT() and I2C_MasterReceiveDataIT(), respectively (Figure 12).<\/span><\/span><\/p>\n

\"Testing
Figure 12. Replacing the APIs.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

In Figure 12, the rcv_buf is a global buffer.<\/span><\/p>\n

11. If you want to use semi hosting, then you can enable the printf statement in Figure 13.<\/span><\/span><\/p>\n

\"Testing
Figure 13. Code for semi hosting.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

12.You have to do the IRQ config of the I2C peripheral since you are communicating using interrupts. Now let\u2019s do I2C IRQ configuration using I2C_IRQInterruptConfig API after peripheral configuration, as shown in Figure 14. <\/span><\/span><\/p>\n

You have to mention the IRQ number of the interrupt as a parameter of the I2C_IRQInterruptConfig API. The I2C event interrupt and error interrupts are enabled by using IRQ numbers IRQ_NO_I2C1_EV and IRQ_NO_I2C1_ER, respectively (Figure 14).<\/span><\/p>\n

\"Testing
Figure 14. IRQ config of the I2C peripheral.<\/span><\/figcaption><\/figure>\n

You may also configure the priority, but that is not necessary. The priority doesn\u2019t matter here since you have only I2C interrupts.<\/span><\/p>\n

13. Implement the interrupt service routines for I2C1 event interrupt and I2C1 error interrupt:<\/span><\/span><\/p>\n

    \n
  • Go to the startup code(startup_stm32.s) to get the ISR name.<\/span><\/li>\n
  • Search for I2C1, as shown in Figure 15.<\/span><\/li>\n<\/ul>\n
    \"Testing
    Figure 15. Search for ISR name.<\/span><\/figcaption><\/figure>\n

     <\/p>\n

      \n
    • Copy the ISR names, shown in Figure 16.<\/span><\/li>\n<\/ul>\n
      \"Testing
      Figure 16. Copy the ISR names.<\/span><\/figcaption><\/figure>\n

       <\/p>\n

        \n
      • Go to the application and create the IRQ handlers at the end, as shown in Figure 17.<\/span><\/li>\n<\/ul>\n
        \"Testing
        Figure 17. Creation of IRQ handlers.<\/span><\/figcaption><\/figure>\n

         <\/p>\n

          \n
        • Inside IRQ handlers of Figure 17, you have to call the IRQ handling APIs, which are already developed. Now call I2C_EV_IRQHandling, as shown in Figure 18, and pass the address of the handler (I2C1Handle) as a parameter.<\/span><\/li>\n<\/ul>\n
          \"Testing
          Figure 18. Calling the IRQ handling APIs inside the IRQ handlers.<\/span><\/figcaption><\/figure>\n

           <\/p>\n

          Whenever an event happens during the I2C communication, the I2C1 event handler will be called, where the event IRQ handling APIs are called in order to decode that event and take the appropriate action. Whereas in the case of error, IRQ handling APIs are called.<\/span><\/p>\n

            \n
          • Once the control enters into the IRQHandling API, the IRQHandling API notifies the application about the different events through the callbacks. Therefore now you have to implement I2C_ApplicationEventCallback() in your application.<\/span><\/li>\n<\/ul>\n

            a. Create the function I2C_ApplicationEventCallback() (Figure 19).<\/span><\/p>\n

            \"Testing
            Figure 19. Creation of I2C_ApplicationEventCallback().<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            b. Figure 20 shows the various events generated by the driver and are defined in the driver header file. You can check for all these events.<\/span><\/p>\n

            \"Testing
            Figure 20. Various events generated by the driver.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            c. For example, in our application, let\u2019s check for TX complete, RX complete, and errors in the semi hosting, as shown in Figure 21.<\/span><\/p>\n

            \"Testing
            Figure 21. Checking the generation of various events.<\/span><\/figcaption><\/figure>\n

            Here I2C_ERROR_AF means ACK failure. Now the question is, why the ACK failure happens? For example, in master, the ACK failure happens when a slave fails to send ACK for the byte sent from the master. That means the master has sent 1 byte but didn\u2019t receive the ACK from the slave, resulting in ACK failure.<\/span><\/p>\n

             <\/p>\n

            d. When ACK failure occurs in the case of a master, then you can conclude something like slave device might have been removed from the bus or slave device might have gone bad or it may not want more data. Therefore, the master should close the communication by calling I2C_CloseSendData() API, as shown in Figure 22, and should not send more data to the slave.<\/span><\/p>\n

            \"Testing
            Figure 22. Call for I2C_CloseSendData() API.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            e. In the definition of I2C_CloseSendData() API (Figure 23), we turn off a couple of interrupts, and we make TxRx state as I2C_READY, TxBuffer=NULL, and TxLen=0.<\/span><\/p>\n

            \"Testing
            Figure 23. Definition of I2C_CloseSendData() API.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            f. The stop condition is didn\u2019t generated in the CloseSendData() API. Therefore, you have to generate the stop condition in the callback function to release the bus. There is an API to generate the stop condition, which is a private API. But if the application wants to release the bus, then the application should call generate stop condition API. Therefore, now you have to make this API as public instead of private. For that, first cut the API shown in Figure 24, then go to the driver file and paste the API under the peripheral control APIs section and remove the static keyword (Figure 25).<\/span><\/p>\n

            Also, remove the static keyword from the definition of GenerateStopCondition() API.<\/span><\/p>\n

            \"Testing
            Figure 24. Prototype of private generate stop condition function.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            \"Testing
            Figure 25. Prototype of generate stop condition function.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            Since the GenerateStopCondition() API is made public, now you can call it from the application callback function, as shown in Figure 26.<\/span><\/p>\n

            \"Testing
            Figure 26. Call for GenerateStopCondition() API from the application callback function.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            g. Look at Figure 27. If ACK failure occurs in the very first line, then the application should not go further. Because the ACK failure happened in the first line itself and for our application, executing the second line without executing the first line doesn\u2019t make any sense. Therefore, the program control must hang in the application callback function (Figure 27) to pause code execution.<\/span><\/p>\n

            \"Testing
            Figure 27. Code to hang in the application callback function.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            14.  Since you have used a printf statement, it is necessary to enable the semi hosting (Figure 28 and 29).<\/span><\/span><\/p>\n

            \"Testing
            Figure 28. Enabling semi hosting.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            \"Testing
            Figure 29. Enabling semi hosting.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            15.  On the Arduino side, download the sketch 002 I2CSlaveTxString (Figure 30).<\/span><\/span><\/p>\n

            \"Testing
            Figure 30. Arduino sketch 002 I2CSlaveTxString.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            16. Compile the code (Figure 31).<\/span><\/span><\/p>\n

            \"Testing
            Figure 31. Code compilation.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            17.  There seems to be one warning, as shown in Figure 32.<\/span><\/span><\/p>\n

            \"Testing
            Figure 32. Results of compilation.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            18. To solve this problem, you have to extern the initialise_monitor_handles() shown in Figure 33 by enabling the statement in Figure 34.<\/span><\/span><\/p>\n

            \"Testing
            Figure 33. Call for initialise_monitor_handles().<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            \"Testing
            Figure 34. Making function initialise_monitor_handles() as extern.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            19.  Again, build the project. Now the project builds successfully without any errors (Figure 35).<\/span><\/span><\/p>\n

            \"Testing
            Figure 35. Results of compilation.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            20.  Download the code into the chip.<\/span><\/span><\/p>\n

            \"Testing
            Figure 36. Downloading the code into the chip.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            21. Go into the debug mode (Figure 37). You can see debug mode in Figure 38, and it is saying that semi hosting is enabled.<\/span><\/span><\/p>\n

            \"Testing
            Figure 37. Enter into the debug mode.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            \"Testing
            Figure 38. Debug mode.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            22.  Go to the breakpoints and remove all (Figure 39).<\/span><\/span><\/p>\n

            \"Testing
            Figure 39. Removing the breakpoints.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            23.  Hit the resume button (Figure 40). Now the code is running, and you have to press the user button.<\/span><\/span><\/p>\n

            \"Testing
            Figure 40. Run the code.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            24.  Start tracing by pressing the user button (Figure 41).<\/span><\/span><\/p>\n

            \"Testing
            Figure 41. Capturing I2C trace.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            You can see the I2C trace of your application in Figure 42.<\/span><\/p>\n

            \"Testing
            Figure 42. I2C trace of the application.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            25. Observe the console in Figure 43. Application is running, Tx is completed, Rx is completed, Tx is completed, but the data is not received.<\/span><\/span><\/p>\n

            \"Testing
            Figure 43. Output on the console.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            Look at the trace in Figure 44, the data is received, and the last 4 characters of data are EBA and \\n. But the data is not printed on the console. The problem is the program has to wait until the receive completes. Without that, you cannot proceed to the next line, or you cannot execute the printf statement in Figure 45.<\/span><\/p>\n

            \"Testing
            Figure 44. I2C trace of the application.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            \"Testing
            Figure 45. Debug mode.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            26. To solve this problem, set the rxComplt flag after Rx completed, as shown in Figure 46.<\/span><\/span><\/p>\n

            \"Testing
            Figure 46. Code to set the rxComplt variable.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            27. Declare the flag variable (Figure 47).<\/span><\/span><\/p>\n

            \"Testing
            Figure 47. Flag variable declaration.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            28. In the application after the while statement, wait until the rxComplt variable is set, as shown in Figure 48. After printing the data, you can make rxComplt = RESET again.<\/span><\/span><\/p>\n

            \"Testing
            Figure 48. Code to wait until rxComplt is set.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            29.Remember that you have one more MasterReceiveData() API. After the completion of receive data here also the ApplicationEventCallback() will be executed for the event I2C Rx complete, and the flag will be set. Therefore, before checking whether rxComplt is set or reset, make sure that you clear the rxComplt flag, which was set for the previous MasterReceiveData event. That means RESET the rxComplt variable, as shown in Figure 49.<\/span><\/span><\/p>\n

            \"Testing
            Figure 49. Code to reset the rxComplt variable.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            30.  Build the project. There is one warning saying while clause does not guard. Basically, this warning is harmless; you can keep it as it is. But if you want to solve this warning, remove the semicolon of while and give the guards, as shown in Figure 50.<\/span><\/span><\/p>\n

            \"Testing
            Figure 50. Resolving the warning.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            31. Build the project. Now the project is error-free.<\/span><\/p>\n

            32.Program the chip (Figure 51).<\/span><\/p>\n

            \"Testing
            Figure 51. Programming the chip.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            33. Go to the debugging mode (Figure 52<\/span>).<\/span><\/span><\/p>\n

            \"Testing
            Figure 52. Entering into the debug mode.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            34.  Now you are in the debugging mode (Figure 53). Reset the Arduino board and remove all the breakpoints.<\/span><\/span><\/p>\n

            \"Testing
            Figure 53. Debug mode.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            35. Hit the run button (Figure 54).<\/span><\/span><\/p>\n

            \"Testing
            Figure 54. Run the application.<\/span><\/figcaption><\/figure>\n

             <\/p>\n

            36. Hit the user button. Now you can observe that the data is received from the slave (Figure 55).<\/span><\/span><\/p>\n

            \"Testing
            Figure 55. Data received from the slave.<\/span><\/figcaption><\/figure>\n

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

              Exercise : Testing I2C interrupt APIs part 1     Now let\u2019s test the interrupt related code and APIs using an application. Consider the same exercise i2c_master_rx_testing (Figure 1) that we coded while testing our MasterSendData and MasterReceiveData APIs.   Steps for testing I2C interrupt APIs: 1. Create a source file: Copy the i2c_master_rx_testing […]<\/p>\n","protected":false},"author":1,"featured_media":4806,"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-4795","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 53- Exercise : Testing I2C interrupt APIs part 1<\/title>\n<meta name=\"description\" content=\"Exercise: Testing I2C interrupt APIs part 1.Now let\u2019s test the interrupt related code and APIs using an application. Consider the same exercise\" \/>\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-53-exercise-testing-i2c-interrupt-apis-part-1\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1\" \/>\n<meta property=\"og:description\" content=\"Exercise: Testing I2C interrupt APIs part 1.Now let\u2019s test the interrupt related code and APIs using an application. Consider the same exercise\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/\" \/>\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=\"2021-01-04T11:19:35+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-11-23T04:22:15+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2021\/01\/Figure-1-2.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1917\" \/>\n\t<meta property=\"og:image:height\" content=\"1023\" \/>\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=\"21 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-53-exercise-testing-i2c-interrupt-apis-part-1\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/\"},\"author\":{\"name\":\"FastBitLab\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#\\\/schema\\\/person\\\/e32b38e733a0d76ffa7e6bc998652e5d\"},\"headline\":\"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1\",\"datePublished\":\"2021-01-04T11:19:35+00:00\",\"dateModified\":\"2022-11-23T04:22:15+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/\"},\"wordCount\":2353,\"commentCount\":3,\"publisher\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/Figure-1-2.png\",\"keywords\":[\"STM32 I2C Lectures\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/\",\"url\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/\",\"name\":\"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/Figure-1-2.png\",\"datePublished\":\"2021-01-04T11:19:35+00:00\",\"dateModified\":\"2022-11-23T04:22:15+00:00\",\"description\":\"Exercise: Testing I2C interrupt APIs part 1.Now let\u2019s test the interrupt related code and APIs using an application. Consider the same exercise\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/#primaryimage\",\"url\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/Figure-1-2.png\",\"contentUrl\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/01\\\/Figure-1-2.png\",\"width\":1917,\"height\":1023,\"caption\":\"Figure 1. Exercise i2c_master_rx_testing.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/fastbitlab.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1\"}]},{\"@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 53- Exercise : Testing I2C interrupt APIs part 1","description":"Exercise: Testing I2C interrupt APIs part 1.Now let\u2019s test the interrupt related code and APIs using an application. Consider the same exercise","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-53-exercise-testing-i2c-interrupt-apis-part-1\/","og_locale":"en_US","og_type":"article","og_title":"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1","og_description":"Exercise: Testing I2C interrupt APIs part 1.Now let\u2019s test the interrupt related code and APIs using an application. Consider the same exercise","og_url":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/","og_site_name":"FastBit EBA","article_publisher":"https:\/\/www.facebook.com\/fastbiteba\/","article_published_time":"2021-01-04T11:19:35+00:00","article_modified_time":"2022-11-23T04:22:15+00:00","og_image":[{"width":1917,"height":1023,"url":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2021\/01\/Figure-1-2.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":"21 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/#article","isPartOf":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/"},"author":{"name":"FastBitLab","@id":"https:\/\/fastbitlab.com\/blog\/#\/schema\/person\/e32b38e733a0d76ffa7e6bc998652e5d"},"headline":"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1","datePublished":"2021-01-04T11:19:35+00:00","dateModified":"2022-11-23T04:22:15+00:00","mainEntityOfPage":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/"},"wordCount":2353,"commentCount":3,"publisher":{"@id":"https:\/\/fastbitlab.com\/blog\/#organization"},"image":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/#primaryimage"},"thumbnailUrl":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2021\/01\/Figure-1-2.png","keywords":["STM32 I2C Lectures"],"articleSection":["Blog"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/","url":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/","name":"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1","isPartOf":{"@id":"https:\/\/fastbitlab.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/#primaryimage"},"image":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/#primaryimage"},"thumbnailUrl":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2021\/01\/Figure-1-2.png","datePublished":"2021-01-04T11:19:35+00:00","dateModified":"2022-11-23T04:22:15+00:00","description":"Exercise: Testing I2C interrupt APIs part 1.Now let\u2019s test the interrupt related code and APIs using an application. Consider the same exercise","breadcrumb":{"@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/#primaryimage","url":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2021\/01\/Figure-1-2.png","contentUrl":"https:\/\/fastbitlab.com\/blog\/wp-content\/uploads\/2021\/01\/Figure-1-2.png","width":1917,"height":1023,"caption":"Figure 1. Exercise i2c_master_rx_testing."},{"@type":"BreadcrumbList","@id":"https:\/\/fastbitlab.com\/blog\/stm32-i2c-lecture-53-exercise-testing-i2c-interrupt-apis-part-1\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/fastbitlab.com\/blog\/"},{"@type":"ListItem","position":2,"name":"STM32 I2C Lecture 53- Exercise : Testing I2C interrupt APIs part 1"}]},{"@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\/4795","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=4795"}],"version-history":[{"count":5,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/posts\/4795\/revisions"}],"predecessor-version":[{"id":12589,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/posts\/4795\/revisions\/12589"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/media\/4806"}],"wp:attachment":[{"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/media?parent=4795"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/categories?post=4795"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fastbitlab.com\/blog\/wp-json\/wp\/v2\/tags?post=4795"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}