LCD 240x128 need help - website link with pdf file

[myown]

LCD 240x128 need help

This is Doc for LM24010z (240x128) LCD
**broken link removed**

PLEASE Help to write C-function to output pixel with some coordinates(X,Y)

Thanks!

 

[C-Man]

Re: LCD 240x128 need help

Might not be exactly what you are looking for but read here:





best regards

 

[myown]

Re: LCD 240x128 need help

Thanks for links but here LCD with special input data and I need
help to write function to send it to LCD

 

[C-Man]

Re: LCD 240x128 need help

Sorry that I did not look at your datasheet.

This is a LCD module which needs an external controller who refreshes the image 70 to 80 times a second. When you look at the timing diagrams I do not think that you can do this easily with a simple microcontroller.

Maybe you could use an FPGA or something similiar to do what you want?

You can also take a look at what this guy has done:
http://elm-chan.org/docs/avr/avrdma_e.html

best regards

 

[myown]

Re: LCD 240x128 need help

Ok not PIC but I don't want to use FPGA
How about 2 PIC or DSpic
That don't metter . PLEASE help with simple function to drive an 1 Pixel on LCD

 

[C-Man]

Re: LCD 240x128 need help

OK maybe this can help you (not tested):

#define PIXELS_IN_X 240
#define PIXELS_IN_Y 128

const unsigned char Mask[8]={0x80, 0x40, 0x20, 0x10, 0x08, 0x04, 0x02, 0x01}; // for setting/clearing a dot
unsigned char Shadow_Memory[PIXELS_IN_Y][PIXELS_IN_X / 8]; // this holds what is displayed at the LCD

// allowed range for x:0 (left) to 239 (right), allowed range for y:0 (top) to 127 (bottom)
void set_pixel(unsigned char x, unsigned char y)
{
unsigned char mask=Mask[x & 0x07];

Shadow_Memory[y][x >> 3]|=mask;
}

// allowed range for x:0 (left) to 239 (right), allowed range for y:0 (top) to 127 (bottom)
void clear_pixel(unsigned char x, unsigned char y)
{
unsigned char mask=Mask[(x & 0x07) ^ 0xFF];

Shadow_Memory[y][x >> 3]&=mask;
}

And you still need a function that outputs Shadow_Memory byte by byte to your LCD at 70 or more times per second and this is the main problem that can not easily be solved with a small mirocontroller as I have written earlier ....

best regards