> may I say that usage of the I2C is not a good idea when you have
> lack of code space. This interface has much more complex protocol
> than, for example, SPI or UART.
> For example, even Master transmit mode has about 10 possible
> states which must be processed correctly. So think twice before
> come into troubles with "not enough memory" etc.

This might be correct if you would implement the *complete*
protocol. For accessing simple peripherals, the interface is not
that complex, and I know how to bit-bang this with very small
code. However, using the I2C hardware in the LPC932 should
result in yet smaller code, so I would like to use it instead of
bit-banging.

I just need more detailed information about the correct sequence
of events and actions when using the built-in I2C controller.

BTW, the decision for I2C is based on many more details and won't
be changed. There are no alternatives to this interface here.