Summary of I2C bus learning experience (Part 2) - Related doubts

Publisher:EternalSunsetLatest update time:2015-10-22 Source: eefocus Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere
1: Last time, we said that the rising edge of SCL writes to the bus and the falling edge of SCL reads the data on the bus. Who reads and who writes? Or do they both read and write and cooperate with each other?  Because my understanding is that the CPU has the control function, and the IC has the I2C feature. The rising edge writes to the bus and the falling edge reads data for the slave IC.

 

2: If my understanding is correct, then when the CPU sends data to the slave device, there must be a rising edge and a falling edge. The falling edge is easy to understand, the slave device reads SDA, and what about the rising edge, does the slave device also send data to SDA?

  Similarly, when the CPU receives data from the slave device, there must be a rising edge and a falling edge. The rising and falling edges are easy to understand. The slave device sends SDA to the bus. What about the falling edge? Does the slave device read SDA data?

 

3: Answer questions

  "I2C stipulates that each time a byte of data is transmitted, there must be an acknowledgement signal. The acknowledgement signal is generated by the receiving device. The acknowledgement signal is expressed as the receiving device pulling SDA low during the period when SCL is at a high level, indicating that the data transmission is correct and generating an acknowledgement. When the host is the receiving device, the host does not acknowledge the last byte to indicate to the sending device that the data transmission is completed. However, the actual program does not seem to be like this.

Reference address:Summary of I2C bus learning experience (Part 2) - Related doubts

Previous article:Summary of Common Problems in KEIL C Language
Next article:Summary of I2C bus learning experience (I)

Latest Microcontroller Articles
  • Download from the Internet--ARM Getting Started Notes
    A brief introduction: From today on, the ARM notebook of the rookie is open, and it can be regarded as a place to store these notes. Why publish it? Maybe you are interested in it. In fact, the reason for these notes is ...
  • Learn ARM development(22)
    Turning off and on interrupts Interrupts are an efficient dialogue mechanism, but sometimes you don't want to interrupt the program while it is running. For example, when you are printing something, the program suddenly interrupts and another ...
  • Learn ARM development(21)
    First, declare the task pointer, because it will be used later. Task pointer volatile TASK_TCB* volatile g_pCurrentTask = NULL;volatile TASK_TCB* vol ...
  • Learn ARM development(20)
    With the previous Tick interrupt, the basic task switching conditions are ready. However, this "easterly" is also difficult to understand. Only through continuous practice can we understand it. ...
  • Learn ARM development(19)
    After many days of hard work, I finally got the interrupt working. But in order to allow RTOS to use timer interrupts, what kind of interrupts can be implemented in S3C44B0? There are two methods in S3C44B0. ...
  • Learn ARM development(14)
  • Learn ARM development(15)
  • Learn ARM development(16)
  • Learn ARM development(17)
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号