[Coco] 6809 File I/O

[Michael R. Furman]

Pete,

Again this is C code, but James Dessart who made early contributions to gcc6809 actually wrote an entire libc and coco library system that includes calls into the coco roms to do various things.  I am pretty sure that this code will not compile and run with a modern version of gcc6809 without some modifications, but you can at least look at how he is doing the rom call accesses, probably need to start with the implementation of fopen in stdio and drill down into where the roms are actually called. 

https://sourceforge.net/projects/gcc-coco/ <https://sourceforge.net/projects/gcc-coco/>


—

Michael R. Furman
Email: n6il at ocs.net
Phone: +1 (408) 480-5865


> On Mar 18, 2017, at 11:17 AM, Darren A <mechacoco at gmail.com> wrote:
> 
> On Sat, Mar 18, 2017 at 12:02 PM, Peter Cetinski <pete at pski.net <mailto:pete at pski.net>> wrote:
> 
>>> On Mar 18, 2017, at 12:32 PM, lost <lost at l-w.ca> wrote:
>>> The stuff in the disk edtasm manual assumes you are using that weird
>> color trsdos thing that disk edtasm runs under. In other words,  that stuff
>> isn't for raw disk basic.
>> 
>> Ah, that makes sense.  I was wondering if anyone actually ever used that
>> EDTASM DOS.
>> 
>> So, it looks like there are no documented high level disk routines, like
>> open, write, etc. for RS Disk Basic to use from assembly language?  Is
>> there any way to tap into to the Basic ROM I/O routines?  Or do we
>> essentially have to work at the sector/track level?
>> 
>> Thanks
>> 
> 
> 
> The CMOC compiler includes source code for an RSDOS file I/O library.
> 
> It can be found in the src/support/disk.h file.
> 
> https://perso.b2b2c.ca/~sarrazip/dev/cmoc.html <https://perso.b2b2c.ca/~sarrazip/dev/cmoc.html>
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com <mailto:Coco at maltedmedia.com>
> https://pairlist5.pair.net/mailman/listinfo/coco <https://pairlist5.pair.net/mailman/listinfo/coco>