Mark has been running my "kromtest" program (ie. replaced the KROM bios chip on the SFC-Box mainboard by the kromtest EPROM)!
21 screenshots showing the kromtest v1.0 results can be found here:
kromtest10.zip [281.2 KiB]
Downloaded 301 times
(aside from the screenshots, the original test program v1.0 is also included for reference).
The cpu tests are showing invalid opcode traps, "-"=passed, "0"=trapped with UFO=0, "."=skipped/not tested. The interesting part is that the HD64180 is actually trapping all undocumented opcodes, even those that are more or less commonly used on Z80 CPUs, ie. the HD64180 doesn't support accessing IX/IY 16bit registers as 8bit fragments (IXH,IXL,IYH,IYL), doesn't support "SLL" opcode, nor useless opcode mirrors (like alternate NEG/IM/RETN/RETI/NOP mirrors).
Please ignore the "DDCBxx" test page, it's rather meaningless; I wanted to test DDCBNNxx, not DDCBxx, but I got that wrong :-)
The TEST "VBLANK" TIME test... I've no clue what the results mean. It was intended to measure timings of a bit that was assumed to be a VBLANK (or maybe VSYNC) signal, but somehow the timings don't seem to match either one...
For a 60Hz signal I would have expected 8 times bigger values (although the HD64180 waitstates and refresh cycles might slowdown the CPU, but even then the values should be around 4 times bigger as they are). And transformed to 262 total scanlines, the "duty" would be around 10 scanlines, which also doesn't match typical vblank or vsync periods.
The WATCHDOG is trapping in both cases (when leaving the watchdog bit stuck set to "1", or stuck set to "0"). Meaning that... watchdog reset should occur either on 1-to-0 or 0-to-1 transitions (or both)... or on repeated writes without transitions. That isn't quite clear yet, anyways it's confirmed that the bit is really having a watchdog function.
The 00000ABAh value gives some hint on the timeout, but it's also affected by memory waitstates and refresh cycles, so it'd be a bit difficult to convert that value to an actual "time" value counted in cycles or seconds.
OSD Tests are showing the full charset, the resolution isn't yet good enough for dumping it, but at least one can see japanese characters, special volume/tape/am/pm/no/arrow symbols, and the normal ASCII characters (which lack some chars like "@|\").
Char Sizes test reveals which bits do control horizontal and vertical zoom. Also note that, after vertical zoom, the next line is skipped, eg. after zoom in Line 3, next line is Line 5 (and Line 4 isn't displayed).
The Special Styles screen reveals a blink-feature, the abitlity to use the "unknown color" as per-character background color, and some complicated bit-combinations that do enable using the "background color" either as "outline" or as "solid" background.
The blink interval isn't visible in the screenshots (obviously), but it can be seen in the original test video http://www.youtube.com/watch?v=nDwZ62e1FdQ
Next kromtest version will include a higher resoltion font-viewer with chars drawn on a chessboard pattern. The missing DDCBNNxx opcode trap test, and verification of (un-)expected traps.