[Coco] OS9 sc6551 driver with t2

[Dave Philipsen]

Mmmmmm....I don't think the 6502 has anything to do with the serial 
port.  Maybe the Becker port but I have that switched off.

Dave



On 4/11/2017 5:55 PM, Mark Marlette wrote:
> Dave,
> I haven't had my CoCoFPGA out for a long time.
> I **thought** Gary had a 12MHZ 6502 running all the IO. ????
> Regards, Mark Marlette
>   http://www.cloud9tech.com
> mark at cloud9tech.com
> mark at gamecamaddict.com
>
>        From: Dave Philipsen <dave at davebiz.com>
>   To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>   Sent: Tuesday, April 11, 2017 5:44 PM
>   Subject: Re: [Coco] OS9 sc6551 driver with t2
>     
> Well, this is a 25 MHz 6809 so the capabilities are quite increased as
> far as the CPU's ability to suck the data from the UART.  And, it's not
> a real 6551 either.  So it's possible it could be a problem with the
> hardware but based upon it's actions I'm more inclined to think it's
> something in the driver.  As I recall, the problems continued even when
> I slowed it down to 9600.
>
> Dave
>
>
> On 4/11/2017 5:25 PM, Tim Fadden wrote:
>> On 4/11/2017 1:19 PM, Dave Philipsen wrote:
>>> I'm creating an un-tethered NitrOS9 setup with my CoCo3FPGA. So it
>>> now boots from the SD card and I've stripped drivers and descriptors
>>> associated with DW but I added the sc6551 and t2 modules so I can use
>>> the serial port to transfer a few files back & forth from my laptop
>>> now & then.  I found the drivers in the NITROS9 subdirectory and I
>>> believe they are from an 'official' distribution. So I'm using
>>> Supercomm on the CoCo side and Terraterm on the PC side. Bitrate is
>>> 19.2k.  Most x/ymodem transfers work ok with smaller files but now
>>> and then I get an error that will not resolve.  Larger files over
>>> 100k or so are almost impossible as they will almost surely fail
>>> before finishing.  Turns out that the CoCo3FPGA stops receiving.  I
>>> can exit Supercomm and then restart it and everything works again.
>>> This leads me to believe it's a driver problem as simply closing the
>>> path and re-opening gets it working again for awhile.  Does anyone
>>> have a similar or experience or an idea on what might be causing this?
>>>
>>> Dave
>>>
>> I am amazed you got 19.2k to work at all.  I have never been able to
>> get more than 9600 out of the rs232pak, and for long transfers, in the
>> megabytes only 4800 was reliable.
>>
>>
>