[Coco] Noob 6809 ASM programmer looking for tips

[Dave Philipsen]

Actually, I pretty much agree with Mark on this.  Once you get the 
'hang' of assembler whether on a Z-80, 6809, 6502, 68000, or 8088 then 
pretty much all you need is a reference type book.  You don't need to be 
taught assembler all over again for another processor. When I went from 
programming the 6809 to programming the 68000 there were a whole bunch 
of new registers and stuff but the concept remained the same.  I bought 
the 68000 Leventhal book and was writing assembly code (for the 68000) 
in short order.  You also learn a few tricks on the way by experimenting 
or by looking at other people's code.

Dave


On 12/29/2015 2:13 PM, Cocodemus wrote:
> I don't agree that you need only reference because different cpu work in different ways. In a z-80 you would use as many register possible when with a 6502 you need to know about 0 page and how it does everythink with just one register.
>
>
>
> Sent from my iPhone
>
>> On Dec 26, 2015, at 12:17 AM, Mark McDougall <msmcdoug at iinet.net.au> wrote:
>>
>>> On 25/12/2015 6:03 AM, ricspam at mpc.com.br wrote:
>>>
>>> Now I'd like to develop a couple of games for the Coco, and I want (and probably
>>> need) do it in assembly. So, any tips from experts such as you guys are really
>>> welcomed!
>> I'll throw my $0.02 in though I suspect the mainstream won't agree with me.
>>
>> For books, I never really liked Leventhal (sp?) and prefer Zaks (Sybex). If you're fluent in other assemblers you'll likely need nothing more than a reference anyway. Ditto for any Coco books; the GIME data sheet and source listings of example code should suffice - _if_ you've coded for other platforms.
>>
>> As for assembler, I use ASXXX because I develop for multiple 8/16-bit CPU's and like the fact that I can use the same syntax for all of them.
>>
>> My build environment is command-line make (or simple scripts) and my text editor of choice (everyone has their own favourite, I won't bore you with mine).
>>
>> My test environment includes file2dsk for the Coco to produce a DSK image before launching MESS.
>>
>> There's no integrated IDE or turnkey build-and-run with a mouse click, but I've tended to always roll my own tools anyway. And once you've set it all up, it's easier to customise, and easier and more portable from host to host and into version control software for example. You can also archive the entire development environment for each project in a single archive that doesn't require installation, registry settings, etc etc.
>>
>> Regards,
>>
>> -- 
>> |              Mark McDougall              | "Electrical Engineers do it
>> |  <http://members.iinet.net.au/~msmcdoug> |   with less resistance!"
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco