| ??? 03/24/12 14:16 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#186856 - Why not solve your problem BEFORE trying to save pins? Responding to: ???'s previous message |
I'd guess you can put off trying to save a pin here and a pin there by simply getting the thing working with the pin assignments you've chosen, BEFORE you make additional changes. That way you'll have a much better notion of what's going on.
After that, you can experiment with timing loops or anything else you need to try, fully able to fall back to a working scheme. RE |
| Topic | Author | Date |
| 4 Bit LCD | 01/01/70 00:00 | |
| I am no sherlock Holmes, but ... | 01/01/70 00:00 | |
| LCD | 01/01/70 00:00 | |
| Did you think about accesses using DATA1? | 01/01/70 00:00 | |
| lcd | 01/01/70 00:00 | |
| So you found a solution ... | 01/01/70 00:00 | |
| LCD 4 BIT | 01/01/70 00:00 | |
| where did you get that idea? | 01/01/70 00:00 | |
| Using Read Cycle to LCD | 01/01/70 00:00 | |
| of course, you can not use a signal that is not there | 01/01/70 00:00 | |
| busy flad check | 01/01/70 00:00 | |
| Why not solve your problem BEFORE trying to save pins? | 01/01/70 00:00 | |
Premature optimisation | 01/01/70 00:00 |