Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site pedsgo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!hjuxa!petsd!pedsgd!pedsgo!tom
From: tom@pedsgo.UUCP (Tom Gillispie)
Newsgroups: net.micro.cpm
Subject: Re: Help needed with 8251 USART
Message-ID: <129@pedsgo.UUCP>
Date: Thu, 2-Jan-86 15:56:28 EST
Article-I.D.: pedsgo.129
Posted: Thu Jan  2 15:56:28 1986
Date-Received: Sat, 4-Jan-86 04:46:51 EST
References: <1098@brl-tgr.ARPA>
Reply-To: tom@pedsgo.UUCP (Tom Gillispie)
Organization: Perkin-Elmer DSG, Tinton Falls, NJ
Lines: 28

Organization : Concurrent Computer Corp. (a P-E company), Tinton Falls, NJ
Keywords: 


I have shared your frustration with programming the 8251.  Maybe I can help
some.  First, you must 'kick' the 8251 into a mode where it will recognize
and accept the control byte.  If the board you are using has a hardware
reset facility of some type, that may work.  There is a pin on the 8251
that will physically reset the chip, and put it in a mode where it is
waiting for the control byte.  If your board doesnt have that (many dont),
you must send the 8251 several 'invalid' control bytes, which will get it
into a state where it is expecting the control byte.  I have found that
outputting several bytes of 0 will work.  I have seen some code use 2
zeros, and some use 3 zeros, it may not matter.  Once that has been done,
you set up the chip the way it states in the manual.  Your code looks good,
just add the outputting of serveral bytes of zero to the command port
first. 

Second, I have found several things with the 8251.  Some of the older
ceramic-body 8251 chips are not to be trusted.  I was told and found to be
true that you should stick to the plastic parts.  My ceramic 8251s were at
least 5 years old, so maybe newer ceramic parts are ok.  Also, I found that
some of my 8251s would not work correctly (sorry, I cant remember what
wasnt correct) when you ran them with NO PARITY.

Hope this help.

Tom