Testing Methodology

A project log for Voyage 200 Upgrades

Following up with nearly a decade old thread about overclocking TI's V200 with a bit of a twist

Michael O'BrienMichael O'Brien 02/08/2015 at 22:150 Comments

The new RAM is in place and the V200 is operating just fine; no reason why it shouldn't. I'm not worried so much about the viability of the RAM, though this removed one more variable to go wrong with the overclock. That said, there aren't a whole lot of tools to testing the hardware of TI's 68K calculators. From the limited programming in TIGCC that I've done, there are a few types of tests that will 'stress' the different components of the hardware: RAM, CPU, FLASH. As such, I've come up with a rudimentary list of tests.Before I get there, I need to measure a few other clocks: input clock on the NOR FLASH, clock for the serial data link. I do not know if these clocks are proportional to the RC oscillator or the MC68K system oscillator. If they are, its possible that overclocking can break their functionality. Anyhow, the tests will be conducted in the following order:

  1. Boot from reset
  2. Plot sin (x) and cos (x) with zoom fit function
  3. Run tibench and compare against oscilloscope
  4. Run an md5sum on a file, send to calculator, copy back and run md5sum again
    • Repeat for an Archived file
    • Repeat for a FlashApp
  5. Archive and unarchive a 64 KiB file until a garbage collection is forced twice
  6. Test execution of grayscale programs using the FAT engine
  7. Test execution of Space Dementia II which is a full 3D engine
  8. Test display of 8-level grayscale images with PicView
  9. Test file compression utility
  10. Load an fresh OS to the calculator using TI-Connect and a SilverLink cable