??? 06/05/11 08:59 Read: times |
#182483 - 100k is the upper limit Responding to: ???'s previous message |
So, any lower speed is good enough for simple apps.
Timing using simple delay loop is acceptable for testing. From your post I guess you are a newbie, hence the lecture below: There are some pitfalls in such delay loops: If your app is complex, then you are wasting CPU clock cycles in idling. If your code is in C and you switch on the code optimizations, the delay value will decrease, that is the freq will go up and if that exceeds 100k, then you will get erratic behaviour in EEPROM comms. So, don't be tempted to enable the code optimizer of your C compiler. And most important, don't forget to see some excellent sample code on this website, link on the left "Code Library". |
Topic | Author | Date |
Help me ? 89C52 interfacing with EEPROM 24C02 | 01/01/70 00:00 | |
Do *not* use 'for' loops for delays! | 01/01/70 00:00 | |
100k is the upper limit | 01/01/70 00:00 | |
HLL delay loops - just don't do it! | 01/01/70 00:00 | |
that may be difficult | 01/01/70 00:00 | |
but there is a way | 01/01/70 00:00 | |
See if this code is of any help! | 01/01/70 00:00 | |
I doubt it very much | 01/01/70 00:00 | |
No, it isn't | 01/01/70 00:00 | |
doubts 1,2,3 | 01/01/70 00:00 | |
code for 24c02 wih 89c52 | 01/01/70 00:00 | |
Do *not* use 'for' loops for delays! | 01/01/70 00:00 | |
code? | 01/01/70 00:00 |