Newsgroups: comp.robotics
Path: brunix!sgiblab!cs.uoregon.edu!news.uoregon.edu!netnews.nwnet.net!ns1.nodak.edu!plains.NoDak.edu!nanders
From: nanders@plains.NoDak.edu (Noel Anderson)
Subject: Re: HC11 - HC16 info
Sender: usenet@ns1.nodak.edu (Usenet login)
Message-ID: <CKAL0t.DED@ns1.nodak.edu>
Date: Thu, 27 Jan 1994 14:17:17 GMT
References: <2i7jqhINN2n3@nbc.ksu.ksu.edu>
Nntp-Posting-Host: plains.nodak.edu
Organization: North Dakota Higher Education Computing Network
Keywords: HC11, HC16, GCC
Lines: 42

In article <2i7jqhINN2n3@nbc.ksu.ksu.edu> chappy@nbc.ksu.ksu.edu (Doug R. Chapman) writes:
>
>We are currently working on communication between the HC16 and 
>the HC11's.  The HC16 will set an interupt line causing the proper HC11's
>to listen for communication.  We basically have 2 problems.

[ Stuff deleted to save bandwidth ]

>Basically we are looking for the follwing things:
>	Examples or information on communication code for
>	the HC11 HC16 or both.

You have several options.  Both processors have integrated synchronous
and asynchronous communication subsystems.  The asynchronous SCIs can
be connected to RS-485 drivers for a multi-drop network. The code needs
to listen for messages on the link, start talking in a free time, and listen
to itself so it can tell if a collision occurred with another message.

If the HC11s are slaves to the HC16, the HC16 can select a slave and
interact with it using the queued serial module. The HC11 would use the
synchronous SPI subsystem. If you can stand delay associated with  
polled or time multiplexed communication, I think this would be easier.

>	Either an inexpensive C compiler or even better a back
>	end for GCC to compile HC16 code.  Possibly a limited 
>	version that compiles to assembler code then use the
>	motorola assember.

If you haven't spent any compiler money yet, I'd recommend buying the
Dunfield compiler for the HC16 and then getting the Coactive Aesthetics port
of gcc or the icc compiler off the net for the HC11. Unfortuneately the
HC16 is not as compatible with the HC11 as one would hope at the
assembly language level so you are stuck getting two sets of tools.
We've had good experiences locally with
the Dunfield compilers for both the HC11 and HC16 and no experience with
the other two compilers I mentioned.


-- 
Noel W. Anderson                   nanders@plains.nodak.edu (Internet)
Asst Prof, Computer Engineering         "I speak for myself, not NDSU"
EE Dept, North Dakota State University         nanders@plains (BITNET)
