[Coco] Basic09 <==> 6809 interface.

[L. Curtis Boyle]

The problem with data modules for OS9/6809 (I don’t know if this applies to OSK) is that you have to re-verify the CRC each write to it, which can slow things down (or you shut CRC checking off completely). From appearances, the 6809 version is more meant as a read only file of data. 

Sent from my iPhone

> On Aug 26, 2023, at 6:14 PM, Allen Huffman via Coco <coco at maltedmedia.com> wrote:
> 
> 
>> 
>> On Aug 26, 2023, at 4:43 PM, coco--- via Coco <coco at maltedmedia.com> wrote:
>> 
>> All
>> 
>> Has anyone written a program that allows some shared memory buffer between a
>> Basic09 program and an OS9 assembler program, so that some variables can be shared
>> without having to save them to files in one language and read/write reply in the
>> Other ?
> 
> 
> OS-9 “data modules” are designed for this purpose. I have used them on later versions of OS-9 for the 68000/PPC/etc. but do not have experience with them under OS-9/6809.
> 
> The basic idea is that OS-9 components are modules with a header, body and CRC. For a program the body is the code. For a data module, the body is whatever you want. For example, it could be a compiled list of data for a program to access — useful on a machine without a file system.
> 
> You can “link” to a data module and it is mapped in to your 64K user space (on the CoCo 3, or just there on a 64K machine). You get a pointer to the data area and can read/write bytes to it. Other programs can do the same.
> 
> I am unaware of any built-in OS-9/6809 resource locking, so that would be needed.
> 
> --
> Allen Huffman - PO Box 7634 - Urbandale IA 50323 - 515-999-0227 (vmail/TXT only)
> http://www.subethasoftware.com - https://www.facebook.com/subethasoftware
> 
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>