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

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
Richard Erlacher
03/24/12 08:16
Read: 481 times
Denver, Co
USA


 
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


List of 13 messages in thread
TopicAuthorDate
4 Bit LCD      Sean O Mara      03/22/12 12:10      
   I am no sherlock Holmes, but ...      Erik Malund      03/22/12 13:31      
      LCD      Sean O Mara      03/22/12 13:56      
         Did you think about accesses using DATA1?      Per Westermark      03/22/12 15:41      
            lcd      Sean O Mara      03/22/12 17:18      
               So you found a solution ...      Andy Neil      03/22/12 18:02      
                  LCD 4 BIT      Sean O Mara      03/23/12 06:49      
                     where did you get that idea?      Erik Malund      03/23/12 06:57      
                        Using Read Cycle to LCD      Michael Karas      03/23/12 10:33      
                           of course, you can not use a signal that is not there      Erik Malund      03/23/12 10:45      
                        busy flad check      Sean O Mara      03/23/12 16:02      
                           Why not solve your problem BEFORE trying to save pins?        Richard Erlacher      03/24/12 08:16      
                              Premature optimisation      Andy Neil      03/24/12 09:48      

Back to Subject List