Xref: utzoo comp.os.os9:422 comp.sys.m6809:1044
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!agate!brahms.berkeley.edu!koonce
From: koonce@brahms.berkeley.edu (tim koonce)
Newsgroups: comp.os.os9,comp.sys.m6809
Subject: Re: Assembling Device Drivers/Descriptors
Summary: More info, please?
Message-ID: <22020@agate.BERKELEY.EDU>
Date: 25 Mar 89 01:51:47 GMT
References: <42560@clyde.ATT.COM> <1320@bucket.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: koonce@brahms.berkeley.edu (tim koonce)
Followup-To: comp.os.os9
Distribution: na
Organization: University of California, Berkeley
Lines: 22

You say you can't communicate at anything higher than 300 baud?

First, the obvious questions:
  - What program are you using?
Because of multi-tasking overhead, writing programs that work well under OS9
Level 2, especially with the CoCo 3 ACIAPAK driver, requires a bit of care.
Home-grown programs aren't really recommended unless you have a pretty good
idea of what you're doing.
  - Have you installed the IRQ hack?
The GIME in the CoCo3 isn't too clever about handling interrupts.  Wiring the
interrupt line from the ACIA chip directly to the CPU gets around this.
For that matter, some people have discovered that the interrupt lines inside
the RS232 pak aren't correctly wired.  Since most RSDOS terminal programs
use polling rather than interrupts, it rarely shows up there.
  - How old is the RS232 pak?
Some older RS232 paks used a version of the 6551 ACIA which wouldn't
work well at the 2mhz clock speed.  Some people have solved a lot of
problems by simply replacing the 6551.

Hope this helps.

					- Tim Koonce