MCT8316A: I2C 100us between bytes requirement

Goran Ekstrom

Part Number: MCT8316A

Hi,

the 100us between bytes requirement on the I2C port is kind of a pain since it complicates the driver software substantially. I was wondering, will clocking the I2C bus at "half speed", 50kHz instead of 100kHz, also work?

Regards,

Goran Ekstrom

Apodosis AB

over 2 years ago

0 Vishnu Balaraj over 2 years ago

TI__Mastermind 24415 points

Hi Goran,

Clocking the I2C bus at 10 kHz will add the 100 us delay so I would recommend to operate your I2C bus at 10 kHz.

Regards,

Vishnu

0 Goran Ekstrom over 2 years ago in reply to Vishnu Balaraj

Prodigy 65 points

Thanks for the answer,

I've been thinking, with an I2C bus clock at 100kHz, that results in approx. 11kByte/seconds, i.e. SCL / 9, i.e. 1/11000 = approx. 91us / byte. If you require 100us "silence" per byte, that is 191us per byte, equal to 5238kBytes/second. 5238 * 9 equals to 47143kHz.

Wouldn't a 45kHz I2C SCL work?

Regards

Goran

0 Vishnu Balaraj over 2 years ago in reply to Goran Ekstrom

TI__Mastermind 24415 points

Goran,

A simple way of looking at it is, at 10 kHz, the data line will toggle every 100 us which will take care of the 100 us inter-byte delay.

Regards,

Vishnu

Motor drivers

Motor drivers forum

MCT8316A: I2C 100us between bytes requirement