I'm using an HD44780 clone LCD module a KS0066U. Everything works ok on the module except when I rapidly power cycle the device (on->off->on). For some reason a very short interruption in the power causes the display module to improperly initialize as a 1-line LCD instead of a 2-line LCD display. What would cause this behavior? Is there any way to prevent it in software?
EDIT: I'm using the display controller in 4-bit mode not 8-bit mode.
I changed my initialization code so that it sent the upper 4-bit nibble of the function set command twice. Following which I resent the upper 4-bit nibble followed by the lower 4-bit nibble. This does not match the datasheet which seems to indicate that you can send the upper 4-bit nibble then send the function set command upper 4-bit followed by lower 4-bit.
// Works sometimes pseudo-code
port=0x20;
e=1; e=0;
port=0x20;
e=1; e=0;
port=0xC0;
e=1; e=0;
// Works all the time pseudo-code
port=0x20;
e=1; e=0;
e=1; e=0;
port=0x20;
e=1; e=0;
port=0xC0;
e=1; e=0;
My guess would be that you are missing a necessary delay in your initialization sequence. If the display is busy when you try to send a command, that command will be ignored. If when you start your procedure, the display is in four bit mode and has just had "0000" clocked in as the first half of a command, then when you clock in "0011" the display will see the whole command as "00000011", which will cause the display to be busy for up to 1.6ms.
Incidentally, it is good if possible to wire the low-order data wires from the display in such a way that when a "0011" command is sent to the display, the whole 8 bits seen by the display will form a mode-set command which is correct for the type of display you are using. That will help avoid any display glitches when resetting a display which is already in use (periodically resetting the display is a good idea, if it can be done glitchlessly, since it will ensure that if the display somehow gets into a bad mode it will fix itself).
I found a workaround for the problem:
I added a 1000milisecond delay at startup, before initializing/configuring the LCD controller. It worked pretty good for me.
A lower delay(100, 200ms) not worked so well. Just a note: It happened only in 4bits databuss.
Good luck!
Inserting a delay in your code so when it switches on it gives the LCD long enough to initialize when it starts up. A maximum of a few hundred milliseconds.
You could also try connecting the LCD power to the microcontroller and powering off the LCD for a second after start up.
Not sure if this helps AT ALL, but I messed with the KS0066U on an Arduino project. Here is the link.
