home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dsp
- Path: sparky!uunet!mcsun!Germany.EU.net!mpifr-bonn.mpg.de!speckled.mpifr-bonn.mpg.de!mlelstv
- From: mlelstv@speckled.mpifr-bonn.mpg.de (Michael van Elst)
- Subject: Re: Finding how much DSP56001 RAM is installed via program??
- Message-ID: <1992Aug27.124324.19204@mpifr-bonn.mpg.de>
- Sender: news@mpifr-bonn.mpg.de
- Nntp-Posting-Host: speckled
- Organization: Max-Planck-Institut f"ur Radioastronomie
- References: <17fb61INN572@agate.berkeley.edu> <1992Aug26.134637.5838@leland.Stanford.EDU>
- Date: Thu, 27 Aug 1992 12:43:24 GMT
- Lines: 22
-
- In <1992Aug26.134637.5838@leland.Stanford.EDU> bil@cmn16.Stanford.EDU (Bill Schottstaedt) writes:
- >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.
-
- Yep, this is hard to find. If however you know what can be at the
- different addresses you can test for these shadowed RAM areas.
-
- My favourite RAM address checker fills the memory with a series of
- pseudo-random numbers and checks then against the same series. Any
- addressing fault or shadowing (happens when address lines are shorted as
- well) will most probably be detected. Of course you need a random
- number generator with a period larger than your memory :-)
-
- Regards,
- --
- Michael van Elst
- UUCP: universe!local-cluster!milky-way!sol!earth!uunet!unido!mpirbn!p554mve
- Internet: p554mve@mpirbn.mpifr-bonn.mpg.de
- "A potential Snark may lurk in every tree."
-