From owner-diy_efi  Fri Oct 28 19:04:55 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA22071; Fri, 28 Oct 94 19:04:55 GMT
Received: from wotan.compaq.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA22066; Fri, 28 Oct 94 15:04:54 -0400
Received: from twisto.eng.hou.compaq.com by wotan.compaq.com with smtp
	(Smail3.1.28.1 #12) id m0r0wES-000vK4C; Fri, 28 Oct 94 13:40 CDT
Received: from bangate.compaq.com by twisto.eng.hou.compaq.com with smtp
	(Smail3.1.28.1 #10) id m0r0wCf-000uIZC; Fri, 28 Oct 94 13:39 CDT
Message-Id: <m0r0wCf-000uIZC@twisto.eng.hou.compaq.com>
Received: by bangate.compaq.com with VINES ; Fri, 28 Oct 94 13:33:20 CDT
Date: Fri, 28 Oct 94 13:21:24 CDT
From: Steve=Ravet%Prj=Eng%PCPD=Hou@bangate.compaq.com
Subject: the diy-sbc
To: diy_efi
Cc: 
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI

Just got your schematic and printed it, good work.  I have a couple questions:

1)  what is the circuitry connected to IC9 pin1?  Debounce for the switch?

2)  what are your pal equations?


also, a comment labeling each bus and what signals are on it would be nice.
maybe put the pal equations on the schematic too?


Anyway, it seems complete, what are your plans for enhancements?  I mean on 
this board, not plans for expansion boards...

--steve


From owner-diy_efi  Fri Oct 28 21:05:27 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA22432; Fri, 28 Oct 94 21:05:27 GMT
Received: from localhost.eng.ohio-state.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA22427; Fri, 28 Oct 94 17:05:24 -0400
Message-Id: <9410282105.AA22427@coulomb.eng.ohio-state.edu>
To: DIY_EFI
Subject: Re: the diy-sbc 
In-Reply-To: Your message of "Fri, 28 Oct 94 13:21:24 CDT."
             <m0r0wCf-000uIZC@twisto.eng.hou.compaq.com> 
Date: Fri, 28 Oct 94 17:05:24 -0400
From: John S Gwynne <jsg>
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI

--------

   In message <m0r0wCf-000uIZC@twisto.eng.hou.compaq.com> , you write:
 
| 1)  what is the circuitry connected to IC9 pin1?  Debounce for the switch?

The initial reset must be asserted for 100ms. It works but it can
be replaced by a "reset generator" with fewer external parts. See below...

| 2)  what are your pal equations?

appended to the end of this e-mail.

| Anyway, it seems complete, what are your plans for enhancements?  I mean on 
| this board, not plans for expansion boards...

1) ic10 and most of the discrete parts attached to it will be replaced with a
MAXIM "watch-dog/battery switch over/reset generator". I hope to order this
next week...

2) I need a few wait states for the external bus that will be on the
expansion board. Right now this should just be an equation change to ic11, but
I may add one connection between E1 and ic11.

3) In hind sight, I think ic13 and ic15 (the battery backed-up ram) should
be put on the expansion board and 2 128kx8 SRAM chips put on this board. 
Originally, I was going to put 0.5 or 1 Meg of DRAM (SIMMs) on the expansion
board, but this seems like too much over kill now. I intend to put 2 128kx8
SRAM chips on my expansion board.

4) A connection will be made between the reset generator and IC19 to ensure
that the battery backed-up RAM can not be selected during the first few
clock cycles of a power-on reset. 

5) I made the following pin swaps to minimize wire path lengths.
	IC7:
	(pin as shown on the schematics),(was changed to new pin number)
	2,9 3,8 4,7 5,6 6,5 7,4 8,3 9,2 18,11 17,12 16,13
	15,14 14,15 13,16 12,17 11,18

	IC2:
	11,17 13,15 15,13 17,11 9,3 7,5 5,7 3,9
	
	IC3:
	11,17 13,15 15,13 17,11 9,3 7,5 5,7 3,9
	
