Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
03/23/12 16:33
Read: times


 
#186834 - Using Read Cycle to LCD
Responding to: ???'s previous message
Erik Malund said:
The wait LCD label is redundant,better off using a delay routine
where did you get that idea?
checking the LCD ready bit is, by far, the most reliable and fastest method.
that some posting amateurs have not figured that out is no reason for you to follow the herd.

Erik


There are a good number of cases where delays of some sort are necessary when dealing with LCD controllers. I have been tasked to work with a number of display modules where the interface cable from the MCU board over to the LCD was a narrow flex cable. The LCD manufacturers in these cases had elected to tie the RW line to the controller to a permanent "write" level on the module so as to save a conductor in the connection cable. Of course these applications also used the 4-bit mode to the display for exactly the same reason. As a result of this the software driver I supplied had to do its own delays because reading busy status from the controller was not possible.

Michael Karas



List of 13 messages in thread
TopicAuthorDate
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      

Back to Subject List