home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dsp
- Path: sparky!uunet!ftpbox!mothost!white!rtsg.mot.com!lido16!wiegand
- From: wiegand@rtsg.mot.com (Robert Wiegand)
- Subject: Re: DSP56000 memory
- Message-ID: <wiegand.715639282@lido16>
- Sender: news@rtsg.mot.com
- Nntp-Posting-Host: lido16
- Reply-To: motcid!wiegand@uunet.uu.net
- Organization: Motorola Inc., Cellular Infrastructure Group
- References: <1992Sep4.111051.29113@bernina.ethz.ch>
- Date: Fri, 4 Sep 1992 20:41:22 GMT
- Lines: 39
-
- stettbac@isibee5 (Juerg Stettbacher) writes:
-
-
- >Hello world
-
- >The DSP56001 has 3 memory spaces (X, Y and P).
- >X and Y are data memory spaces. Their sizes depend on
- >the particular application. P holds the program.
-
- >Question: What's a reasonable size for program memory P.
- >(Common DSP applications with monitor for stand alone.
- >Software development in C and assembler).
-
- >Any suggestions?
-
-
- >Thanks
- >juerg at ethz switzerland
-
- The program size will also depend on your application.
- I would suggest 8K x 24 as a minimum size for program memory.
- 8K x 8 chips are common and not too expensive. 3 parts will give you
- the 8K x 24 program memory.
- I also believe Motorola makes a 8K x 24 part.
-
- If your application will be large you could go to 32K x 24 by using
- three 32K x 8 parts. This is somewhat more expensive, but still not
- too bad.
-
- It is also possible to use the same parts for X, Y and P memory.
- You need a fast address decoder to do this, but it saves on memory
- chips.
-
-
- --
- ------------------------------------------------------------------------------
- Robert Wiegand - Motorola Inc.
- uunet!motcid!wiegand
- Disclamer: I didn't do it - I was somewhere else at the time.
-