[comp.sys.amiga.hardware] SRAM and BURST mode on 3000

dalbec@sakura.ucdavis.edu (Gabe Dalbec) (02/07/91)

How do I turn on static colum mode and burst mode for my A3000.
I have setcpu but it doesn't seem to do anything.  I also have
setramsey from Fred Fish, but it just locks the computer.  What is
the official way to tell the A3000 that you have SRAM?

I thought that is was a jumper that the dealer would take care of, but
setramsey and setcpu both say the BURST and Static-column mode are
deafult to off.

thanks

*************************************************************************
*                             |                                         *
* Gabe Dalbec                 |    >screw you                           *
* Univ. or Calif. Davis       |    Unknown command "screw"              *
* Computer Science Engr.      |    >_                                   *
* dalbec@sakura.ucdavis.edu   |                                         *
*                             |                                         *
*************************************************************************

bryce@cbmvax.commodore.com (Bryce Nesbitt) (02/09/91)

In article <> dalbec@sakura.ucdavis.edu (Gabe Dalbec) writes:
>How do I turn on static colum mode and burst mode for my A3000.

The OS detects static column chips, and enables burst mode automatically.
There are several "turn on SCRAM" programs out there.  If they crash
your machine, you probably don't have properly working SCRAMs.

-- 
|\_/|  . "ACK!, NAK!, EOT!, SOH!"  "Lawyers: America's untapped export market."
{X o} .     Bryce Nesbitt, Operating Systems Group, Commodore-Amiga, Inc.
 (")        BIX: bnesbitt
  U	    USENET: bryce@commodore.COM -or- uunet!cbmvax!bryce

wendell@medsys.uucp (Wendell Dingus) (02/11/91)

bryce@cbmvax.commodore.com (Bryce Nesbitt) writes:

>In article <> dalbec@sakura.ucdavis.edu (Gabe Dalbec) writes:
>>How do I turn on static colum mode and burst mode for my A3000.

>The OS detects static column chips, and enables burst mode automatically.
>There are several "turn on SCRAM" programs out there.  If they crash
>your machine, you probably don't have properly working SCRAMs.

Ok, why after a cold boot does SetRamsey tell me that burst mode is on, but
static column, and Burst Wrap mode are off. I can turn them on and the 
machine works fine, and gets a few points higher in most benchmarking
programs with these modes on. Why don't they stay on? They seem to stay
as set after a warm boot. 
Configuration is 2 megs chip, 3 megs 256Kx4 SCRAMS (fast). 

-----
Wendell Dingus
...uunet!medsys!wendell

daveh@cbmvax.commodore.com (Dave Haynie) (02/13/91)

In article <1991Feb11.015011.621@medsys.uucp> wendell@medsys.uucp (Wendell Dingus) writes:
>bryce@cbmvax.commodore.com (Bryce Nesbitt) writes:

>>In article <> dalbec@sakura.ucdavis.edu (Gabe Dalbec) writes:
>>>How do I turn on static colum mode and burst mode for my A3000.

>>The OS detects static column chips, and enables burst mode automatically.
>>There are several "turn on SCRAM" programs out there.  If they crash
>>your machine, you probably don't have properly working SCRAMs.

>Ok, why after a cold boot does SetRamsey tell me that burst mode is on, but
>static column, and Burst Wrap mode are off. I can turn them on and the 
>machine works fine, and gets a few points higher in most benchmarking
>programs with these modes on. Why don't they stay on? They seem to stay
>as set after a warm boot. 

They don't stay on because you don't want them on, probably.  The OS folks,
like Bryce, have done testing to find out which parameters, both in RAMSEY
and 68030 cache control, yield the best performance.  Not in the reasonably
silly benchmark programs around, but in actual test of representative code.
Even Dhrystone 2.x will show that page-detect mode (what SetRAMSEY calls
static column mode) is at best a draw, and sometimes a loss, in most programs.
Plus, it has a potential conflict with hard disk DMA.  Apparently, SetRAMSEY
was written early in the testing periods of the A3000, before the OS knew
the right things to do.  A proper utility would at least check the version of
the RAMSEY and refuse to set up page-detect mode in the current system.  Both
page-detect and burst modes in RAMSEY are static column memory modes.

>Wendell Dingus


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"What works for me might work for you"	-Jimmy Buffett

don@brahms.udel.edu (Donald R Lloyd) (02/13/91)

     When I first run SetRamsey, it indicates that static, burst, and wrap are
all off, despite the fact that I've got 2M of 256x4 SCRAMS inside (the DIPs've
been moved over to the chip RAM area).  Other postings here have indicated that
It should be indicating that static mode is on.  Any idea what my problem might
be?  Setramsey does seem to turn static mode on without complaining, so I
assume (read hope, pray) that the chips themselves aren't the problem.

-- 
  Gibberish             Publications Editor, AmigaNetwork 
  is spoken             Contact don@brahms.udel.edu for more information.
    here.               DISCLAIMER:  It's all YOUR fault.

stefanb@cip-s02.informatik.rwth-aachen.de (Stefan Becker) (02/15/91)

daveh@cbmvax.commodore.com (Dave Haynie) writes:
>They don't stay on because you don't want them on, probably.  The OS folks,
>like Bryce, have done testing to find out which parameters, both in RAMSEY
>and 68030 cache control, yield the best performance.  Not in the reasonably
>silly benchmark programs around, but in actual test of representative code.
>Even Dhrystone 2.x will show that page-detect mode (what SetRAMSEY calls
>static column mode) is at best a draw, and sometimes a loss, in most programs.
>Plus, it has a potential conflict with hard disk DMA.  Apparently, SetRAMSEY

But why then pay the extra price for SCRAM????

	Stefan

Mail  : Stefan Becker, Holsteinstrasse 9, D-5100 Aachen  ///    Only
Phone : +49-241-505705   FIDO: 2:242/7.6    Germany     ///  Amiga makes
Domain: stefanb@informatik.rwth-aachen.de           \\\///  it possible..
Bang  : ..mcvax!unido!rwthinf!stefanb                \XX/  -->A3000/25<--

daveh@cbmvax.commodore.com (Dave Haynie) (02/19/91)

In article <stefanb.666561799@cip-s02> stefanb@cip-s02.informatik.rwth-aachen.de (Stefan Becker) writes:

>daveh@cbmvax.commodore.com (Dave Haynie) writes:
>>They don't stay on because you don't want them on, probably.  The OS folks,
>>like Bryce, have done testing to find out which parameters, both in RAMSEY
>>and 68030 cache control, yield the best performance.  

>But why then pay the extra price for SCRAM????

First of all, you shouldn't pay more for SCRAM, it costs the same to make as
PRAM.  C= certainly doesn't pay any extra.

Secondly, what's wrong with using burst mode, the way the OS sets things up.
This gives you a clear 10%-20% speedup with SCRAM, and virtually never causes
a speed loss.  You obviously want your system set up to run as fast as 
possible.  The silly benchmarks most people use will mislead you on this, the
operating system won't.

>Mail  : Stefan Becker, Holsteinstrasse 9, D-5100 Aachen  ///    Only


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"What works for me might work for you"	-Jimmy Buffett