Erik Slagter

The problem could be that after the first sequence the tiny needs to do some processing and isn't ready in time to respond to the second sequence with fresh data?...

There is a principal problem with USI (for both SPI and I2C). As a master it's okay, but as a slave there are very tight timing demands, because the slave...

> I'm in the process of writing a wrapper for your updated library for > Arduino and with the ATtiny Tiny Cores. Cool! > this Initializes the TWI. That seems...

> I still really don't understand the *idle_callback usage. When would I > use it? How is it used? Any simple example? I am using to reset the watchdog and...

> regarding hardware setup: Using external pull-ups and that are correctly > sized and I'm running at 8mhz internal, but calibrated. Okay. The clock doesn't need to be calibrated though,...

Just a wild guess. I've never used this on an attint2313, but the 2313 is, afaik, of an older generation than the '85 and '861 I've been using. Maybe the...

I find some unexplainable problems come from marginal power supply, you might want to check that. The voltage regulator should have enough (somewhat more voltage in than required) headroom (and...

> If such functionality doesn't exist, I'd be happy to try and implement > it and submit a patch :) Nice. Please note that twi does feature a start condition...

Yes confirmed. You need to run > 8 Mhz to make I2C reliable. It can be done quite easily with the PLL clock (which the larger models don't have...), without...

Funny you mention that. Definitely more people have mentioned this fact. The USI isn't helping very much indeed, I also found out. If you're going to do a full-blown I2C...