[Coco] Level 1 & Drivewire

Sun Jan 3 13:29:11 EST 2016

Hi Bill,
no; my mmu does not provide that capability.  If this turns out to be a big
problem or performance sink I could look at changing the behaviour.
Neal.
On 3 Jan 2016 18:08, "Bill Nobel" <b_nobel at hotmail.com> wrote:

> The reason I ask is Level 2 on the CC3 has a vector ram page that is
> always present in the 64k space of either task from $fe00-$ffff (basically
> top of ram) no matter what bank is mapped into logical block 7 or 15 but
> can be modified.  The CC3 uses block $3f as the base for setting up this
> area of memory (handled in REL/KRN).
>
> This is where the main IRQ vectors and task switching software sits (the
> core of Level 2).  I’m wondering does your MMU support this same type of
> scheme?  or do I have to for now make sure every block of ram has this code
> by copying. I know you state $ffd0-$ffdf is always hardware.
>
> Bill Nobel
>
> > On Jan 3, 2016, at 8:43 AM, Neal Crook <foofoobedoo at gmail.com> wrote:
> >
> > Bill,
> > Block 7 of the MMU is slightly different from the others. You can map
> > memory into it in the same way as for all the other blocks. However, the
> > address region ffd0-ffdf always accesses the I/O devices: any
> > underlying/mapped RAM is NOT corrupted. I think that answers your
> question
> > but if I misunderstood please ask again.
> >
> > Neal
> > I have already been looking at that Neal.  I think doing Level 2 is a
> > better first step, as I have been looking at everything you have so far
> in
> > hardware, and it looks like it won’t be that difficult.  I actually think
> > Krn will end up smaller than the CC3 version, by your using only 2
> > registers on the MMU rather than the CC3’s 16 plus task select
> register.  I
> > am making one assumption though on the MMU your logical block 7 is it the
> > same as the CC3 to use physical block $3f for the top of RAM?  The CC3
> uses
> > physical $3f as the top of memory in the DAT registers for the top of
> > hardware and vectors, or is that a value that won’t make a difference
> what
> > is stored in logical block 7.
> >
> > Bill Nobel
> >
> >
> >> On Jan 2, 2016, at 12:30 PM, Neal Crook <foofoobedoo at gmail.com> wrote:
> >>
> >> Hi Bill (Nobel),
> >>
> >> I checked the Drivewire spec. and found that it calls for 1 start + 8
> data
> >> + 1 stop and that 115,200bps is a supported speed.
> >> I reviewed the UART RTL and ran an RTL simulation and confirmed that the
> >> UART is hard-wired for 1 start + 8 data + 1 stop -- and the default
> >> configuration runs at 115,200bps.
> >>
> >> In summary, I was incorrect to indicate any hardware impediment. It
> seems
> >> as though "all" that's needed is a version of dwio.asm that writes to a
> >> 6850-style UART. Are you interest in working on this?
> >>
> >> regards,
> >>
> >> Neal.
> >>
> >> On 2 January 2016 at 02:22, Chad H <chadbh74 at hotmail.com> wrote:
> >>
> >>> Using DriveWire on NitrOS9 level 1 here with my CoCo 2.  Yes, it works
> >>> great at 'normal' speed.   Double speed works well in HDBDOS but not
> with
> >>> the current files in the repo.  Something was broken on the newer
> files.
> >>> Should not effect NitrOS9 though.
> >>>
> >>> - Chad H
> >>> http://sites.google.com/site/cbhlab101/
> >>>
> >>> -----Original Message-----
> >>> From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Bill
> Pierce
> >>> via Coco
> >>> Sent: Thursday, December 31, 2015 9:38 AM
> >>> To: coco at maltedmedia.com
> >>> Cc: Bill Pierce
> >>> Subject: Re: [Coco] Level 1 & Drivewire
> >>>
> >>> Bill, the repo "latest" has disk images of NitrOS9 L1 w/dw.
> >>> I have used L1 & DW4 with both my Coco 1 & my Coco 2 as well as with
> > XRoar.
> >>> The only thing is the standard L1 DW distro disk does not leave much
> >>> ram... you may need to strip out a few unneeded modules to get some
> > memory
> >>> back. The Coco 1 disks have dw drivers that run at 38400 baud (due to
> odd
> >>> serial setup) and Coco 2 disk have drivers for 57600 baud (can't double
> >>> speed a Coco 2).
> >>>
> >>> DriveWire works nicely on NitrOS9 L1 :-)
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Bill Pierce
> >>> "Charlie stole the handle, and the train it won't stop going, no way to
> >>> slow down!" - Ian Anderson - Jethro Tull
> >>>
> >>>
> >>>
> >>> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> >>> https://sites.google.com/site/dabarnstudio/
> >>> Co-Contributor, Co-Editor for CocoPedia
> >>> http://www.cocopedia.com/wiki/index.php/Main_Page
> >>> Global Moderator for TRS-80/Tandy Color Computer Forums
> >>> http://www.tandycoco.com/forum/
> >>>
> >>> E-Mail: ooogalapasooo at aol.com
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: Bill Nobel <b_nobel at hotmail.com>
> >>> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> >>> Sent: Thu, Dec 31, 2015 10:01 am
> >>> Subject: [Coco] Level 1 & Drivewire
> >>>
> >>> Hey All,  I have a question.  Has anybody tried or is it even possible
> to
> >>> use Drivewire on Level 1 Nitros9?I’m curious as I now have Neal Crooks
> >>> Level1 Nitros9 with 4 DS Drives setup with 512K Ram (only 64k used
> under
> >>> Level 1) and would like to get the further Drive access and
> > communication a
> >>> lot better.I have Drivewire Servers already setup and working from
> >>> emulators, but wonder if Level1 has the same capability.Bill Nobel--
> Coco
> >>> mailing listCoco at maltedmedia.comhttps://
> >>> pairlist5.pair.net/mailman/listinfo/coco
> >>>
> >>> --
> >>> Coco mailing list
> >>> Coco at maltedmedia.com
> >>> https://pairlist5.pair.net/mailman/listinfo/coco
> >>>
> >>> -----
> >>> No virus found in this message.
> >>> Checked by AVG - www.avg.com
> >>> Version: 2016.0.7294 / Virus Database: 4489/11304 - Release Date:
> > 01/01/16
> >>>
> >>>
> >>> --
> >>> Coco mailing list
> >>> Coco at maltedmedia.com
> >>> https://pairlist5.pair.net/mailman/listinfo/coco
> >>>
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> https://pairlist5.pair.net/mailman/listinfo/coco
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > https://pairlist5.pair.net/mailman/listinfo/coco
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > https://pairlist5.pair.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>