[Lcdproc] BLK202a

[Paul Aviles]

I tried with both lcdproc-CVS-current.tar.gz and
lcdproc-CVS-stable-0-5-x.tar.gz and got the same issues. I also tried
with different serial cables and the same.

Here are some pics of what I get. If you connect the power to the unit
it initializes itself pretty good. If you connect the serial cable still
good with the BLK202A label appearing. If you send commands with echo
"blabla" > /dev/ttyS0 it works good too. Then if you load LCDd it starts
showing a "V" where a block character should be, usually at the very
first position in the upper left of the screen and in other places too.

Regards,

Paul

-----Original Message-----
From: Ethan Dicks [mailto:ethan.dicks@gmail.com]=20
Sent: Tuesday, November 06, 2007 6:37 PM
To: Paul Aviles
Cc: lcdproc@lists.omnipotent.net
Subject: Re: [Lcdproc] BLK202a

On 11/6/07, Paul Aviles <paul.aviles@nickelnetworks.com> wrote:
> Hey guys, maybe someone can share some light into the issues I am
having.
> New installation of 0.5.2 and 0.5.1 and I get some malformed
characters on
> the screen. Particularly the letter V appears at the very first
position on
> the screen and where I think the cursor location is.
>
> I have to use 0..5.0 or older to get some decent screens.

This sounds like the bug I fixed in 0.5.2 - go get a recent nightly
tarball and build that.

> I have also tried changing the mtxorb.c code for the initialization
string
> cfsetispeed as below without any results.
>
> //cfsetispeed(&portset, B0);
>
>     cfsetispeed (&portset, speed);

If this is what I think it is, the problem is not baud rate.  The
problem is an incorrect control character sent by the MtxOrb driver
when refreshing the screen.  I submitted a change months ago when I
found it.  There has not been a new release of LCDproc since then, so
you have to get a nightly tarball to get the fix until the next point
release.

-ethan