| ??? 06/20/09 11:19 Read: times |
#166282 - Start describing your hw and what you have tested Responding to: ???'s previous message |
Your subject line isn't descriptive - it doesn't even mention LCD.
You haven't mentioned what LCD. You haven't posted your code as code - that may indicate how careful you have read the datasheet for your display. You are using a software delay that doesn't synchronize with any real hardware. How do you know how long delays it generates? You do not mention any tests you have done to figure out what goes wrong. What signal values have you seen on the processor pins? Are all signals correctly connected? Why should we find out what is wrong. Isn't that your job? Isn't the goal with asking on a forum to tell what you have done, and get tips about things you have forgotten to look at? Your only comments are there to explain your magic constants. Why not use the functionality of the language and name each of the commands, so the code looks like: cmd(CMD_CLEAR_SCREEN);instead of cmd ( 0x01 ); // Clear Display Screen |
| Topic | Author | Date |
| Plz help me any one.. | 01/01/70 00:00 | |
| Start describing your hw and what you have tested | 01/01/70 00:00 | |
| Thank you.. | 01/01/70 00:00 | |
| Re-Initialize Inside Loop | 01/01/70 00:00 | |
| LCD problem | 01/01/70 00:00 | |
| How to debug | 01/01/70 00:00 | |
| LCD problem | 01/01/70 00:00 | |
| A few tips | 01/01/70 00:00 | |
| Thank you.. | 01/01/70 00:00 | |
| At least one error | 01/01/70 00:00 | |
| Thank you.. | 01/01/70 00:00 | |
| At least one error | 01/01/70 00:00 | |
| Amazing... | 01/01/70 00:00 | |
| Unfortunately not Amazing | 01/01/70 00:00 | |
| Thank you | 01/01/70 00:00 | |
| DISPLAYING MESG IN LCD, INTERFACE 2 89s52 | 01/01/70 00:00 | |
No replies | 01/01/70 00:00 |