Re: DRAM refresh rates

Article View: alt.lang.asm

Article #158

#158

From: John West
Date: Wed, 13 Jan 1993 05:35

14 lines
1107 bytes

jt@fuw.edu.pl (Jerzy Tarasiuk) writes:

>It is possible to write a program testing DRAM refresh assuming we have
>some memory which will not be destroyed when refresh discontinues to
>work. I suppose video RAM can be used for this purpose.

It isn't just losing the program... ANY access to the DRAM will refresh part
of it, destroying the test. It wasn't uncommon in the past to arrange memory
so adjacent bytes were in different rows, so just executing code would 
(hopefully) refresh all of memory. Just watch out for those tight loops.

John West
--
For the humour impaired: Insert a :-) after every third word

Technical Details

Message-ID: <1j09m4INNdmc@uniwa.uwa.edu.au>

Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!uniwa!john

References: <1992Dec29.012957.14287@cbfsb.cb.att.com> <1hso9hINNeks@sbusol.rz.uni-sb.de> <JT.93Jan12204346@fizyk1.fuw.edu.pl>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!uniwa!john
From: john@gu.uwa.edu.au (John West)
Newsgroups: alt.lang.asm,comp.sys.ibm.pc.hardware
Subject: Re: DRAM refresh rates
Date: 13 Jan 1993 05:35:00 GMT
Organization: The University of Western Australia
Lines: 14
Message-ID: <1j09m4INNdmc@uniwa.uwa.edu.au>
References: <1992Dec29.012957.14287@cbfsb.cb.att.com> <1hso9hINNeks@sbusol.rz.uni-sb.de> <JT.93Jan12204346@fizyk1.fuw.edu.pl>
NNTP-Posting-Host: mackerel.gu.uwa.edu.au

Reply to Parent Message