[Coco] Relocatable ROM monitor

Arthur Flexser flexser at fiu.edu
Wed Oct 3 00:17:56 EDT 2018


P.S.  A plus is that the manual contains a commented disassembly of the
source of Edtasm and (I think) ZBUG.

Art

On Tue, Oct 2, 2018 at 11:36 PM, Arthur Flexser <flexser at fiu.edu> wrote:

> It may be the ZBUG, included with Disk Edtasm+ from Radio Shack, already
> handles everything you want.  I believe the Disk version of ZBUG includes
> its own versions of CHROUT and POLCAT, though I'm not 100% sure about
> that.  It's probably in the archives here.  It has also been patched by
> third parties for 80-column output and some other niceties (Robert Gault?)
> I'm pretty sure it is relocatable.
>
> Art
>
> On Tue, Oct 2, 2018 at 11:14 PM, tim lindner <tlindner at macmess.org> wrote:
>
>> Yes it is. Thanks you very much!
>> On Tue, Oct 2, 2018 at 5:54 PM Dave Philipsen <dave at davebiz.com> wrote:
>> >
>> > I got the monitor working on the CoCo.  It’s not relocatable and it
>> relies on POLCAT and CHROUT right now: https://youtu.be/dcT5mnyPtCw
>> >
>> > It’ll take me a little time to write a keyboard scan routine, character
>> out routine, re-format for 32 columns, and re-write a few sections for
>> re-locatable code.  It allows you to view/edit memory locations, do a dump
>> of memory from a specific address, and execute code at a specific address.
>> Is that kind of what you want?
>> >
>> > Dave
>> >
>> > > On Oct 2, 2018, at 1:35 PM, tim lindner <tlindner at macmess.org> wrote:
>> > >
>> > > 32.
>> > >
>> > >> On Tue, Oct 2, 2018 at 11:34 AM Dave Philipsen <dave at davebiz.com>
>> wrote:
>> > >>
>> > >> Yeah, that makes it a little more difficult since I'd have to write
>> the
>> > >> keyboard scan and text display routines from scratch.  They are
>> normally
>> > >> just a simply read/write to a UART.  What text mode do you plan on
>> using
>> > >> for the monitor (32,40,80)?
>> > >>
>> > >> Dave
>> > >>
>> > >>> On 10/2/2018 1:19 PM, tim lindner wrote:
>> > >>> I love to see it. But it'll prolly also need adjusting to read the
>> > >>> CoCo keyboard and output to the CoCo video.
>> > >>>
>> > >>> I'm looking for something that doesn't depend on POLCAT or CHROUT.
>> > >>>
>> > >>>> On Tue, Oct 2, 2018 at 11:16 AM Dave Philipsen <dave at davebiz.com>
>> wrote:
>> > >>>> I have a monitor that I’ve used for years on embedded systems. It
>> probably wouldn’t be too tough to make sure it’s relocatable. It uses a few
>> locations in direct page RAM though.
>> > >>>>
>> > >>>> Dave
>> > >>>>
>> > >>>>> On Oct 2, 2018, at 10:16 AM, tim lindner <tlindner at macmess.org>
>> wrote:
>> > >>>>>
>> > >>>>> Does anyone know of a relocatable ROM monitor program for the
>> CoCo?
>> > >>>>>
>> > >>>>> Something I can load in to RAM arbitrarily and start peeking and
>> > >>>>> poking RAM, ROM and peripherals?
>> > >>>>>
>> > >>>>>
>> > >>>>> --
>> > >>>>> --
>> > >>>>> tim lindner
>> > >>>>>
>> > >>>>> "Proper User Policy apparently means Simon Says."
>> > >>>>>
>> > >>>>> --
>> > >>>>> 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
>> > >
>> > >
>> > >
>> > > --
>> > > --
>> > > tim lindner
>> > >
>> > > "Proper User Policy apparently means Simon Says."
>> > >
>> > > --
>> > > 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
>>
>>
>>
>> --
>> --
>> tim lindner
>>
>> "Proper User Policy apparently means Simon Says."
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>
>
>


More information about the Coco mailing list