[Coco] DS1216

[Bill Pierce]

Kelly, if you're using the disassembler from the repo disks, it's a 6309 compatible disasm... hence the odd instructions.
Now why is it throwing 6309 code up when it's a 6809 program? It's hitting the FCBs & FDBs at the beginning and seeing them as code... some are reading as 6309 stuff. That's why you have no data at the beginning.

Try using Sleuth... it will give you the "Entry" address when it reads the file in, you can then set the FCB/FDB/FCC/FCS areas, and do fake disasms until you get all set... then save it to disk. I think you'll get a better disassembly with Sleuth... unless it IS actually 6309 code..... But what you described sounded like 6809 being disassembled by 6309 disasm from the wrong entry point.

Also, I think the sources are on RTSI...
Try this and see if it's the same program:
http://ftp://os9archive.rtsi.com/OS9/OS9_6X09/SYSMODS/RTC_Disto_RGB_Utils.lzh

 

 


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: K. Pruitt <pruittk at roadrunner.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Tue, Sep 22, 2015 11:32 pm
Subject: Re: [Coco] DS1216



----- Original Message ----- 
From: "Gene Heskett" <gheskett at wdtv.com>
To:
<coco at maltedmedia.com>
Sent: Tuesday, September 22, 2015 8:06 PM
Subject: Re:
[Coco] DS1216


> On Tuesday 22 September 2015 21:48:41 K. Pruitt wrote:
>
>> >
----- Original Message -----
>> > From: "Gene Heskett" <gheskett at wdtv.com>
>> >
To: <coco at maltedmedia.com>
>> > Sent: Tuesday, September 22, 2015 4:58 PM
>> >
Subject: Re: [Coco] DS1216
>> >
>> >> On Tuesday 22 September 2015 19:52:05 K.
Pruitt wrote:
>> >
>> > <snip>
>> >
>> >>> > --
>> >>>
>> >>> Not to hijack this
thread, but rather than start an entire new
>> >>> thread with no context...
>>
>>>
>> >>> Anybody have any idea why setclk doesn't disassemble correctly?
>>
>>>
>> >>> eim? oim? aim? Where are these op codes coming from? Are these
>> >>>
even real?
>> >>>
>> >>> L02A5    eim   #$63,$0F,s
>> >>>
>> >>> Seriously?  Is
this actually legit code?
>> >>
>> >> Legit code, but for a 6309?
>> >>
>> >>
Cheers, Gene Heskett
>> >> --
>> >> "There are four boxes to be used in defense
of liberty:
>> >> soap, ballot, jury, and ammo. Please use in that order."
>> >>
-Ed Howdershelt (Author)
>> >> Genes Web page
<http://geneslinuxbox.net:6309/gene>
>> >>
>> >> --
>> >
>> > Thanks for taking
the time to answer Gene.
>> >
>> > --
>>
>> I found Chris Burke's "The 6309
Book" online. I'm surprised to se a
>> disassember from 1988 spit out 6309 code.
I thought the 6309 being put
>> in to CoCo's was much later. Also surprised to
see the setclk program
>> written in 1989 contain 6309 code. Some of you guys
were way ahead of
>> the curve.
>
> I bought my first HD63C09EP as a kit from
Chris Burke.  In about that
> late 80's time frame.
>
> As for the setclk, there
should have been in those days, a separate
> version for each cpu as that code
would certainly not have worked on a
> 68x09.  I doubt if it exists today
because of the extremely limited
> amount of difference it would make since its
normally only used by the
> user to set the clock.  With the right clock, that
might be once a day
> if you were being picky.
>
> Cheers, Gene Heskett
> -- 
>
"There are four boxes to be used in defense of liberty:
> soap, ballot, jury,
and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page
<http://geneslinuxbox.net:6309/gene>
>
> -- 

I don't think setclk is
disassembling correctly for whatever reason. I see 
no data in this disassembly
and there should be, based on just looking at 
the binary with a hex editor.
I've placed data at the bottom of my code and 
seen disassembler results like
this before. I don't think I ever saw 6309 
code pop up before. But it does run
on a 6809 and has been on my CoCo since 
at least 1990 doing it's thing so I'm
going to assume the 6309 code in the 
disassembly is just randomness. The
disaasembler had to spit out something 
so it did.


-- 
Coco mailing
list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco