>Well this case is a bit special, I think I need to know
>both the start and stop conditions (particulary stop) as
>I need to do some data processing after the message is recived.
>The final program will emulate an Philiphs LCD driver chip
>but add an hoist of additional features (MMC-card gateway, Realtime
>clock, LED display support (7segment)).
>I haven't seen an clearcut way to signalise that the data from
>the master is complete without hooking onto the stop condition.
>Or are there other ways ?

I had the same problem in my implementation, and ended up starting a timer
to check the stop state bit after receiving a nak from the master. I started
off trying to use the interrupts, and although the data sheet seemed to
imply that the start and stop states should cause them, it turns out the
fine print says they don't in slave mode, so that seemed the only way to do
what I needed to detect the I2C idle state.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads