Intro

[John S Gwynne]

--------

   In message <940505135705.2dc04180 at STDVAX.GSFC.NASA.GOV> , you write:
 
| A while ago I worked with a company called CUbit - they made, among other 
| things, an 80186 based, STD Bus board.  What I particularly enjoyed about 
| their set-up is that the on board ROMs would communicate with Borland's C 
| Remote debugger.   That means you write the code on a PC (all Borland), 
| compile and link it, and then down load it to the board - and you can step 
| through the code running on the remote CPU.  A breeze to debug.  Then you 
| link the code with a provided library and you can burn that code directly 

Yea, this can also be done with GNU's gcc and the GNU debugger gdb; a remote
serial interfaced debugger. That's why I've chosen to work with the 68000 and
a C cross-compiler. It would be nice if we all used the same CPU but I don't
think it's going to happen. A more reasonable goal would be to stick with an
ANSI-C language (available for PC's, 68HC11's, and about everything
else)(avoiding calls to the standard library functions) and have a common
interface bus that would let us share sensory interface designs. This way 
you could use the 80186, I could use a 68HC000, and ???? could use 
his 68HC11. We could all still share the software (with vary minor changes) 
and sensor interface designs.



                                       John S Gwynne
                                          Gwynne.1 at osu.edu
_______________________________________________________________________________
               T h e   O h i o - S t a t e   U n i v e r s i t y
    ElectroScience Laboratory, 1320 Kinnear Road, Columbus, Ohio 43212, USA
                Telephone: (614) 292-7981 * Fax: (614) 292-7292
-------------------------------------------------------------------------------