Occasionally, we are tasked with designing circuitry for aspecific purpose. The request may have customer originsor it may be an in-house requirement. Alternately, a circuitmay be developed because its possibility is simply tooattractive to ignore1. Over time, these circuits accumulate,encompassing a wide and useful body of proven capabilities.They also represent substantial effort. These considerationsmake publication an almost obligatory propositionand, as such, a group of circuits is presented here. This isnot the first time we have displayed such wares and, giventhe encouraging reader response, it will not be the last2.Eighteen circuits are included in this latest effort, roughlyarranged in the categories given in this publication’s title.They appear at the next paragraph.
標(biāo)簽：
信號(hào)源
調(diào)節(jié)器
電源
電路分析
上傳時(shí)間：
2013-11-12
上傳用戶(hù)：012345
The 87LPC76X Microcontroller combines in a small package thebenefits of a high-performance microcontroller with on-boardhardware supporting the Inter-Integrated Circuit (I2C) bus interface.The 87LPC76X can be programmed both as an I2C bus master, aslave, or both. An overview of the I2C bus and description of the bussupport hardware in the 87LPC76X microcontrollers appears inapplication note AN464, Using the 87LPC76X Microcontroller as anI2C Bus Master. That application note includes a programmingexample, demonstrating a bus-master code. Here we show anexample of programming the microcontroller as an I2C slave.The code listing demonstrates communications routines for the87LPC76X as a slave on the I2C bus. It compliments the program inAN464 which demonstrates the 87LPC76X as an I2C bus master.One may demonstrate two 87LPC76X devices communicating witheach other on the I2C bus, using the AN464 code in one, and theprogram presented here in the other. The examples presented hereand in AN464 allow the 87LPC76X to be either a master or a slave,but not both. Switching between master and slave roles in amultimaster environment is described in application note AN435.The software for a slave on the bus is relatively simple, as theprocessor plays a relatively passive role. It does not initiate bustransfers on its own, but responds to a master initiating thecommunications. This is true whether the slave receives or transmitsdata—transmission takes place only as a response to a busmaster’s request. The slave does not have to worry about arbitrationor about devices which do not acknowledge their address. As theslave is not supposed to take control of the bus, we do not demandit to resolve bus exceptions or “hangups”. If the bus becomesinactive the processor simply withdraws, not interfering with themaster (or masters) on the bus which should (hopefully) try toresolve the situation.
標(biāo)簽：
routines
slave
I2C
87L
上傳時(shí)間：
2013-11-19
上傳用戶(hù)：shirleyYim
