Re: 68008 co-processor board complete working design available ...

[Jim Gilbert <brokerjim@gmail.com>]

On Dec 28, 2:13 pm, Jim Gilbert <broker...@gmail.com> wrote:
> On Nov 25, 2:47 pm, Patrick Schaefer <pa.schae...@web.de> wrote:
>
> > Am 24.11.2010 21:53 schrieb Jim Gilbert:
>
> > > Newly posted information:
>
> > > (...)
>
> > Thank you very much! It would be great if you could provide binary
> > versions of the sotware as well. I.e. a hex or bin file for the EPROM,
> > and a dsk or shk with the Prodos part.
>
> > Best regards
> > Patrick
>
> Hi Patrick,
>
> The web page now has .txt files for:
>
> RAMDisk-a65.txt = DOS Toolkit 6502 assembler source for RAMDisk
> Uses 4 simple macros. Not sure macro declarations in proper syntax for
> EDASM since I can't find a manual for it anymore. The macros are
> utterly simple, although they do use local labels.
>
> DBG68.txt = Applesoft Debugger with expansions including built in help
> MON68 Makefile.txt = 4.3 BSD Makefile for 68008 Monitor
> All-h.txt = All .h files needed by the makefile run together into
> one .txt file
> All-i.txt = All .i ( .globl decls ) needed by the makefile run
> together into one .txt file
> All-s.txt = All .s files needed by the makefile run together into
> one .txt file
>
> The 68008 assembler source is AT&T syntax. No macros. Does use local
> labels.
>
> This is all the softcopy anyone, including me, will need to rebuild
> any of the binaries assuming access to the right tools on Windows, or
> probably easier, the right tools on Linux.
>
> All this is free for any use, just identify the author.
>
> Newer technology hosts like Carte Blance offer more memory, more
> features, etc.
>
> I do note that having the coprocessor interface with the 6502 CPU by a
> dedicated 512x9 FIFO in each direction allows some really nice things,
> like moving entire big sectors across the interface without to
> handshake explictly with the guy on the other side.  The FIFOs let the
> 68k and the 6502 both proceed without bothering each other most of the
> time.
>
> Cheers.

And yes, I did REKEY and check all the sources for the Debugger,
Monitor and RAMDisk.