i2c vs rs232

[evsource]

Hi,

Is there a way to send data using i2c that takes less time away from the processor than using rs232 and #int_tbe? I mean, it seems to send data with i2c, for every byte of data you want to send, you have to use i2c_write. Even though the data is being transmitted quickly this way, what can be quicker than simply writing a byte to the uart?

Hopefully the question makes sense, and is valid. Basically, if choosing i2c, for a tightly run program, will i2c take longer in overhead to send out the data than taking advantage of the buffer of the rs232 uart?

[Ttelmah]

Quicker, no, depending on the clock rate actually being used.
As quick, yes.

It is a 'fault' of the CCS internal functions, that in several cases, they do unnecessary work. This applies particularly to I2C_WRITE, putc, and the SPI functions, when used inside interrupts.
You can simply declare the I2C buffer address, and in the interrupt, when servicing a write, just write the byte to the I2C buffer, without using the CCS functions, and exit the function ASAP. Obviously the potential transfer rate of I2C (and even more so, with SPI), should send the byte faster than would normally be done with RS232, which would then potentially give an improvement in overall performance.

I'm using I2C, over 30m runs, at 12v, with the P82B96L buffers, at 400KHz, using a custom 'INT_GLOBAL' (a search here will find why this is important), and direct writing to the buffer, to send 50 byte packets, in 1.2mSec.

Best Wishes