Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Message

Re: [AVR-Chat] OT: HD44780 LCD lock-up - busy flag stays set

2007-08-22 by Mark Nowell

According to the display datasheet it's apparently a "KS0066U or 
Equivalent", and according to Google, the KS0066U is compatible with the 
HD44780 apart from some timing differences in the initialisation 
sequence, where it seems I'm well within spec for both devices. Having 
said which, the 4-bit init sequence in the KS0066U datasheet doesn't 
appear identical to the HD44780 init that I'm using. If nothing else 
turns up I may try tweaking the init to see if that makes any 
difference, though if the init was wrong I'd have thought it would fail 
there, rather than working normally for a while.

Mark



Zack Widup wrote:
> Hi Mark,
>
> If your program has been working with other HD44780 display drivers, I'd 
> assume some problem with the displays. I haven't seen that they changed 
> anything within that chip.
>
> Or does HD44780 compatible mean it actually uses an HD44780? Or something 
> else?
>
> Zack
>
> On Wed, 22 Aug 2007, Mark Nowell wrote:
>
>   
>> We've recently switched to yet another cheaper, brighter, 16x2, HD44780
>> compatible LCD (Ampire AC162DY1LY). A small number of these latest
>> displays lock-up after correctly initialising and executing a (variable)
>> number of display commands. By "lock-up" I mean that the busy-flag stays
>> set for at least 150ms, after which time the watchdog resets the micro,
>> which then attempts to re-initialise the display, and fails, presumably
>> because it's still busy. Display shows the last written text overwritten
>> by blocks on the top line, bottom line blank. The display controller
>> appears to still be alive because the successive E-cycles show different
>> data-bit patterns for the alternate BF and AC3 cycles (4-bit mode).
>>
>>     
>
>
>  
> Yahoo! Groups Links
>
>
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.