Ethan Dicks

The driver isn't the issue, it's the connection back to the CPU. It's likely that's just an HD44780 under one of those epoxy bubbles. That's the driver you probably need. What you have to know is what I/O location in memory the ports are at, and what bits control which functions. Even more than that, the HD44780 can be talked to in 4-bit mode or 8-bit mode and you'd need to know that just to begin speaking to the LCD. In the case of attaching a raw HD44780-type 16x2 LCD, there are examples in the...

The driver isn't the issue, it's the connection back to the CPU. It's likely that's just an HD44780 under one of those epoxy bubbles. That's the driver you probably need. What you have to know is what I/O location in memory the ports are at, and what bits control which functions. Even more than that, the HD44780 can be talked to in 4-bit more or 8-bit mode and you'd need to know that just to begin speaking to the LCD. In the case of attaching a raw HD44780-type 16x2 LCD, there are examples in the...

That's an odd looking connector up there. From the view of the lit LCD and the part number, it's likely that the core LCD is some sort of 16x2 HD44780-based LCD module, but it looks tough to guess which lines at the connector might correspond to which standard HD447800 signals because the die is under an epoxy blob, not in a standard PLCC or QFP package that one might trace out. I won't say it's impossible to figure out but it looks quite difficult.

Screen not overwriting background

LCDd only updates the portions of the screen that it has changed. It has no idea...

On Mon, Jan 4, 2016 at 2:36 AM, Sam Bingner sbingner@users.sf.net wrote: WOW, over...

On Mon, Dec 7, 2015 at 4:09 AM, MTZ mtz_ro_2003@users.sf.net wrote: Hello I'm interested...

On Tue, Nov 24, 2015 at 4:11 PM, Alex Scarbro alexscarbro@users.sf.net wrote: Hello,...