Hi

I am working on wince5.0(ARM).i am using 640x480 LCD.
My LCD is working fine at boot time but as soon as display driver loads
nothing will appear on the LCD(Black).

--
Software Developer
Johari Digital Healthcare LTD.
INDIA

RE: LCD Display Driver Problem by CL

CL
Wed Aug 20 00:02:01 PDT 2008

Maybe you can check the debug message when loading display driver. It must be
something wrong with display driver.

"Dipendra" wrote:

> Hi
>
> I am working on wince5.0(ARM).i am using 640x480 LCD.
> My LCD is working fine at boot time but as soon as display driver loads
> nothing will appear on the LCD(Black).
>
> --
> Software Developer
> Johari Digital Healthcare LTD.
> INDIA

RE: LCD Display Driver Problem by Rameshchandra

Rameshchandra
Wed Aug 20 02:18:01 PDT 2008

Give the error that you are getting when the display driver is up and
running.....

If you are display driver is not showing up any errors, then check out
whether you have include userinterface elements like minimal window
configuration etc...

When you not include these components then also you will have a blank
display...even after you display driver is up...

--
Ramesh.c
Innovate Software Solutions.
Bangalore.


"Dipendra" wrote:

> Hi
>
> I am working on wince5.0(ARM).i am using 640x480 LCD.
> My LCD is working fine at boot time but as soon as display driver loads
> nothing will appear on the LCD(Black).
>
> --
> Software Developer
> Johari Digital Healthcare LTD.
> INDIA

RE: LCD Display Driver Problem by Dipendra

Dipendra
Wed Aug 20 04:33:00 PDT 2008

Hi,

I got the following Error message :

Data Abort: Thread=8d5d0a74 Proc=8c226370 'gwes.exe'
AKY=00000009 PC=03981980(s3c2410x_lcd.dll+0x00001980)
RA=0398194c(s3c2410x_lcd.d
ll+0x0000194c) BVA=08210000 FSR=00000007
Data Abort: Thread=8d5d0a74 Proc=8c226370 'gwes.exe'
AKY=00000009 PC=0004c070(gwes.exe+0x0003c070)
RA=00053618(gwes.exe+0x00043618) B
VA=08000008 FSR=00000007

--
Software Developer
Johari Digital Healthcare LTD.
INDIA

Re: LCD Display Driver Problem by Bruce

Bruce
Wed Aug 20 05:14:18 PDT 2008

Take a look at:
http://geekswithblogs.net/BruceEitman/archive/2008/06/02/platform-builder-find-the-source-of-a-data-abort-an.aspx

this will help you find the cause of the data abort.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

"Dipendra" <Dipendra@discussions.microsoft.com> wrote in message
news:F4757D08-D83D-40A1-AEA0-B14A51415EB9@microsoft.com...
> Hi,
>
> I got the following Error message :
>
> Data Abort: Thread=8d5d0a74 Proc=8c226370 'gwes.exe'
> AKY=00000009 PC=03981980(s3c2410x_lcd.dll+0x00001980)
> RA=0398194c(s3c2410x_lcd.d
> ll+0x0000194c) BVA=08210000 FSR=00000007
> Data Abort: Thread=8d5d0a74 Proc=8c226370 'gwes.exe'
> AKY=00000009 PC=0004c070(gwes.exe+0x0003c070)
> RA=00053618(gwes.exe+0x00043618) B
> VA=08000008 FSR=00000007
>
> --
> Software Developer
> Johari Digital Healthcare LTD.
> INDIA



RE: LCD Display Driver Problem by CL

CL
Wed Aug 20 18:28:04 PDT 2008

You can check the s3c2410x_lcd.map file to see in which function the data
abort happened (offset = 0x00001980).

"Dipendra" wrote:

> Hi,
>
> I got the following Error message :
>
> Data Abort: Thread=8d5d0a74 Proc=8c226370 'gwes.exe'
> AKY=00000009 PC=03981980(s3c2410x_lcd.dll+0x00001980)
> RA=0398194c(s3c2410x_lcd.d
> ll+0x0000194c) BVA=08210000 FSR=00000007
> Data Abort: Thread=8d5d0a74 Proc=8c226370 'gwes.exe'
> AKY=00000009 PC=0004c070(gwes.exe+0x0003c070)
> RA=00053618(gwes.exe+0x00043618) B
> VA=08000008 FSR=00000007
>
> --
> Software Developer
> Johari Digital Healthcare LTD.
> INDIA

Re: LCD Display Driver Problem by Dipendra

Dipendra
Wed Aug 20 22:09:01 PDT 2008

Hi,

Now crashing problem is solved but my LCD shows only upper half portion.
i have faced same problem in boot up,but it got resolved by making buffer
double.
i have done same thing in my display driver but it not working in it.

_U32 (*frameBuffer8Bit)[640*2*480];

frameBuffer8Bit = (_U32 (*)[640*2*480])0x30100000;

s2410LCD->LCDSADDR1 = (((_U32)frameBuffer8Bit >> 22) << 21 ) |
((M5D((_U32)frameBuffer8Bit >> 1)) << 0);

s2410LCD->LCDSADDR2 = M5D((_U32)frameBuffer8Bit + (LCD_XSIZE_TFT * 2 *
LCD_YSIZE_TFT) >> 1);

s2410LCD->LCDSADDR3 = (((LCD_XSIZE_TFT - LCD_XSIZE_TFT) / 1) << 11) |
(LCD_XSIZE_TFT / 1);

plz suggest something to get rid of it.

--
Software Developer
Johari Digital Healthcare LTD.
INDIA


"Bruce Eitman [eMVP]" wrote:

> Take a look at:
> http://geekswithblogs.net/BruceEitman/archive/2008/06/02/platform-builder-find-the-source-of-a-data-abort-an.aspx
>
> this will help you find the cause of the data abort.
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> Bruce.Eitman AT EuroTech DOT com
> My BLOG http://geekswithblogs.net/bruceeitman
>
> EuroTech Inc.
> www.EuroTech.com
>
> "Dipendra" <Dipendra@discussions.microsoft.com> wrote in message
> news:F4757D08-D83D-40A1-AEA0-B14A51415EB9@microsoft.com...
> > Hi,
> >
> > I got the following Error message :
> >
> > Data Abort: Thread=8d5d0a74 Proc=8c226370 'gwes.exe'
> > AKY=00000009 PC=03981980(s3c2410x_lcd.dll+0x00001980)
> > RA=0398194c(s3c2410x_lcd.d
> > ll+0x0000194c) BVA=08210000 FSR=00000007
> > Data Abort: Thread=8d5d0a74 Proc=8c226370 'gwes.exe'
> > AKY=00000009 PC=0004c070(gwes.exe+0x0003c070)
> > RA=00053618(gwes.exe+0x00043618) B
> > VA=08000008 FSR=00000007
> >
> > --
> > Software Developer
> > Johari Digital Healthcare LTD.
> > INDIA
>
>
>