From: N_Cook on 6 Jun 2010 04:29 Found time to build the 7405 interface today. Googling around the subject beforehand, came across this http://oocities.com/microappnotes/UARTAVR.htm It was mirrored from Geocities in october 2009. text only http://web.archive.org/web/20080624061921/http://www.geocities.com/microappn otes/UARTAVR.htm note www.nutsvolts.com not www.ntsvolts.com other ref maybe (not read yet) Programming The 54� Micro by G. Y. Xu Microcontroller/PIC 2006-02 (Program files and code listing) http://www.nutsvolts.com/media-files/25/THE%2054%C2%A2%20MICRO.zip
From: Franc Zabkar on 6 Jun 2010 20:33 On Sun, 6 Jun 2010 09:29:37 +0100, "N_Cook" <diverse(a)tcp.co.uk> put finger to keyboard and composed: >Found time to build the 7405 interface today. >Googling around the subject beforehand, came across this >http://oocities.com/microappnotes/UARTAVR.htm That article talks about bit-banging an RS232 software UART for a UART-less uC. The I2C bus and protocol is completely different. It doesn't frame its bytes with start and stop bits. AIUI, each byte is acknowledged by the recipient with an ACK bit. Furthermore, traffic is bidirectional, along a single wire, ie no separate Tx/Rx wires. Commands and data are both sent down the same wire. ISTM, that you are monitoring all I2C traffic, not just the EEPROM data. You may like to read a datasheet for a common I2C serial EEPROM chip. 24AA00/24LC00/24C00: http://ww1.microchip.com/downloads/en/DeviceDoc/21178E.pdf - Franc Zabkar -- Please remove one 'i' from my address when replying by email.
From: N_Cook on 7 Jun 2010 05:28 Franc Zabkar <fzabkar(a)iinternode.on.net> wrote in message news:b1fo06hf7g95h3htb0sh9pi3hdnkem9gmn(a)4ax.com... > On Sun, 6 Jun 2010 09:29:37 +0100, "N_Cook" <diverse(a)tcp.co.uk> put > finger to keyboard and composed: > > >Found time to build the 7405 interface today. > >Googling around the subject beforehand, came across this > >http://oocities.com/microappnotes/UARTAVR.htm > > That article talks about bit-banging an RS232 software UART for a > UART-less uC. > > The I2C bus and protocol is completely different. It doesn't frame its > bytes with start and stop bits. AIUI, each byte is acknowledged by the > recipient with an ACK bit. Furthermore, traffic is bidirectional, > along a single wire, ie no separate Tx/Rx wires. Commands and data are > both sent down the same wire. > > ISTM, that you are monitoring all I2C traffic, not just the EEPROM > data. You may like to read a datasheet for a common I2C serial EEPROM > chip. > > 24AA00/24LC00/24C00: > http://ww1.microchip.com/downloads/en/DeviceDoc/21178E.pdf > > - Franc Zabkar > -- > Please remove one 'i' from my address when replying by email. Don't know whether using 74LS05 rather than L or salvaged X24C04P or my breadboarding , but not getting very far. Selected LPT1 in iicuni.exe Philips profile just gave error SDA low with any button presses/settings or even disconnected In MIR profile and trying various settings of BaseAdr+0 /2 of 00,FF,CF,DF SDA normally L would go H momentarily pulsed on pressing I2Clist on all of those BaseAdr settings SCL would go H or L but not osc on various of those settings and button pushes My translation of I2Clist function 'I2C List'-Button: To determine which devices exist on the I2C bus are. Sends all the even device addresses from (0,2,4 ... FE) maybe problem something to do with win 98SE or this "http://www.boerde.de/~matthias/delphi/ IIC Bus - Universal V 1.2 a program (Executables - Source) to control I�C-Bus devices at the parallel port, for any passive I�C-Bus Interface (e.g. Philips, Eagle-files and pdf), with E�PROM editor. Price winning tool (3th national price in Elektor's International Electronic Software Competition 1996). If you want to use the sources you need the component DStamp too. Attention: Use "Default Settings for output":BaseAdr+2 = DF with newer MoBo's. For Win2k or XP you need userport.sys (cached here)."
First
|
Prev
|
Pages: 1 2 3 Prev: AC current sensor with interface Next: ? on NTE56041 for touch-on lamp |