欢迎访问ic37.com |
会员登录 免费注册
发布采购

SI1002-C-GM 参数 Datasheet PDF下载

SI1002-C-GM图片预览
型号: SI1002-C-GM
PDF下载: 下载PDF文件 查看货源
内容描述: 超低功耗, 64/32 KB , 10位ADC, MCU ,集成了240-960兆赫的EZRadioPRO收发器 [Ultra Low Power, 64/32 kB, 10-Bit ADC MCU with Integrated 240-960 MHz EZRadioPRO Transceiver]
分类和应用:
文件页数/大小: 376 页 / 2369 K
品牌: SILICON [ SILICON ]
 浏览型号SI1002-C-GM的Datasheet PDF文件第290页浏览型号SI1002-C-GM的Datasheet PDF文件第291页浏览型号SI1002-C-GM的Datasheet PDF文件第292页浏览型号SI1002-C-GM的Datasheet PDF文件第293页浏览型号SI1002-C-GM的Datasheet PDF文件第295页浏览型号SI1002-C-GM的Datasheet PDF文件第296页浏览型号SI1002-C-GM的Datasheet PDF文件第297页浏览型号SI1002-C-GM的Datasheet PDF文件第298页  
Si1000/1/2/3/4/5  
24.4.2. SMB0CN Control Register  
SMB0CN is used to control the interface and to provide status information (see SFR Definition 24.2). The  
higher four bits of SMB0CN (MASTER, TXMODE, STA, and STO) form a status vector that can be used to  
jump to service routines. MASTER indicates whether a device is the master or slave during the current  
transfer. TXMODE indicates whether the device is transmitting or receiving data for the current byte.  
STA and STO indicate that a START and/or STOP has been detected or generated since the last SMBus  
interrupt. STA and STO are also used to generate START and STOP conditions when operating as a mas-  
ter. Writing a 1 to STA will cause the SMBus interface to enter Master Mode and generate a START when  
the bus becomes free (STA is not cleared by hardware after the START is generated). Writing a 1 to STO  
while in Master Mode will cause the interface to generate a STOP and end the current transfer after the  
next ACK cycle. If STO and STA are both set (while in Master Mode), a STOP followed by a START will be  
generated.  
The ARBLOST bit indicates that the interface has lost an arbitration. This may occur anytime the interface  
is transmitting (master or slave). A lost arbitration while operating as a slave indicates a bus error condi-  
tion. ARBLOST is cleared by hardware each time SI is cleared.  
The SI bit (SMBus Interrupt Flag) is set at the beginning and end of each transfer, after each byte frame, or  
when an arbitration is lost; see Table 24.3 for more details.  
Important Note About the SI Bit: The SMBus interface is stalled while SI is set; thus SCL is held low, and  
the bus is stalled until software clears SI.  
24.4.2.1. Software ACK Generation  
When the EHACK bit in register SMB0ADM is cleared to 0, the firmware on the device must detect incom-  
ing slave addresses and ACK or NACK the slave address and incoming data bytes. As a receiver, writing  
the ACK bit defines the outgoing ACK value; as a transmitter, reading the ACK bit indicates the value  
received during the last ACK cycle. ACKRQ is set each time a byte is received, indicating that an outgoing  
ACK value is needed. When ACKRQ is set, software should write the desired outgoing value to the ACK  
bit before clearing SI. A NACK will be generated if software does not write the ACK bit before clearing SI.  
SDA will reflect the defined ACK value immediately following a write to the ACK bit; however SCL will  
remain low until SI is cleared. If a received slave address is not acknowledged, further slave events will be  
ignored until the next START is detected.  
24.4.2.2. Hardware ACK Generation  
When the EHACK bit in register SMB0ADM is set to 1, automatic slave address recognition and ACK gen-  
eration is enabled. More detail about automatic slave address recognition can be found in Section 24.4.3.  
As a receiver, the value currently specified by the ACK bit will be automatically sent on the bus during the  
ACK cycle of an incoming data byte. As a transmitter, reading the ACK bit indicates the value received on  
the last ACK cycle. The ACKRQ bit is not used when hardware ACK generation is enabled. If a received  
slave address is NACKed by hardware, further slave events will be ignored until the next START is  
detected, and no interrupt will be generated.  
Table 24.3 lists all sources for hardware changes to the SMB0CN bits. Refer to Table 24.5 for SMBus sta-  
tus decoding using the SMB0CN register.  
Refer to “Limitations for Hardware Acknowledge Feature” on page 299 when using hardware ACK genera-  
tion.  
294  
Rev. 1.0