Welcome, Guest. Please login or register.

Author Topic: Warpengine 4040 in a 3000D  (Read 5525 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: Warpengine 4040 in a 3000D
« on: June 22, 2012, 09:54:19 AM »
Accelerator SCSI always requires running the INT2 signal from a CIA (or wherever it's present) to the CPU slot as it isn't present on the 3000 yet. Actually it's not a bug, rather a later pinout change.
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: Warpengine 4040 in a 3000D
« Reply #1 on: June 23, 2012, 10:06:42 AM »
Static column RAM/mode is for '030 burst mode only, the '040 bursts differently and SC mode will be disabled (=there is no difference between SC and FP RAM for '040+).

AFAIR, there's a problem with an '060 and SC RAM with Kick 2.0 (it fails to deactivate SC mode) but you can easily sabotage SC mode by swapping in a single FP chip into the first bank (Kickstart just tests the first bank only).

Leaving the slow mobo RAM in doesn't hurt because the faster accelerator RAM gets higher priority and is always allocated first. Only when it's depleted mobo RAM will get used.
« Last Edit: June 23, 2012, 10:11:14 AM by Zac67 »
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: Warpengine 4040 in a 3000D
« Reply #2 on: June 24, 2012, 08:46:09 PM »
Quote
Zac, i could be wrong on this  but if memory serves it was the DMAC2 chip that had the problem deactivating sc mode when using a 040 and why you needed fast page in bank one.


Hmm... I think I recall seeing Ramsey setup code in Kickstart's bonus area - but I may be misremembering (we're all older now). Don't think DMAC has anything to do with it, but a newer Ramsey calls for a DMAC 4 anyway.