??? 02/13/06 19:52 Read: times |
#109881 - well, I can't Responding to: ???'s previous message |
Peter, if you read my posts, you will see I have, in none, stated "DO NOT bit-bang" I have no argument for that. What I argue against is your point "bit-bang is always better"
Since typically a main loop must be fast from the humans view, no human was able to detect a 100µs delay. If all your applications "interface with humans" sure, but many '51 apps do not. When you "interface with humans", you typically have "all the time in the world". And again, I know no main loop which can not tolerate several 100µs delay. well, I can't 100µs would be 20% of my loop On my experience a HW-I2C was only really needed in very rarely cases or to support I2C slave or multimaster. You keep banging on "needed" I have stated "in many cases you can use bit-bang with no ill effect, but, as I post, not in all. Should that be a reason to shun HW IIC?" I really do not give a hoot if you "need" it I merely state "the overhead is less" Erik |