Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!galileo.berkeley.edu!jbuck
From: jbuck@galileo.berkeley.edu (Joe Buck)
Newsgroups: comp.arch
Subject: Re: On Chip Emulator
Keywords: TMS320C30, 96002 DSP chips
Message-ID: <36977@ucbvax.BERKELEY.EDU>
Date: 12 Jun 90 17:11:51 GMT
References: <9598@pt.cs.cmu.edu>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: jbuck@galileo.berkeley.edu (Joe Buck)
Lines: 20

In article <9598@pt.cs.cmu.edu>, lindsay@MATHOM.GANDALF.CS.CMU.EDU
(Donald Lindsay) writes:
|> There's a nifty new wrinkle in the new Motorola DSP, the 96002.
|> It contains what Motorola refers to as an on-chip emulator. The
|> "OnCE" has its own dedicated serial interface, and accepts commands
|> to set breakpoints, report on internal values, and so on.

This is not new.  Motorola's biggest competition for the 96002 is TI's
TMS320C30 DSP chip, which has been out for a while and already has
this feature.  I've used it extensively.

It's nice that it exists: you can provide a connector to the chip in
an embedded system and tell what's going on -- but it's inferior to
a real emulator, since you can only set breakpoints based on instruction
execution, you can't trace the data busses (I'm refering to the C30,
perhaps Motorola has done a better job).

--
Joe Buck
jbuck@ohm.berkeley.edu	 {uunet,ucbvax}!ohm.berkeley.edu!jbuck