TWI HW producing shortened ACK clock pulse

[Benjamin]

Hi everyone,

we are trying to use the TWI interface of the nRF52832 to communicate with a TI BQ28Z610 fuel gauge, using the TWI driver of the nRF5_SDK_13.0. For the last few days we had seen always the same behaviour: when we were trying to transmit more than 1 byte of data, the device address as well as the first byte were transmitted correctly, the second byte however produced a NACK.

We've been able to narrow down the problem to the ACK clock pulse after the first byte. As you can see from the attached scope screenshots, the relevant clock pulse has circa 1/4 of the length of a normal clock pulse. While I'm assuming that this behaviour brings a technical advantage in most cases (since the shorter clock pulse frees the interface earlier for subsequent communication) it leads to problems with the BQ28Z610.

My workaround at this point is to use the deprecated bit banging methods from twi_sw_master.c. I've insterted a 5ms delay after the function checks for the ack bit to delay the SCL line going low again.

Now the question is, since we're not fully happy with not being able to use the TWI hardware driver, is there any way to lengthen the relavant clock pulse using the TWI hardware? Has anybody else experienced problems with that behaviour?

tek00000.png tek00001.png tek00002.png

[RK]

I think you're seeing the same thing devzone.nordicsemi.com/.../ post talks about.

It's not .. really a shortened clock pulse and it's got nothing to do with freeing the interface earlier. I believe what you're seeing is the TWI attempting to output a normal clock pulse, however the slave, your TI device, is holding the clock low and stretching it. So really all that time it's low, the TWI interface has it high, but the TI chip is pulling it down. So actually it's a very LONG clock pulse.

As soon as the slave releases the clock and stops stretching, the clock jumps high, the TWI interface sees that it's been released and is now high (where it's been holding it for some time) and then is able to do what it wanted to do a while back and drive the clock line back low to finish that stretched clock pulse.

There is a minimum time the TWI hardware is required to hold the clock high after the slave stops stretching it, I had read 4us at 100kB/s but I don't have a spec handy. Can't instantly tell from those traces whether the TWI is compliant and holding the end of the clock after the slave releases it for long enough. Once that ACK is done, the TWI interface is free to start another cycle.

So not sure here which is the non-standards compliant bit.

[RK]

The Nordic guys are really helpful, if you just open a My Page case and reference the thread, if nothing else to get them to check what the I2C delay after clock stretch is and discuss whether that's within the I2C spec (to the extent there is an I2C spec). Then if it's out of spec it can go in as an errata, if it's within, or just not clear there is a value, possibly just document it.