public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: "Wilson Kwan" <wilson@kinesphere.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] LCD on EP7211
Date: Wed, 31 Jan 2001 14:49:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20010131174437.00aa1100@larwe.com> (raw)
In-Reply-To: <005f01c08bd7$7a806c00$0b02a8c0@r2d2>

Hi Wilson,

>Has anyone been able to get the cirrus 72xx LCD code sample to work
>recently? I recompiled the code and checked the values for all of the
>control registers in the Cirrus documentation. It looks correct but when I
>initialize the ALPS LCD on my EP7211 board I get alot of garbage on the
>screen. When I try to clear the screen by writing zeroes to 0xc0000000 my
>program just hangs. Any ideas anyone?

The sample code in eCos works A-OK for me (I am using the 7212, but it's 
the same board). Are you 100% certain you have initialized your pointer 
correctly? I tested initially using the Alps grayscale 640x240 LCD and now 
I've interfaced a color QVGA LCD, which is working great! (with tweaking, 
of course).

However I did see some weird behavior with the lcd_printf routine (bad 
characters, garbage characters). Try commenting out all the places in the 
LCD test source that write to display memory; just call that file to init 
the LCD registers. Then try your manual memory write.

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."

  reply	other threads:[~2001-01-31 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31 14:43 Wilson Kwan
2001-01-31 14:49 ` Lewin A.R.W. Edwards [this message]
2001-01-31 15:10   ` Wilson Kwan
2001-01-31 15:19     ` Lewin A.R.W. Edwards
2001-01-31 16:20       ` Wilson Kwan
2001-01-31 19:01         ` Lewin A.R.W. Edwards
2001-02-01 22:26           ` Wilson Kwan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4.3.2.7.2.20010131174437.00aa1100@larwe.com \
    --to=larwe@larwe.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=wilson@kinesphere.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).