Welcome, Guest. Please login or register.

Author Topic: Fastest running CyberStorm Mk III?  (Read 10657 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline matthey

  • Hero Member
  • *****
  • Join Date: Aug 2007
  • Posts: 1294
    • Show all replies
Re: Fastest running CyberStorm Mk III?
« on: February 14, 2010, 04:56:18 PM »
I have a CSMK3 with 68060@75MHz. I use 50ns marked EDO SIMMs. I have a very fast and stable system at this speed. I do not overclock the motherboard or SCSI, just the 68060 with a 2nd oscillator. I changed a jumper to do this. It's described here...

http://members.iinet.net.au/~davem2/overclock/csppc.html

I tried 80MHz and the system booted but was not completely stable. I didn't think the problem was the 68060 (newest mask). It could have been the ram being too slow but I doubt that even. I can set the memory speed up in the CS boot menu at 75 MHz but it didn't help to have it at the slower speed at 80 MHz. I figured the limit of the CS circuitry had been reached. Good luck going farther and let me know if you have any luck.
 

Offline matthey

  • Hero Member
  • *****
  • Join Date: Aug 2007
  • Posts: 1294
    • Show all replies
Re: Fastest running CyberStorm Mk III?
« Reply #1 on: February 15, 2010, 10:45:45 PM »
Quote from: johnklos;543323
I suppose I wasn't thinking that I could damage the programmable logic - I didn't realize that it depends on the m68060 clock. If the programmable logic is a limiting factor and can be damaged from overclocking, then I will not be trying to clock this any faster - as a matter of fact, I'm going to bring it down.

...

75 MHz is more than fast enough. Thanks!


The right way to do the overclocking with the CSMK3 is to change the jumper and add a 2nd oscillator. This overclocks the 68060 only. This should be safe enough as this should be the way Phase5 would have supported faster 68060's. 75MHz is very fast considering the memory speeds up too and it was already faster than most other 68060 accelerators. Plus we have ultra wide SCSI. I wouldn't trade for an Apollo 68060@90MHz with half speed memory and broken SCSI. If I want a faster 68060, I'll wait for the Natami with 68060.
 

Offline matthey

  • Hero Member
  • *****
  • Join Date: Aug 2007
  • Posts: 1294
    • Show all replies
Re: Fastest running CyberStorm Mk III?
« Reply #2 on: February 17, 2010, 10:28:26 AM »
Quote from: bernd_afa;543507
if here are users with overclocked 68k cards, i like to see how fast then SDL games at 640*480* 16 bit resolution can run.

I upload a defendguin with framerate display

it work on default in window.but for fastest speed it should start from shell with the defendguin -f

this work in fullscreen

Here is the link for download, can copy to ram and run.note music should stay off

http://www.daten-transport.de/?id=nfvHR9gTPYGw


I got 20fps most of the time. It flashed a higher or lower fps from time to time but it wasn't displayed long enough to read it. I had AWeb & Genesis going in the background and my memory was probably pretty well fragmented. I decompressed to ram and did a lot of compiles and disassembles first. The speed seamed fast and responsive but the gfx were messed up. The foreground objects were multi-colored. The background was fine.
 

Offline matthey

  • Hero Member
  • *****
  • Join Date: Aug 2007
  • Posts: 1294
    • Show all replies
Re: Fastest running CyberStorm Mk III?
« Reply #3 on: February 17, 2010, 11:15:08 PM »
Quote from: delshay;543640
err what is the speed of your processor(s) and what card do you have this would help if we are doing benchmark.

do you own a apollo @90Mhz?


Nope. Just a CSMK3 with 68060@75MHz, 50ns SIMMs running with the fastest memory settings of the CS, Mediator 3000T/4000T with Voodoo4 and AmigaOS 3.9 with updates in a 3000T.
 

Offline matthey

  • Hero Member
  • *****
  • Join Date: Aug 2007
  • Posts: 1294
    • Show all replies
Re: Fastest running CyberStorm Mk III?
« Reply #4 on: February 18, 2010, 09:21:13 PM »
@bernd
The Voodoo4 supports most every gfx mode but the big endian modes have problems with the colors of some objects. This is an Elbox bug for a long time and they don't seem too enthusiastic about fixing. Having big endian and small endian modes open at the same time can cause gfx corruption according to Elbox. Elbox recommends using little endian modes. Did your demo open in big endian mode? That would explain why it ran so fast too.
« Last Edit: February 18, 2010, 11:11:33 PM by matthey »