maybe it will help: 1. usualy, the device address in most I2C implementations is shifted left as the lower bit is direction bit, so, if your device address, for example, 0x03, in most implementations, you program it as 0x06. in msp430's implementation you have to write into address register 0x03. 2. try to debug it without interrupts, just in polling mode, if it works, try read manual carefully, the interrupt functions assigned weird in msp430.
2007/9/6, Robert Spanton <[email protected]>: > > On 05/09/07, Randall Restle <[email protected]> wrote: > > Is your IIC master a MSP430? > > No, it's not. It's a Linksys NSLU2. I've verified that its I2C works > properly on some other devices. > > I think I may have got to the bottom of my problems - but right now > I'm not near the hardware to test them. I was slightly confused about > which interrupt did what, and discovered through some experimentation > - after re-reading the docs I think I've worked it out. > > I was quite surprised that I couldn't find anything on google code > search that used the USCI in slave mode! Still, any working code from > anyone would be much appreciated. > > Once we get it working here, I'll make the code available to others. > > Rob > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > -- _____________ Oleg V. Kobrin
