[Coco] CoCoSDC and Extended ADOS3

Fri Nov 18 16:01:53 EST 2016

Hmmm...   Not sure what to do at this point to get it to work.

Thanks for the info on the preamble and postamble!

-Ron

On Fri, Nov 18, 2016 at 2:34 PM, William Astle <lost at l-w.ca> wrote:

> Actually, it isn't. Those extra 10 bytes are the preamble and postamble
> required by LOADM and don't actually get loaded to memory.
>
> Still, even if the file was 10 bytes too long, that wouldn't affect the
> "WRITE MEM" command which happens *after* the LOADM and works from data in
> memory. It has no idea where those bytes came from.
>
> On 2016-11-18 01:24 PM, Arthur Flexser wrote:
>
>> That sounds like a very plausible explanation of the FC error.
>>
>> Art
>>
>> On Fri, Nov 18, 2016 at 3:18 PM, Ron Klein <ron at kdomain.org> wrote:
>>
>>> Everyone,
>>>
>>> I just checked.  The EPROM.BIN file is 16394 bytes.  It looks like 10
>>> bytes
>>> too big, so Mike Rowan might be correct when he said the header and
>>> footer
>>> (5 bytes each) might need to be stripped prior to flashing...  Could this
>>> be the cause of the FC error?
>>>
>>> Thanks
>>>
>>> -Ron
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Nov 18, 2016 at 2:15 PM, Ron Klein <ron at kdomain.org> wrote:
>>>
>>> Hi Brett,
>>>>
>>>> Funny enough I did try this as my first attempt to flash Extended ADOS3
>>>> (before I set out to do it manually).
>>>>
>>>> When running the program, I get the following:
>>>>
>>>> SOURCE FILENAME
>>>> ? EPROM.BIN
>>>> DEST BANK NO
>>>> ? 7
>>>> COPY ROM 1 :EPROM.BIN TO BANK 7
>>>> ? Y
>>>> DONE
>>>> OUT OF RANGE (0-3).
>>>> RG ERROR IN 500
>>>>
>>>> Thanks
>>>>
>>>> -Ron
>>>>
>>>>
>>>>
>>>> On Fri, Nov 18, 2016 at 2:08 PM, Brett Gordon <beretta42 at gmail.com>
>>>> wrote:
>>>>
>>>> Ron, I have a simple wrapper util on my cocoboot2 site, that will flash
>>>>> a
>>>>> straight, flat rom to sdc.  The disk image is called "sdcutils.dsk".
>>>>>
>>>>> brett
>>>>> On Nov 18, 2016 3:02 PM, "William Astle" <lost at l-w.ca> wrote:
>>>>>
>>>>> First of all, you would use &H2000 as your argument for WRITE MEM
>>>>>>
>>>>> because
>>>>>
>>>>>> that's the first address of your image, but that shouldn't be what's
>>>>>> causing the FC error.
>>>>>>
>>>>>> You should check the documentation for WRITE MEM to make sure you have
>>>>>>
>>>>> the
>>>>>
>>>>>> arguments right (right order, etc.) and there aren't any restrictions
>>>>>> on
>>>>>> where the ROM image can be located or the maximum size you can flash
>>>>>> at
>>>>>> once.
>>>>>>
>>>>>> On 2016-11-18 12:52 PM, Ron Klein wrote:
>>>>>>
>>>>>> I tried the alternate take on the PCLEAR way but continue to get an FC
>>>>>>> error anytime I try to flash the CoCoSDC:
>>>>>>>
>>>>>>> PCLEAR1
>>>>>>> CLEAR 200,&H1FFF
>>>>>>> LOADM"EPROM.BIN"
>>>>>>> KILL MEM @7
>>>>>>> WRITE MEM @7,&H1FFF,&HC000,16384-256
>>>>>>>
>>>>>>> Argh!
>>>>>>>
>>>>>>> -Ron
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Nov 18, 2016 at 1:39 PM, William Astle <lost at l-w.ca> wrote:
>>>>>>>
>>>>>>> I wonder if it has occurred to anyone to just load the file with an
>>>>>>>
>>>>>> offset
>>>>>
>>>>>> so it loads at &H4000? Then the CLEAR command, etc., in the sequence
>>>>>>>> would
>>>>>>>> be sufficient. If the file loads by default at &H2000, then you can
>>>>>>>>
>>>>>>> add
>>>>>
>>>>>> an
>>>>>>>> offset of &H2000 to load it to &H4000:
>>>>>>>>
>>>>>>>> LOADM"EPROM.BIN",&H2000
>>>>>>>>
>>>>>>>> However, for complete correctness you should use &H3FFF, not &H4000
>>>>>>>>
>>>>>>> since
>>>>>
>>>>>> the address sets the highest address DECB will use, not the first
>>>>>>>>
>>>>>>> address
>>>>>
>>>>>> of the reserved area. It will probably work fine due to a fluke about
>>>>>>>>
>>>>>>> how
>>>>>
>>>>>> things get set up related to string space, but to be completely
>>>>>>>>
>>>>>>> correct,
>>>>>
>>>>>> you should set the address correctly.
>>>>>>>>
>>>>>>>> The other suggestion of a PCLEAR1 first and use &H1FFF (adjusted for
>>>>>>>> correctness) as the CLEAR argument should also work. You're getting
>>>>>>>>
>>>>>>> the
>>>>>
>>>>>> OM
>>>>>>>> error because you're trying to put the top of memory for DECB below
>>>>>>>>
>>>>>>> the
>>>>>
>>>>>> top
>>>>>>>> of the PMODE graphics pages. If you do go that route, you'll have to
>>>>>>>> adjust
>>>>>>>> the argument to your WRITE MEM command to match where ERPOM.BIN
>>>>>>>> loads
>>>>>>>>
>>>>>>> or
>>>>>
>>>>>> you'll be writing the top half of the ROM image followed by 8K of
>>>>>>>>
>>>>>>> junk to
>>>>>
>>>>>> the flash.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 2016-11-18 12:12 PM, Ron Klein wrote:
>>>>>>>>
>>>>>>>> Hi Art,
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Changing the CLEAR statement to:
>>>>>>>>>
>>>>>>>>> CLEAR 200, &H2000
>>>>>>>>>
>>>>>>>>> ... results in an ?OM ERROR
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Changing the CLEAR statement to:
>>>>>>>>>
>>>>>>>>> CLEAR 200, &H7000
>>>>>>>>>
>>>>>>>>> ... results in crashing the Coco 3 after doing a LOADM "EPROM.BIN"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Nov 18, 2016 at 1:00 PM, Arthur Flexser <flexser at fiu.edu>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Ron, your CLEAR 200,&H4000 statement will plop the stack in the
>>>>>>>>>
>>>>>>>> middle
>>>>>
>>>>>>
>>>>>>>>> of the region reserved for the code you are loading in, so that the
>>>>>>>>>> stack will get overwritten by the code, which does not bode well
>>>>>>>>>> at
>>>>>>>>>> all.  Try using $2000 or $7000 instead of $4000.
>>>>>>>>>>
>>>>>>>>>> Art
>>>>>>>>>>
>>>>>>>>>> On Fri, Nov 18, 2016 at 1:46 PM, Ron Klein <ron at kdomain.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Art,
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> That's how I was treating it, but seem to be getting an FC error
>>>>>>>>>>>
>>>>>>>>>> when
>>>>>
>>>>>> attempting to flash it to the CoCoSDC.
>>>>>>>>>>>
>>>>>>>>>>> I do the following:
>>>>>>>>>>>
>>>>>>>>>>> KILL MEM @7
>>>>>>>>>>> CLEAR 200,&H4000
>>>>>>>>>>> LOADM"EPROM.BIN"
>>>>>>>>>>> WRITE MEM @7,&H4000,&HC000,16384-256
>>>>>>>>>>>
>>>>>>>>>>> I get the following error:
>>>>>>>>>>>
>>>>>>>>>>> ?FC ERROR
>>>>>>>>>>>
>>>>>>>>>>> Not sure what the issue is as the SYNTAX is correct.  I'm
>>>>>>>>>>> thinking
>>>>>>>>>>>
>>>>>>>>>> it
>>>>>
>>>>>> has
>>>>>>>>>>> something to do with the addresses.
>>>>>>>>>>>
>>>>>>>>>>> Mike Rowan brought up the binary header and footer information as
>>>>>>>>>>> being
>>>>>>>>>>> a
>>>>>>>>>>> possible issue.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> -Ron
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Nov 18, 2016 at 12:35 PM, Arthur Flexser <
>>>>>>>>>>> flexser at fiu.edu>
>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Ron, I'm not sure if this is what you need, but...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> The EPROM.BIN file starts at $2000, but it is like a cartridge
>>>>>>>>>>>>
>>>>>>>>>>> that
>>>>>
>>>>>> would ultimately reside at $C000.  So, whatever method you'd use
>>>>>>>>>>>>
>>>>>>>>>>> for
>>>>>
>>>>>> a
>>>>>>>>>>>> cartridge file of 16K should be applicable to it.
>>>>>>>>>>>>
>>>>>>>>>>>> Art
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Nov 18, 2016 at 11:58 AM, Ron Klein <ron at kdomain.org>
>>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>
>>>>>>
>>>>>>>>>>>> Hello everyone,
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've been wanting to use ADOS again and went through the steps
>>>>>>>>>>>>> to
>>>>>>>>>>>>>
>>>>>>>>>>>>> create
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> a
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> customized EPROM.BIN for Extended ADOS3.  I'm trying to figure
>>>>>>>>>>>> out
>>>>>>>>>>>>
>>>>>>>>>>>>> the
>>>>>>>>>>>>> correct method for flashing this BIN to bank 7 of the CoCoSDC
>>>>>>>>>>>>> and
>>>>>>>>>>>>>
>>>>>>>>>>>>> confused
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> by the start and ending addressing required for this 16K ROM and
>>>>>>>>>>>>
>>>>>>>>>>> how
>>>>>
>>>>>>
>>>>>>>>>>>>> to
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> tell it to use bank 7.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Is anyone else using ADOS/Extended ADOS3 with their Coco 1,2 or
>>>>>>>>>>>>> 3
>>>>>>>>>>>>> and
>>>>>>>>>>>>>
>>>>>>>>>>>>> a
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> CoCoSDC?
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Thank you!
>>>>>>>>>>>>>
>>>>>>>>>>>>> -Ron
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> 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
>