Is there a way to slow down the I2C datarate on a Teensy 3.0?

[dlchambers]

I have a flaky I2C connection and I'm suspecting that it might be affected by the datarate.

I'm running it as a Teesnyduino.

Is there any way to slow down the I2C speed to a rate of my choosing, say 1kHz?

And, while we're on the subject, what is the Teensy 3.0's I2C datarate when running in 96MHz overclock using the std Arduino Wire library?

many thanks,
-Dave

[Headroom]

"suspecting" is not a very good method of determining what the actual poblem is, particularly if you're sitting on this side of the keyoard. Not enough info ;-)

Do you have proper pull-up resistors installed ?
How long is your connection and what cable are you using ?

The "standard" I2C bus frequency is 100KHz with the wire library. You can usually lower that, but I strongly suggest you figure out what the electrical problem is. How did you determine that you have a "flaky" I2C connection ? What are the syptoms ?

Perhaps also post what components you are trying to connect (schematics, link to data sheet etc.)

[PaulStoffregen]

I have a flaky I2C connection and I'm suspecting that it might be affected by the datarate.

Yes, but you'll need to edit the Wire library code.

Look for this code in Wire.cpp:

#if F_BUS == 48000000
        I2C0_F = 0x27;  // 100 kHz
        // I2C0_F = 0x1A; // 400 kHz
        // I2C0_F = 0x0D; // 1 MHz
        I2C0_FLT = 4;
#elif F_BUS == 24000000
        I2C0_F = 0x1F; // 100 kHz
        // I2C0_F = 0x45; // 400 kHz
        // I2C0_F = 0x02; // 1 MHz
        I2C0_FLT = 2;
#else
#error "F_BUS must be 48 MHz or 24 MHz"
#endif

Those magic numbers from from table 44.4.1.10 on page 1027-1028 in the reference manual. 0x3F is the slowest, which should result in a 12.5 kHz clock on SCL.

You can also use 0x7F or 0xBF, which turns on the multiplier, that should give you 6.25 or 3.125 kHz. However, I do not recommend using the multiplier. It seems to cause trouble with some of the I2C features.

You can also run Teensy3 at 24 MHz to cut the bus clock speed in half.

And, while we're on the subject, what is the Teensy 3.0's I2C datarate when running in 96MHz overclock using the std Arduino Wire library?

It's 100 kHz.

Internally, Teensy3 has several clocks. The "bus" clock is 48 MHz when the CPU is either 48 or 96. The I2C runs from the bus clock.

[dlchambers]

Do I also need to tweak the inline TWBRemulation functions in Wire.h?
They're for __MK20DX128__, which IIRC is the Teensy 3.0

[PaulStoffregen]

Do I also need to tweak the inline TWBRemulation functions in Wire.h?

Only if your code writes to TWBR.

[DaQue]

Yes, but you'll need to edit the Wire library code.

Look for this code in Wire.cpp:

#if F_BUS == 48000000
        I2C0_F = 0x27;  // 100 kHz
        // I2C0_F = 0x1A; // 400 kHz
        // I2C0_F = 0x0D; // 1 MHz
        I2C0_FLT = 4;
#elif F_BUS == 24000000
        I2C0_F = 0x1F; // 100 kHz
        // I2C0_F = 0x45; // 400 kHz
        // I2C0_F = 0x02; // 1 MHz
        I2C0_FLT = 2;
#else
#error "F_BUS must be 48 MHz or 24 MHz"
#endif

Those magic numbers from from table 44.4.1.10 on page 1027-1028 in the reference manual. 0x3F is the slowest, which should result in a 12.5 kHz clock on SCL.

You can also use 0x7F or 0xBF, which turns on the multiplier, that should give you 6.25 or 3.125 kHz. However, I do not recommend using the multiplier. It seems to cause trouble with some of the I2C features.

You can also run Teensy3 at 24 MHz to cut the bus clock speed in half.




It's 100 kHz.

Internally, Teensy3 has several clocks. The "bus" clock is 48 MHz when the CPU is either 48 or 96. The I2C runs from the bus clock.

Paul can you verify this has changed to be lines in WireKinetis.cpp now?

[PaulStoffregen]

Yes, the Wire lib changed.