To content | To menu | To search

Checking CT60 stability

Whatever the frequency at which your 060 cpu is clocked, you may need to check the complete stability of the system. For doing so, you need to stress test everything simultaneously: bus, cpu, disk I/O and more. I choose to compile a program under MiNT, using gcc. Once the program is compiled, strip the binary and then run md5sum on it to check if the generated binary is the same as a working one.

With the CTPCI plugged, I found that my Rev5 cpu did not go so fast without causing problems. Here is the result of compiling Doom on my Falcon at different frequencies:

  • 60 MHz: a4573c8f268ff8081a8e321d1e93c704
  • 62 MHz: a4573c8f268ff8081a8e321d1e93c704
  • 64 MHz: a4573c8f268ff8081a8e321d1e93c704
  • 65 MHz: a4573c8f268ff8081a8e321d1e93c704
  • 66 MHz, run #1: 27f468c0d7846dc2a82ea47a77b14ec5
  • 66 MHz, run #2: 59f6fd718d352576a1872457d41a92e4

Before plugging the CTPCI, my cpu could run at 73MHz without problems. Just to be on the safe side, I now run at 64MHz.

Even if you have a Rev6 cpu, I highly recommend running a similar test. Your system may not be as stable as you think.