| ??? 09/29/06 15:39 Read: times |
#125374 - I2c Responding to: ???'s previous message |
I think you have to attack the problem from a few directions.
1. Understand I2c protocol www.nxp.com/acrobat/applicationnotes/AN10216_1.pdf http://www.embedded.com/97/feat9711.htm http://www.nxp.com/acrobat_d...340011.pdf (I2c bus specification) 2. Understand the required I2c commands required by your EEPROM Insert your EEPROM I2c command sequnces here.... from the data sheet. 3. Understand how the P89LPC936 generates and decode's I2c messages. Use internal I2c hardware of the P89LPC395 OR bit bash 2 I/O ports to generate I2c serial sequence Some people find the internal I2c hardware SFRs a little overwellming at first.... and opt for bit bash I2c... There are examples here http://www.8052.com/codelib/I2C%20library and here http://www.8052.com/codelib/IIC.asm in ASM. But still you need to understand what commands your EEPROM requires..... Eg START, I2C address, I2c command, STOP etc There is an I2c code example on the NXP (formerly Philips) web site http://www.standardics.nxp.com/support/b...s/pca9633/ this is written in C.... but the concept is the same as the Code Architect generated files... Joe |
| Topic | Author | Date |
| P89LPC936 and external EEPROM through I2C | 01/01/70 00:00 | |
| If you mean CODE memory, you can't | 01/01/70 00:00 | |
| Sorry, not ment as code memory | 01/01/70 00:00 | |
| WRONG! get rid of the interruptifobia | 01/01/70 00:00 | |
| Interrupfobia | 01/01/70 00:00 | |
| then why | 01/01/70 00:00 | |
| why no interrupts | 01/01/70 00:00 | |
| I2c | 01/01/70 00:00 | |
| Code Architect | 01/01/70 00:00 | |
| code architect | 01/01/70 00:00 | |
if domebody carries you through this one ... | 01/01/70 00:00 |