I've started a new thread rather than hijack RaveN 's here:
http://www.ukvac.com/forum/raspberry-pi-arcade-project_topic333310_post789507.html?KW=#789507
Today I've made some good progress with my tester board project. I made a proper PCB a few weeks ago and have been writing some better code to do tests on a target game board.
This time I'm plugged into a working Atari Space Duel PCB rather than the faulty bootleg Asteroids I was using before.
I've been having trouble with getting reliable read/writes to the target game board though, finally solved today by simply increasing the 5V to actually be 5V rather than the 4.85V it has been. I was running from a fixed 5V supply, but it only manages 4.85V on the game itself across the farthest chips.
I have written some vector instruction tests for the Space Duel to test the vector generator. Some simple tests like HALT and the jumps and jumps to subroutine worked fine, but the actual draw vector instruction would not trigger a VCTR state and no vectors were drawn. After increasing the voltage a little it now does properly draw.
If I put back the real 6502A into the board it works fine, even at the lower 4.85V, so this tells me (I think) that my tester is too tight on some read/write timing somewhere.
So now it will do some vector tests, continuous RAM tests and ROM checksums for both 16 bit add checksums and also Adler CRC32 checksums the same as ROMIdent uses.
Below are some photos of it hooked up to my scope, but unfortunately it's a new fangled digital one so awful when it's in XY mode compared to a real analogue scope.
The photos show the tester in 6502 emulation mode, running the original Space Duel ROMs while the game is in test mode, you can make out the screen test patterns though they are not blanked like they would be on a real vector monitor.
In this mode my tester board is emulating a 6502, the Space Duel ROMs and the 1K of RAM at address 0x0000, so I could remove those chips from the game and it would still run.
Mitchell Gant2013-08-18 08:56:31
http://www.ukvac.com/forum/raspberry-pi-arcade-project_topic333310_post789507.html?KW=#789507
Today I've made some good progress with my tester board project. I made a proper PCB a few weeks ago and have been writing some better code to do tests on a target game board.
This time I'm plugged into a working Atari Space Duel PCB rather than the faulty bootleg Asteroids I was using before.
I've been having trouble with getting reliable read/writes to the target game board though, finally solved today by simply increasing the 5V to actually be 5V rather than the 4.85V it has been. I was running from a fixed 5V supply, but it only manages 4.85V on the game itself across the farthest chips.
I have written some vector instruction tests for the Space Duel to test the vector generator. Some simple tests like HALT and the jumps and jumps to subroutine worked fine, but the actual draw vector instruction would not trigger a VCTR state and no vectors were drawn. After increasing the voltage a little it now does properly draw.
If I put back the real 6502A into the board it works fine, even at the lower 4.85V, so this tells me (I think) that my tester is too tight on some read/write timing somewhere.
So now it will do some vector tests, continuous RAM tests and ROM checksums for both 16 bit add checksums and also Adler CRC32 checksums the same as ROMIdent uses.
Below are some photos of it hooked up to my scope, but unfortunately it's a new fangled digital one so awful when it's in XY mode compared to a real analogue scope.
The photos show the tester in 6502 emulation mode, running the original Space Duel ROMs while the game is in test mode, you can make out the screen test patterns though they are not blanked like they would be on a real vector monitor.
In this mode my tester board is emulating a 6502, the Space Duel ROMs and the 1K of RAM at address 0x0000, so I could remove those chips from the game and it would still run.
Mitchell Gant2013-08-18 08:56:31