6) The interrupt priority encoder and heart-beat 100mS interrupt should be on
the cpu board to make it more stand-alone. But, (1) there are a limited
number of pins free on E1 for other external interrupts and (2) not a whole
lot of space left. Expect pins 23,24, and 25 of ic1 and pin 30 of ic17 to be
routed to E1 with maybe pull-up resistor for stand-alone mode.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
GAL equations follow (all GAL's are 15nS)
================ cut here =================
ic9 file

chip ic9 gal16v8a

;1      2       3       4       5       6       7       8       9       10
R1	nc	nc	nc	R	nc	nc	nc	nc	GND
nc	nc	nc	RESET1	W	nc	!RESET	!HALT	nc	VCC

equations

RESET = !R1
HALT = !R1
RESET.OE = !R1
HALT.OE = !R1
RESET1 = RESET.PIN
W = !R
================ cut here =================
ic11 file

chip ic11 gal16v8a

;1      2       3       4       5       6       7       8       9       10
CLK24	!AS	A23	A22	A21	NC	NC	NC	NC	GND
NC	NC	NC	NC	NC	CLK6	!DTACK	!VPA	CLK12	VCC

equations

CLK12 := !CLK12
CLK6 := !CLK6 & CLK12 | CLK6 & !CLK12
DTACK = AS & !A23 | AS & !A22 | AS & !A21
VPA = AS & A23 & A22 & A21
================ cut here =================
ic19 file

chip ic19 gal16v8a

;1      2       3       4       5       6       7       8       9       10
NC	!UDS	!LDS	!AS	A23	A22	A21	R	NC	 GND
NC	NC	NC	!U_RD	!U_WR	!U_CS	!HBRAM	!LBRAM	!EPRM	VCC

equations

EPRM = AS  &  R & !A23 & !A22 & !A21
LBRAM = LDS &      !A23 & !A22 &  A21
HBRAM = UDS &      !A23 & !A22 &  A21
U_CS  =            !A23 &  A22 & !A21
U_WR  = LDS & !R & !A23 &  A22 & !A21
U_RD  = LDS &  R & !A23 &  A22 & !A21
================ cut here =================




                                       John S Gwynne
                                          Gwynne.1@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
-------------------------------------------------------------------------------

From owner-diy_efi  Sat Oct 29 02:50:18 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA23321; Sat, 29 Oct 94 02:50:18 GMT
Received: from eigen.ee.ualberta.ca by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA23316; Fri, 28 Oct 94 22:50:15 -0400
Message-Id: <9410290250.AA23316@coulomb.eng.ohio-state.edu>
Received: by eigen.ee.ualberta.ca
	(1.37.109.4/15.6) id AA14566; Fri, 28 Oct 94 20:49:59 -0600
From: Dale Ulan <ulan@ee.ualberta.ca>
Subject: re: Re: EGO clogging. (long)
To: DIY_EFI
Date: Fri, 28 Oct 94 20:49:58 MDT
In-Reply-To: <m0r0uKU-000uITC@twisto.eng.hou.compaq.com>; from "Steve=Ravet%Prj=Eng%PCPD=Hou@bangate.compaq.com" at Oct 28, 94 10:47 am
Mailer: Elm [revision: 70.85]
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI

> EGO=oxygen sensor
> UEGO=?????
  universal exhaust gas oxygen sensor. It is capable of sensing what
  the relative mixuture is, not just whether it's lean or rich of
  stoich.

> I thought the O2 sensor generated voltage depending on amount of O2 in the 
> exhaust.  sort of an exponential curve with stoich somewhere around where it 
> starts to rise.  Does it need to be driven externally after warm-up?

It has an 'S' type curve, where the voltage is close to 0 when the exhaust
contains exhaust from completely burned lean mixture.
In a rich mixture, the sensor reads approximately 800 mV. Right around
stoich, the sensor goes into its linear region. The height and slope of
this linear region is highly dependant on temperature, even more so
than on the mixture...

                  +----------- 800 mV
                 +
                 +
                 +
100 mV----------+

  LEAN    14.8  14.7  14.6

> I thought it already read out the A/F ratio.  What exactly are you saying 
> above?  Is the "pump" a constant current source?

The 'pump' is fed by a current source. The amount of current fed through
the 'pump' cell controls when the sensing element does the above...
for example, by feeding 5 mA into the pump cell, the trip point looks the
same (more or less), but it is shifted... I'd suggest reading SAE paper
860408, by Seikoo Suzuki, Takao Sasayama, Masayuki Miki, Minoru Ohsuga,
Shigeru Tanaka, Sadayasu Ueno, and Norio Ichikawa of Hitachi.
Also, papers 841250, 850378, and 850379 contain material on this topic.


                    +-------- 800 mV
                   +
                   +
100 mV -----------+
	 10.7    10.6   10.5


<long clip deleted>

That's what everybody thought, too...
About 3 or 4 years ago, a few people from the EPA wrote an SAE
paper on the subject of oxygen sensors. My copy of the paper
is at school, so I can't quote the names or give you the SAE
paper number. But I can summarize it, because I was suprised, too.

The EPA was going to do a study of oxygen sensor aging and break-in
periods, and quantify how this affects exhaust emissions. They
built a test setup with a heater (which would heat up the sensor and
the gas it was exposed to), and a valving system that would allow them
to purge the test system with nitrogen gas, and then give samples
of other gasses.

What they found surprised them... The most obvious test is to see what
temperature was required for the sensor to sense oxygen. So they
cranked up the O2 flow, and started heating. The O2 sensor started to
respond at about 800 or 900 degrees C. No exhaust system operates that
under normal road-load conditions.

At this point, they decided that their study should concentrate on this
lack of O2 sensor activity. What they discovered was that the O2 sensor
would respond to carbon monoxide and hydrogen. At normal operating
temperatures, they concluded that the O2 sensor is not capable of
sensing oxygen at all. Few people seem to have read this paper, though,
so most people out there think that the oxygen sensor actually senses
oxygen in a vehicle. It *can* sense oxygen, but it'll have to be
glowing pretty bright to do it.

I would suggest going to your local technical library and finding
this SAE article. It will be in one of the annual article abstract
books, somewhere between 1989 and 1993, and may be present in either
the big thick SAE publication hardcovers, and/or in 'Sensors and
Actuators', an SAE special publication series.

I haven't seen any papers arguing against their conclusions,
but if there are, I'll hopefully eventually find them and read them.


-Dale

From owner-diy_efi  Tue Nov  1 15:23:53 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA05274; Tue, 1 Nov 94 15:23:53 GMT
Received: from localhost.eng.ohio-state.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA05269; Tue, 1 Nov 94 10:23:51 -0500
Message-Id: <9411011523.AA05269@coulomb.eng.ohio-state.edu>
To: DIY_EFI
Subject: libgcc for the 68000
Date: Tue, 01 Nov 94 10:23:51 -0500
From: John S Gwynne <jsg>
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI

--------

I  placed the file libgcc_m68000 on this mail server today. It is the
original distribution of what I used. I have a couple of these,
but this one seemed to be organized the best.


                                       John S Gwynne
                                          Gwynne.1@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
-------------------------------------------------------------------------------



From owner-diy_efi  Tue Nov  1 17:39:39 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA06305; Tue, 1 Nov 94 17:39:39 GMT
Received: from SGI.COM by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA06300; Tue, 1 Nov 94 12:39:37 -0500
Received: from zcar.engr.sgi.com by sgi.sgi.com via ESMTP (940627.SGI.8.6.9/910110.SGI)
	for <@sgi.sgi.com:DIY_EFI@coulomb.eng.ohio-state.edu> id JAA03142; Tue, 1 Nov 1994 09:39:35 -0800
Received: by zcar.engr.sgi.com (940816.SGI.8.6.9/911001.SGI)
	for DIY_EFI@coulomb.eng.ohio-state.edu id JAA00765; Tue, 1 Nov 1994 09:42:45 -0800
Date: Tue, 1 Nov 1994 09:42:45 -0800
From: keng@zcar.engr.sgi.com (Ken Greenebaum)
Message-Id: <199411011742.JAA00765@zcar.engr.sgi.com>
To: DIY_EFI
Subject: Introduction
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI


Hi All,

Just now subscribed to the efi list and thought I would introduce myself.

I do library/os/systems level programming at Silicon Graphics and have
done a number of embedded dsp projects using both TI, and Motorola DSPs.
At home I design projects around antiquated but cheap and easy to wire wrap
8-bit microcontrollers, most often the 8051.  Often for home controll.
Most recently I have been programming the 8051 in C using Dave Dunfield's
compiler (which I ported to my unix box).

I have long been interested in engine control, but haven't been brave enough
to venture out on my own.  I commute by bicycle, but play w/a '71 240Z on
the weekends.  The Z would be my rolling test bed.  I would be most 
interested in starting with an ignition controller, possibly one with
knock sensors to dynamicaly adjust timing.

I am hoping that folks on this list are participating in a group design.
Possibly I can lend a hand, once brought up to speed...


								-Ken

From owner-diy_efi  Tue Nov  1 19:33:55 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA06831; Tue, 1 Nov 94 19:33:55 GMT
Received: from naitgate.nait.ab.ca by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA06826; Tue, 1 Nov 94 14:33:47 -0500
Received: by naitgate.nait.ab.ca (AIX 3.2/UCB 5.64/4.03)
          id AA21339; Tue, 1 Nov 1994 12:34:26 -0700
Date: Tue, 1 Nov 1994 12:34:25 -0700 (MST)
From: Grant Beattie <grantb@nait.ab.ca>
Subject: Let me introduce myself
To: DIY_EFI <DIY_EFI>
Message-Id: <Pine.3.89.9411011256.A26277-0100000@naitgate.nait.ab.ca>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI


I teach Motorola 68HC11 courses at a two-year technical school in 
Canada.  But on weekends I'm a kart racer who would like to add EFI and
data acquisition to my Briggs 5HP+ engine.  So far I've gotten as far as 
creating a data acquisition system that logs speed, therefore I have a 
long way to go!  Has anyone been down this road before?

GB

.-------------------------------------------------------------------------.
|  Grant Beattie              |   Internet:    grantb@nait.ab.ca          |
|  Computer Engineering Tech. |   Compuserve:  74547,30                   |
|  N.A.I.T. (Alberta, Canada) |   Voice:       403-471-8422               |
`-------------------------------------------------------------------------'


From owner-diy_efi  Wed Nov  2 00:17:19 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA08734; Wed, 2 Nov 94 00:17:19 GMT
Received: from naitgate.nait.ab.ca by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA08729; Tue, 1 Nov 94 19:17:15 -0500
Received: by naitgate.nait.ab.ca (AIX 3.2/UCB 5.64/4.03)
          id AA05252; Tue, 1 Nov 1994 17:18:03 -0700
Date: Tue, 1 Nov 1994 17:18:02 -0700 (MST)
From: Grant Beattie <grantb@nait.ab.ca>
Subject: The files...
To: DIY_EFI <DIY_EFI>
Message-Id: <Pine.3.89.9411011710.A27498-0100000@naitgate.nait.ab.ca>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI


Could someone let me know a little about the 68hc000 postscript files?  I 
am under the impression that it is a schematic of an EFI unit, but 400k 
bytes seems a *little* large for one schematic...

GB


From owner-diy_efi  Wed Nov  2 03:30:46 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA10220; Wed, 2 Nov 94 03:30:46 GMT
Received: from shiva.trl.OZ.AU by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA10215; Tue, 1 Nov 94 22:30:39 -0500
Received: by shiva.trl.OZ.AU id AA22212
  (5.65c/IDA-1.4.4 for DIY_EFI@coulomb.eng.ohio-state.edu); Wed, 2 Nov 1994 14:16:45 +1100
From: Craig Pugsley <c.pugsley@trl.oz.au>
Message-Id: <199411020316.AA22212@shiva.trl.OZ.AU>
Subject: Found.. 8051 FAQ.
To: DIY_EFI
Date: Wed, 2 Nov 1994 14:16:44 +1100 (EST)
X-Mailer: ELM [version 2.4 PL20]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1711      
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI

Hi there,

While the general concensus of this list is to use a 68xxx processor,
I'm using an 8051 as i/ I've used it before ii/ the 8xC552 has all of
the features required for this sort of project iii/ I've got an 8051
based development kit.

Anyway, I was trying to find assemblers/compilers for free and was
pointed to the comp.sys.intel newsgroups "8051 faq" as a source of
FTPable stuff. I haven't read it in detail, but it looks like there's a
lot of nice stuff out there.

Here's a quick list of where it's available:

Host plaza.aarnet.edu.au
    Location: /usenet/FAQs/comp.sys.intel
Host freebsd.cdrom.com
    Location: /.9/rtfm/comp.sys.intel
Host ftp.uni-stuttgart.de
    Location: /pub/doc/faq/comp.sys.intel
Host ftp.rz.uni-ulm.de
    Location: /pub/news-faq/comp.sys.intel
Host rimbaud.polytechnique.fr
    Location: /pub/faq-by-newsgroup/comp/comp.sys.intel

Now, back to an EFI question.

This is what I plan to do to get it running:

I'm going to just use a "3-D" look-up table, with RPM on one axis and
load on the other (load being just engine vacuum level for starters).
The location pointed to by RPM and load will be a number that is used
for a counter that turns on the injectors:

I plan to use 4 bits (=16 points) for the RPM axis and 5 bits (=32
points) for the load axis, giving a total of 512 settings - (Co
incidentally the same way that other well known controllers are laid
out).

Once I get an engine to run then I'll start thinking about an
accelerator pump, cold starting, over-run cut off, altitude compensation,
EGO correction etc etc etc.

Does the 3D table sound described above sound like a reasonable
implementation? Has anyone tried something like this before?

Craig.

From owner-diy_efi  Wed Nov  2 04:16:13 1994
Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI)
	 id AA10314; Wed, 2 Nov 94 04:16:13 GMT
Received: from localhost.eng.ohio-state.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI)
	for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000        -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s        -r DIY_EFI diy_efi-outgoing id AA10309; Tue, 1 Nov 94 23:16:11 -0500
Message-Id: <9411020416.AA10309@coulomb.eng.ohio-state.edu>
To: DIY_EFI
Subject: Re: The files... 
In-Reply-To: Your message of "Tue, 01 Nov 94 17:18:02 MST."
             <Pine.3.89.9411011710.A27498-0100000@naitgate.nait.ab.ca> 
Date: Tue, 01 Nov 94 23:16:11 -0500
From: John S Gwynne <jsg>
Sender: owner-diy_efi
Precedence: bulk
Reply-To: DIY_EFI

--------

   In message <Pine.3.89.9411011710.A27498-0100000@naitgate.nait.ab.ca> , you w
rite:
 
| Could someone let me know a little about the 68hc000 postscript files?  I 
| am under the impression that it is a schematic of an EFI unit, but 400k 
| bytes seems a *little* large for one schematic...


   Large? Just wait till version 1.0 comes out next month :). The ps
file is indeed a schematic, but not a complete controller yet. The
file prints five pages that, when taped together, yield a D-sized
drawing of the CPU portion of what will be a controller.  For more
information, check-out the DIY_EFI's WWW server at

http://www.cpsc.ucalgary.ca/~fridman/diy_efi

There you will find the schematic, a couple of photos, and a
description. In short, this 4"x6" board is a complete single board
computer that has been tailored for EFI control. In the next few
months, a second expansion board will be added to support the EFI
functions.

This project represent the first controller to be shared in this forum
and should not be viewed as more than that (although, I do encourage
people to build it and HELP with its development :) ).  It is my hope
that those who do build something (**anything**) share it with this
group so that the rest of us may learn and benefit from your
experience. I have chosen to work with the 68000 since it is the
cheapest entry into the m68k family that opens the door to a great
deal of GNU software (gcc, gas, binary utilities, glibc, gdb,...) and
the RTEMS kernel. I encourage others to work with the CPU of their
choice, and hopefully we can all share information on interfacing and
control algorithms.


                                       John S Gwynne
                                          Gwynne.1@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
-------------------------------------------------------------------------------


