Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!ftpbox!mothost!motcid!svoboda
From: svoboda@motcid.UUCP (David Svoboda)
Newsgroups: comp.dsp
Subject: Re: TMS32031 - vs - Motorola56001, information requested
Message-ID: <4634@ash31.UUCP>
Date: 20 Mar 91 16:15:56 GMT
References: <1991Mar19.183918.6460@world.std.com>
Distribution: usa
Organization: Motorola Inc., Cellular Infrastructure Div., Arlington Heights, IL
Lines: 33

From article <1991Mar19.183918.6460@world.std.com>, by aep@world.std.com (Andrew E Page):
>    My preference is towards the C3x as well.  Much of my DSP expertise
> was cut with this device.  IN addition I like the feature of the dual
> busses in the same memory address space.  This saves a lot of hassles
> in coding and design.    

If I follow you right, I think you are mistaken on this about the 56K.
To save silicon, you can do as many of us do and use a single memory 
space addressed by X, Y, and P memory.

>     I'm not sure, but I do not think that the 56K supports the following 
> features that the C30 does:
> 
> 	a)  parallel instructions

Yes, it most definitely does.  By this I presume you mean allowing an ALU or
multiply-accumulate instruction in parallel with two memory reads or writes.
This it will do.

>         b)  serial ports (2 for the C30, 1 for the C31)

The DSP56001 has two serial ports and a host interface port for use in
communicating with a master processor.  One serial port is asynch, the
other synch.  The host port supports addressable, networked DSPs.

Note: I work for Motorola Cellular, not DSP Operations,
 so I only USE the 56K.

           Dave Svoboda, Motorola CID, RTSG, Arlington Heights, IL
               uucp => {uunet|mcdchg|att}!motcid!svoboda
  Don't feel paranoid; when we're out to get you, you won't have the vaguest 
    idea what's going on.  Corollary:  When you feel safe, that's when you 
                             should feel paranoid.