Re: SVGA, LCD, Win CE 6.0 and PB

Zebra,

Thanks a lot.

Wish you a great Day!

John

"Zebra" wrote:

first of all you need to ask the distributor to help you to register the AMD
developer network,
when they approved, they will send you the username and password, then you
can login the
website to get the source code download.

that's what I got the code from. have fun!

-Zebra
MVP @ TECHWARE,


"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:999F7A8E-BBDD-4EB7-AD1E-2B7D1CA1315D@xxxxxxxxxxxxxxxx
Hi Zebra,

Thank you for offering help. I've been AMD websites. But I could not find
a
site addressing display drver issues, not to mention the source code. That
is
why I asked my vendor if they have the source code. They told me they
don't
have it either. And this is also the reason I am trying to find a solution
other than modifying the source code. But if I can get the source code, it
will help me understand my problem better and maybe provide me a way to
troubleshoot the problem. At the moment I even do not have a practical way
to
troubleshoot (trace) my problem. If by chance you know more details where
I
may be able to find the source code please let me know. I will really
appreciate it. Thanks.

John


"Zebra" wrote:

It sounds like you are using the AMD LX800 SBC, if it's so, there is the
display driver source code from AMD web site, just download it and modify
the LCDC control register table in the display driver to solve your
problem.

-Zebra,
MVP @ TECHWARE


"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT
com> wrote in message news:udtCm$A%23IHA.2348@xxxxxxxxxxxxxxxxxxxxxxx
That depends on your display driver, OAL, and bootloader, in reverse
order
from first-to-execute to last-to-execute.

Paul T.

"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4E02F014-C183-4ED6-9344-7F443E0BED97@xxxxxxxxxxxxxxxx
Paul,

I wish my system worked in the way of yours. :-)

More findings: in my system, the Win XP ignores BIOS setting. It
controls
desktop size, on-LCD image size and the freq of pulses according to
what
I
set in "Display Property Settings". I wish my Win CE also worked this
way.
Paul, can you tell me (or recommend readings) how the resolution
setings
travel down thru Win CE from boot.ini to the place genrating final LCD
scanning signals? Also, can anyone else help me to gain this
knowledge?

Many many thanks!

John

PS. I drew more lines on my display. I found I could draw exactly 701
pixels
long lines (on SVGA setting). I searched the registry (loaded from my
board
with VS 2005), I could not find values of 699, 700, 701 and 702 that
may
(even remotely) be tied to display or display resolution. I found key
values
related to resolution which is "800 600 60". :-(


"Paul G. Tobey [eMVP]" wrote:

None of my devices can do any of those things, so there's no general
answer
to the question. On my devices physical screen surface = image
displayed on
LCD = Windows CE desktop size.

Paul T.

"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:362C7A78-0A71-4FCB-A491-2A06BE3F6220@xxxxxxxxxxxxxxxx
Paul,

thank you for the suggestion. I will try it. I know it is almost
impossible
to analyze and troubleshoot a problem like this without working in
front
of
the setup. The cause could turn out to be a very obvious and stupid
mistake.
I also do tech support. I have plenty stories like that and I've
done
things
like that myself many time before. :-) Before I leave to do
experiments, I
just want to add a few more lines, providing some food for wild
thoughts.
:-)

After playing with my problem more, I can identify three
windows/screens
in
my system:

1) A Physical Screen - tied to BIOS. It displays stable images only
when
the
BIOS is set at SVGA.
2) A Desktop - tied to boot.ini. When I set resolution terms in
boot.ini
as
1024x768. I can have a desktop larger than physical screen window.
The
desktop can be moved around inside the physical screen window by me
dragging
the mouse pointer to the edges of the physical screen.
3) An actual Image Window. The desktop can also move around in this
window
as if in the physical screen window.

My problem is the image window does not match the physical screen
window.
Is
any key in reg file (or a component in NK.bin) that will cause
this?

Thanks!

John

"Paul G. Tobey [eMVP]" wrote:

