Article View: comp.dsp
Article #713Re: Finding how much DSP56001 RAM is installed via program??
From: Bill Schottstaedt
Date: Wed, 26 Aug 1992 13:46
Date: Wed, 26 Aug 1992 13:46
10 lines
954 bytes
954 bytes
In article <17fb61INN572@agate.berkeley.edu> izumi@pinoko.berkeley.edu (Izumi Ohzawa) writes: > Failure on any one pattern should break the loop. > The program just doesn't exit the loop... I believe the program does not fail because the out-of-range NeXT DSP external memory addresses are mapped back onto lower addresses. For example, on an 8K dsp, an address like X:$B001 actually writes to X:1 (external, of course = $A001). This makes it harder to figure out how much memory is actually out there.
Technical Details
Message-ID:
<1992Aug26.134637.5838@leland.Stanford.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!leland.Stanford.EDU!newsReferences:
<17fb61INN572@agate.berkeley.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.dsp Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!leland.Stanford.EDU!news From: bil@cmn16.Stanford.EDU (Bill Schottstaedt) Subject: Re: Finding how much DSP56001 RAM is installed via program?? Message-ID: <1992Aug26.134637.5838@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: DSO, Stanford University References: <17fb61INN572@agate.berkeley.edu> Date: Wed, 26 Aug 92 13:46:37 GMT Lines: 10