??? 12/04/10 17:17 Read: times |
#179871 - Andy, Michael Responding to: ???'s previous message |
I said: (at least with trivial code)
A non-trivial case (using an OS on a '51/startup only/...) is automaically excluded by the above. Pre (was it) '05 when HW IIC became widely available I did, who knows how many, bit banged IIC apps and ran into all kinds of non-trivial means of handling the (potential) 'dead band'. E.G. a bit banged IIC master (specifically driving an EEPROM) can be made non-trivial by using a timer .... The whole point of my post was that where Jan's post more ot less stated "no problem" there will often be problems if you approach bit-banged IIC as a trivilaility. also, with sub-$1 HW IIC available, why even bother with bit-banging. Erik |
Topic | Author | Date |
I2C EEPROMs, best data sheets? | 01/01/70 00:00 | |
as we are on 8052.com... | 01/01/70 00:00 | |
my first | 01/01/70 00:00 | |
what uC | 01/01/70 00:00 | |
bit-banging I2C master for EEPROMs is trivial | 01/01/70 00:00 | |
yes, the code is trivial, but ... | 01/01/70 00:00 | |
Probably majority units don't suffer from the busy-loops | 01/01/70 00:00 | |
Smart Door Knobs | 01/01/70 00:00 | |
Andy, Michael | 01/01/70 00:00 | |
ADuC7026 | 01/01/70 00:00 | |
WP pin ? | 01/01/70 00:00 | |
It works sometimes | 01/01/70 00:00 | |
Timing - erase? | 01/01/70 00:00 | |
can you givenot enough time? | 01/01/70 00:00 | |
No erase, no abort | 01/01/70 00:00 | |
Hidden erase | 01/01/70 00:00 | |
STOP too short | 01/01/70 00:00 | |
Problem solved (I think) | 01/01/70 00:00 | |
I2C | 01/01/70 00:00 |