One thing to do would be to draw rectangles of various sizes on
the
display
and, in that way, find out *exactly* where the black rectangle
begins.
That
is, it might be revealing if its value was 689, as opposed to 700
(and it
gives you a number to search for in code, registry, etc.) Once
you
know
that number, look for it, and one more than it and one less than
it,
in
the
obvious places, particularly in the bootloader, registry, etc.
Yes,
you'll
probably get lots of false-positives, but there's a reasonable
chance
that
you'll find it -- there just isn't much we can do without the
hardware,
the
software, and suitable instrumentation in front of us...

Paul T.

"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F4305EEB-20F7-45F2-9091-92DD805A1194@xxxxxxxxxxxxxxxx
Hi guys,

Thank you very much for offering speculations and suggestions. I
really
appreciate them all.

I've been gone thru all of reg files in catalog. There is no key
as
".../LCDC". There are a few keys look like related to the
resolution.
But
they seem to be right, specifying resolutions with standard
numbers,
e.g.
800x600, 1024x786 and etc. The thing puzzles me most is why it
draws
lines
up
to 700 pixels? Where is this number 700 from? It will be a
better
clue
if
the
number is 640 or 600 (one of the "standard" numbers). :-) So, I
have a
feeling that the problem probably is not very obvious such as a
typo
defining
the resolution as 700x600, or a piece of the code that is wrong
(because
there must be millions of people used it before me). I feel the
problem
is
still in how the NK.bin is built and there is a key(s) that has
an
indirect
effect to the LCD driving, for example, as Paul described,
causing
errors
in
frame buffer preparation or alike. Do you guys know such keys
existed?
Another thing discourages me is I have no way to trace the
problem.
I
can
not
set up "break points" and step thru the execution. :-(

Any speculation about keys or suggestions about how to close in
at
this
problem?

Many thanks!

John

"MichaelH" wrote:

Hello John...

Do you have the following registry: [HKLM]/Drivers/Display/LCDC

or something along this line defined in your BSP? It could be
that
the
CE 6
driver is getting some bad information from the registry and
changing
the
display.

Good luck.
Michael H.

"John" wrote:

Hi,

The orignal discussion of my problem is listed under "A black
strip
on
right
side of LCD" which may be too long to read. So, I summarize
my
problem
and
findings in one post here:

The problem:

I run Win CE 6.0 on an AMD CPU based SBC (Single board
computer)
board.
I've
got a black (blank) strip (100 pixels wide) at the right side
of
the
LCD
covering (or say, cut off) portion of the desktop image.

What I've found:

1) I've got full 800 pixel wide desktop image when I run Win
XP
on
the
same
board with the same LCD.

2) The BIOS image on the LCD is fine. It extends to the edge
of
the
LCD
screen.

3) I drive a CRT and an LCD simultaneously. While I have a
.

Relevant Pages

  • Re: SVGA, LCD, Win CE 6.0 and PB
    ... site addressing display drver issues, not to mention the source code. ... can you tell me how the resolution ... travel down thru Win CE from boot.ini to the place genrating final LCD ...
    (microsoft.public.windowsce.platbuilder)
  • Re: SVGA, LCD, Win CE 6.0 and PB
    ... site addressing display drver issues, not to mention the source code. ... travel down thru Win CE from boot.ini to the place genrating final LCD ... I can have a desktop larger than physical screen window. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: SVGA, LCD, Win CE 6.0 and PB
    ... That depends on your display driver, OAL, and bootloader, in reverse order ... travel down thru Win CE from boot.ini to the place genrating final LCD ... I can have a desktop larger than physical screen window. ... My board vendor thinks this is a display driver problem. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: SVGA, LCD, Win CE 6.0 and PB
    ... the LCDC control register table in the display driver to solve your problem. ... travel down thru Win CE from boot.ini to the place genrating final LCD ... I can have a desktop larger than physical screen window. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Extending MCE from Digital Monitor to CRT monitor?
    ... screen and then click on the window to pull it the remaining distance. ... MC doesn't know or care what kind of display you're putting it ... You could have a CRT hooked to a DVI adapter, or an LCD ...
    (microsoft.public.windows.mediacenter)