Hi all, in my quest to learn more about using these tools, I've actually come up with a problem, and could use a little explanation. I'm working on a liberator board, and was using the atari cat box. The first two tests in the liberator manual have you check address lines. Well those checked out good. Next was the Data lines. This is where things fell apart, and I'm not sure what I'm seeing. Punch in address 0000, and write AA check the D0-D7 lines going to the ls245 well half the incoming lines are the wrong state, and the output of the ls245 is non existent. Ie pins 2-9 have no output. So I hook up my fluke 9010a thinking there may be something wrong with the catbox, since this is the first time I've used it. Did the same basic setup wddis grounded, and Φ0 Φ2 shorted together. Do a write to 0000 with AA and use my logic probe to check. Same results. Am I to assume Bad memory at location 0000.?? _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
Kevin Moore wrote:
Hi all, in my quest to learn more about using these tools, I've actually come up with a problem, and could use a little explanation.
I'm working on a liberator board, and was using the atari cat box. The first two tests in the liberator manual have you check address lines. Well those checked out good. Next was the Data lines. This is where things fell apart, and I'm not sure what I'm seeing.
Punch in address 0000, and write AA check the D0-D7 lines going to the ls245 well half the incoming lines are the wrong state, and the output of the ls245 is non existent. Ie pins 2-9 have no output.
So I hook up my fluke 9010a thinking there may be something wrong with the catbox, since this is the first time I've used it. Did the same basic setup wddis grounded, and Φ0 Φ2 shorted together. Do a write to 0000 with AA and use my logic probe to check. Same results.
Am I to assume Bad memory at location 0000.??
Yes. Did you do the BUS Test first? That will show if any address or data lines are misbehaving. If BUS Test is OK, and you get this problem for RAM @ 0000h, then try the next RAM set - say @ 0800h or 1000h (if RAM present - check Memory Map). If other RAM all checks OK, or ANY RAM checks OK, then the RAM @ 0000h is certainly suspect. If the RAM is 4-bit, then which bits are locked will tell you which RAM to replace. John :-#)# -- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out" _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
Well I was following the seqeunce given in the manual, which is Address lines, then Data lines, then Ram etc.. I'll run the bus sigs now, and see what I get. Thanks, Kevin 2009/11/25 John Robertson <jrr@flippers.com>
Kevin Moore wrote:
Hi all, in my quest to learn more about using these tools, I've actually come up with a problem, and could use a little explanation.
I'm working on a liberator board, and was using the atari cat box. The first two tests in the liberator manual have you check address lines. Well those checked out good. Next was the Data lines. This is where things fell apart, and I'm not sure what I'm seeing.
Punch in address 0000, and write AA check the D0-D7 lines going to the ls245 well half the incoming lines are the wrong state, and the output of the ls245 is non existent. Ie pins 2-9 have no output.
So I hook up my fluke 9010a thinking there may be something wrong with the catbox, since this is the first time I've used it. Did the same basic setup wddis grounded, and Φ0 Φ2 shorted together. Do a write to 0000 with AA and use my logic probe to check. Same results.
Am I to assume Bad memory at location 0000.??
Yes.
Did you do the BUS Test first? That will show if any address or data lines are misbehaving.
If BUS Test is OK, and you get this problem for RAM @ 0000h, then try the next RAM set - say @ 0800h or 1000h (if RAM present - check Memory Map). If other RAM all checks OK, or ANY RAM checks OK, then the RAM @ 0000h is certainly suspect.
If the RAM is 4-bit, then which bits are locked will tell you which RAM to replace.
John :-#)#
-- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out"
_______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
I hooked up my fluke 9010 and did a bus check, I'm assuming that would be the easiest/fastest way to do a busy check on the board. Results came back good. Now fi I read your email correctly, you want me to use a different memory location. That makes sense. However the memory maps have always confused me a bit. The game is using AM9016EPC memory, which I'm having a problem finding a datasheet for atm. HEX R/W D7 D6 D5 D4 D3 D2 D2 D0 function 17 ---------+-----+------------------------+------------------------ 18 0000 D D D D D D D D XCOORD 19 0001 D D D D D D D D YCOORD 20 0002 D D D BIT MODE DATA 21 ---------+-----+------------------------+------------------------ 22 0003-033F D D D D D D D D Working RAM 23 0340-3D3F D D D D D D D D Screen RAM 24 3D40-3FFF D D D D D D D D Working RAM 25 ---------+-----+------------------------+------------------------ 26 4000-403F R D D D D D D D D EARD* read from non-volatile memory 27 ---------+-----+------------------------+------------------------ 28 5000 R D coin AUX (CTRLD* set low) 29 5000 R D coin LEFT (CTRLD* set low) 30 5000 R D coin RIGHT (CTRLD* set low) 31 5000 R D SLAM (CTRLD* set low) 32 5000 R D SPARE (CTRLD* set low) 33 5000 R D SPARE (CTRLD* set low) 34 5000 R D COCKTAIL (CTRLD* set low) 35 5000 R D SELF-TEST (CTRLD* set low) 36 5000 R D D D D HDIR (CTRLD* set high) 37 5000 R D D D D VDIR (CTRLD* set high) 38 ---------+-----+------------------------+------------------------ 39 5001 R D SHIELD 2 40 5001 R D SHIELD 1 41 5001 R D FIRE 2 42 5001 R D FIRE 1 43 5001 R D SPARE (CTRLD* set low) 44 5001 R D START 2 45 5001 R D START 1 46 5001 R D VBLANK 47 ---------+-----+------------------------+------------------------ 48 6000-600F W D D D D base_ram* 49 6200-621F W D D D D D D D D COLORAM* 50 6400 W INTACK* 51 6600 W D D D D EARCON 52 6800 W D D D D D D D D STARTLG (planet frame) 53 6A00 W WDOG* 54 ---------+-----+------------------------+------------------------ 55 6C00 W D START LED 1 56 6C01 W D START LED 2 57 6C02 W D TBSWP* 58 6C03 W D SPARE 59 6C04 W D CTRLD* 60 6C05 W D COINCNTRR 61 6C06 W D COINCNTRL 62 6C07 W D PLANET 63 ---------+-----+------------------------+------------------------ 64 6E00-6E3F W D D D D D D D D EARWR* 65 7000-701F D D D D D D D D IOS2* (Pokey 2) 66 7800-781F D D D D D D D D IOS1* (Pokey 1) 67 8000-EFFF R D D D D D D D D ROM 68 ----------------------------------------------------------------- 2009/11/25 Kevin Moore <talon.k@gmail.com>
Well I was following the seqeunce given in the manual, which is Address lines, then Data lines, then Ram etc..
I'll run the bus sigs now, and see what I get.
Thanks,
Kevin
2009/11/25 John Robertson <jrr@flippers.com>
Kevin Moore wrote:
Hi all, in my quest to learn more about using these tools, I've actually come up with a problem, and could use a little explanation.
I'm working on a liberator board, and was using the atari cat box. The first two tests in the liberator manual have you check address lines. Well those checked out good. Next was the Data lines. This is where things fell apart, and I'm not sure what I'm seeing.
Punch in address 0000, and write AA check the D0-D7 lines going to the ls245 well half the incoming lines are the wrong state, and the output of the ls245 is non existent. Ie pins 2-9 have no output.
So I hook up my fluke 9010a thinking there may be something wrong with the catbox, since this is the first time I've used it. Did the same basic setup wddis grounded, and Φ0 Φ2 shorted together. Do a write to 0000 with AA and use my logic probe to check. Same results.
Am I to assume Bad memory at location 0000.??
Yes.
Did you do the BUS Test first? That will show if any address or data lines are misbehaving.
If BUS Test is OK, and you get this problem for RAM @ 0000h, then try the next RAM set - say @ 0800h or 1000h (if RAM present - check Memory Map). If other RAM all checks OK, or ANY RAM checks OK, then the RAM @ 0000h is certainly suspect.
If the RAM is 4-bit, then which bits are locked will tell you which RAM to replace.
John :-#)#
-- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out"
_______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
Kevin Moore wrote:
I hooked up my fluke 9010 and did a bus check, I'm assuming that would be the easiest/fastest way to do a busy check on the board. Results came back good.
Now fi I read your email correctly, you want me to use a different memory location. That makes sense.
However the memory maps have always confused me a bit.
The game is using AM9016EPC memory, which I'm having a problem finding a datasheet for atm.
HEX R/W D7 D6 D5 D4 D3 D2 D2 D0 function
17 ---------+-----+------------------------+------------------------ 18 0000 D D D D D D D D XCOORD 19 0001 D D D D D D D D YCOORD
20 0002 D D D BIT MODE DATA 21 ---------+-----+------------------------+------------------------ 22 0003-033F D D D D D D D D Working RAM
23 0340-3D3F D D D D D D D D Screen RAM 24 3D40-3FFF D D D D D D D D Working RAM 25 ---------+-----+------------------------+------------------------
26 4000-403F R D D D D D D D D EARD* read from non-volatile memory 27 ---------+-----+------------------------+------------------------
28 5000 R D coin AUX (CTRLD* set low) 29 5000 R D coin LEFT (CTRLD* set low)
30 5000 R D coin RIGHT (CTRLD* set low) 31 5000 R D SLAM (CTRLD* set low)
32 5000 R D SPARE (CTRLD* set low) 33 5000 R D SPARE (CTRLD* set low)
34 5000 R D COCKTAIL (CTRLD* set low) 35 5000 R D SELF-TEST (CTRLD* set low)
36 5000 R D D D D HDIR (CTRLD* set high) 37 5000 R D D D D VDIR (CTRLD* set high) 38 ---------+-----+------------------------+------------------------
39 5001 R D SHIELD 2 40 5001 R D SHIELD 1 41 5001 R D FIRE 2
42 5001 R D FIRE 1 43 5001 R D SPARE (CTRLD* set low) 44 5001 R D START 2
45 5001 R D START 1 46 5001 R D VBLANK 47 ---------+-----+------------------------+------------------------
48 6000-600F W D D D D base_ram* 49 6200-621F W D D D D D D D D COLORAM* 50 6400 W INTACK*
51 6600 W D D D D EARCON 52 6800 W D D D D D D D D STARTLG (planet frame) 53 6A00 W WDOG*
54 ---------+-----+------------------------+------------------------ 55 6C00 W D START LED 1 56 6C01 W D START LED 2
57 6C02 W D TBSWP* 58 6C03 W D SPARE 59 6C04 W D CTRLD*
60 6C05 W D COINCNTRR 61 6C06 W D COINCNTRL 62 6C07 W D PLANET
63 ---------+-----+------------------------+------------------------ 64 6E00-6E3F W D D D D D D D D EARWR* 65 7000-701F D D D D D D D D IOS2* (Pokey 2)
66 7800-781F D D D D D D D D IOS1* (Pokey 1) 67 8000-EFFF R D D D D D D D D ROM 68 -----------------------------------------------------------------
According to this map 0000h and 0001h are x& ycoord and as such may not store data, the RAM starts at 0003h through 3fff. I would run the RAM test from 0003h to 07ffh, then 0800h to 0fffh, then 1000h to 17ffh and so on. Does the game have aworking self test? John :-#)#
2009/11/25 Kevin Moore <talon.k@gmail.com <mailto:talon.k@gmail.com>>
Well I was following the seqeunce given in the manual, which is Address lines, then Data lines, then Ram etc..
I'll run the bus sigs now, and see what I get.
Thanks,
Kevin
2009/11/25 John Robertson <jrr@flippers.com <mailto:jrr@flippers.com>>
Kevin Moore wrote:
Hi all, in my quest to learn more about using these tools, I've actually come up with a problem, and could use a little explanation.
I'm working on a liberator board, and was using the atari cat box. The first two tests in the liberator manual have you check address lines. Well those checked out good. Next was the Data lines. This is where things fell apart, and I'm not sure what I'm seeing.
Punch in address 0000, and write AA check the D0-D7 lines going to the ls245 well half the incoming lines are the wrong state, and the output of the ls245 is non existent. Ie pins 2-9 have no output.
So I hook up my fluke 9010a thinking there may be something wrong with the catbox, since this is the first time I've used it. Did the same basic setup wddis grounded, and Φ0 Φ2 shorted together. Do a write to 0000 with AA and use my logic probe to check. Same results.
Am I to assume Bad memory at location 0000.??
Yes.
Did you do the BUS Test first? That will show if any address or data lines are misbehaving.
If BUS Test is OK, and you get this problem for RAM @ 0000h, then try the next RAM set - say @ 0800h or 1000h (if RAM present - check Memory Map). If other RAM all checks OK, or ANY RAM checks OK, then the RAM @ 0000h is certainly suspect.
If the RAM is 4-bit, then which bits are locked will tell you which RAM to replace.
John :-#)#
-- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com <http://www.flippers.com> "Old pinballers never die, they just flip out"
_______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com <mailto:Techtoolslist@flippers.com> http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
-- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out" _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
Hi, I've got a noob question regarding ram testing and using the 9010. I'm trying to build a script to do some basic testing on Return of the Jedi using a known working board as a benchmark. So far I'm just concentrating on the main CPU, not the sound CPU and I've got the ROM test all working, now I'm moving on to the RAM. The schematics for Jedi list a ram area at 2400-27FF as Scrolling Playfield(high) and this appears to me to only have 4 data bits. If you run the built in RAM test on the Fluke for this area it fails, and from what I've managed to glean from the reading I've done this is as it should be as only 4 bits of data area are returned (a nibble?), whereas I assume the RAM test algorithm uses a whole 8 bits (byte). I've written the following script to exercise this (and other similar RAM areas). Can you tell me if I'm on the right lines? So far I've never done anything other than the built in 9010 tests so forgive me if this is a stupid question; REG1 = 2400 1: !LABEL 1 IF REG1 = 2800 GOTO 3 WRITE @ REG1 = FF WRITE @ REG1 = AA READ @ REG1 IF REGE = FA GOTO 2 dpy Failed Response = $1 = $E aux Failed Response = $1 = $E GOTO 3 2: !LABEL 2 aux Success Response = $1 = $E INC REG1 GOTO 1 3: !LABEL 3 dpy TEST COMPLETE aux TEST COMPLETE Cheers, Dan -- I am using the free version of SPAMfighter. We are a community of 6 million users fighting spam. SPAMfighter has removed 25777 of my spam emails to date. Get the free SPAMfighter here: http://www.spamfighter.com/len The Professional version does not have this message _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
Danny Pearson wrote:
Hi, I've got a noob question regarding ram testing and using the 9010. I'm trying to build a script to do some basic testing on Return of the Jedi using a known working board as a benchmark. So far I'm just concentrating on the main CPU, not the sound CPU and I've got the ROM test all working, now I'm moving on to the RAM. The schematics for Jedi list a ram area at 2400-27FF as Scrolling Playfield(high) and this appears to me to only have 4 data bits. If you run the built in RAM test on the Fluke for this area it fails, and from what I've managed to glean from the reading I've done this is as it should be as only 4 bits of data area are returned (a nibble?), whereas I assume the RAM test algorithm uses a whole 8 bits (byte). I've written the following script to exercise this (and other similar RAM areas). Can you tell me if I'm on the right lines? So far I've never done anything other than the built in 9010 tests so forgive me if this is a stupid question;
REG1 = 2400 1: !LABEL 1 IF REG1 = 2800 GOTO 3 WRITE @ REG1 = FF WRITE @ REG1 = AA READ @ REG1 IF REGE = FA GOTO 2 dpy Failed Response = $1 = $E aux Failed Response = $1 = $E GOTO 3 2: !LABEL 2 aux Success Response = $1 = $E INC REG1 GOTO 1
3: !LABEL 3 dpy TEST COMPLETE aux TEST COMPLETE
Cheers,
Dan
Looks like a good solution to the problems encountered with other 4-bit RAM (2101/5101/etc.) as well. However your test should include (at a minimum) F5 and FA to check that bits aren't locked. However if you only use FA and F5 then you have no way of finding stuck address nodes. So it wouldn't hurt to add an offset count - something like F0, F1, F2, F3, F4, F5, F6, F7...FE, then skip one space and run that again - this is to try and catch data/address rows or columns that are stuck - trying to check that bits in (for example) location 000h are not the same as location 010h which can happen if RAM internal (or external) addressing has problems. John :-#)# -- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out" _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
John Robertson wrote:
Danny Pearson wrote:
Hi, I've got a noob question regarding ram testing and using the 9010. I'm trying to build a script to do some basic testing on Return of the Jedi using a known working board as a benchmark. So far I'm just concentrating on the main CPU, not the sound CPU and I've got the ROM test all working, now I'm moving on to the RAM. The schematics for Jedi list a ram area at 2400-27FF as Scrolling Playfield(high) and this appears to me to only have 4 data bits. If you run the built in RAM test on the Fluke for this area it fails, and from what I've managed to glean from the reading I've done this is as it should be as only 4 bits of data area are returned (a nibble?), whereas I assume the RAM test algorithm uses a whole 8 bits (byte). I've written the following script to exercise this (and other similar RAM areas). Can you tell me if I'm on the right lines? So far I've never done anything other than the built in 9010 tests so forgive me if this is a stupid question;
REG1 = 2400 1: !LABEL 1 IF REG1 = 2800 GOTO 3 WRITE @ REG1 = FF WRITE @ REG1 = AA READ @ REG1 IF REGE = FA GOTO 2 dpy Failed Response = $1 = $E aux Failed Response = $1 = $E GOTO 3 2: !LABEL 2 aux Success Response = $1 = $E INC REG1 GOTO 1
3: !LABEL 3 dpy TEST COMPLETE aux TEST COMPLETE
Cheers,
Dan
Looks like a good solution to the problems encountered with other 4-bit RAM (2101/5101/etc.) as well. However your test should include (at a minimum) F5 and FA to check that bits aren't locked.
However if you only use FA and F5 then you have no way of finding stuck address nodes.
So it wouldn't hurt to add an offset count - something like F0, F1, F2, F3, F4, F5, F6, F7...FE, then skip one space and run that again - this is to try and catch data/address rows or columns that are stuck - trying to check that bits in (for example) location 000h are not the same as location 010h which can happen if RAM internal (or external) addressing has problems.
John :-#)#
Actually what would work is if you have the data count climb in one direction then fall in the other. Address - Data 000h - F0 001h - F1 002h - F2 ... 00Eh - FE 00Fh - FF 010h - FF 011h - FE 012h - FD ... 01Eh - F1 01Fh - F0 I think that would catch stuck address nodes... John :-#)# -- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out"
Hi all, I finally managed to find an hour or two to do some more on this based on the good suggestions I got and I think it's pretty complete, either way with a new baby about to arrive I think it's all I can do on this for now. I've uploaded the script (Jedi.9lc) to the /incoming directory on the FTP server. I'd appreciate if someone could give it a once over (a test would be great) and check that I've got the right IC's for each designated test. Thanks to James at QuarterArcade for the great script generator that provided most of the structure for this script. Cheers, Dan -----Original Message----- From: techtoolslist-bounces@flippers.com [mailto:techtoolslist-bounces@flippers.com] On Behalf Of John Robertson Sent: 03 December 2009 18:06 To: Technical Tools Mail List Subject: Re: [Techtoolslist] Jedi RAM testing John Robertson wrote:
Danny Pearson wrote:
Hi, I've got a noob question regarding ram testing and using the 9010. I'm trying to build a script to do some basic testing on Return of the Jedi using a known working board as a benchmark. So far I'm just concentrating on the main CPU, not the sound CPU and I've got the ROM test all working, now I'm moving on to the RAM. The schematics for Jedi list a ram area at 2400-27FF as Scrolling Playfield(high) and this appears to me to only have 4 data bits. If you run the built in RAM test on the Fluke for this area it fails, and from what I've managed to glean from the reading I've done this is as it should be as only 4 bits of data area are returned (a nibble?), whereas I assume the RAM test algorithm uses a whole 8 bits (byte). I've written the following script to exercise this (and other similar RAM areas). Can you tell me if I'm on the right lines? So far I've never done anything other than the built in 9010 tests so forgive me if this is a stupid question;
REG1 = 2400 1: !LABEL 1 IF REG1 = 2800 GOTO 3 WRITE @ REG1 = FF WRITE @ REG1 = AA READ @ REG1 IF REGE = FA GOTO 2 dpy Failed Response = $1 = $E aux Failed Response = $1 = $E GOTO 3 2: !LABEL 2 aux Success Response = $1 = $E INC REG1 GOTO 1
3: !LABEL 3 dpy TEST COMPLETE aux TEST COMPLETE
Cheers,
Dan
Looks like a good solution to the problems encountered with other 4-bit RAM (2101/5101/etc.) as well. However your test should include (at a minimum) F5 and FA to check that bits aren't locked.
However if you only use FA and F5 then you have no way of finding stuck address nodes.
So it wouldn't hurt to add an offset count - something like F0, F1, F2, F3, F4, F5, F6, F7...FE, then skip one space and run that again - this is to try and catch data/address rows or columns that are stuck - trying to check that bits in (for example) location 000h are not the same as location 010h which can happen if RAM internal (or external) addressing has problems.
John :-#)#
Actually what would work is if you have the data count climb in one direction then fall in the other. Address - Data 000h - F0 001h - F1 002h - F2 ... 00Eh - FE 00Fh - FF 010h - FF 011h - FE 012h - FD ... 01Eh - F1 01Fh - F0 I think that would catch stuck address nodes... John :-#)# -- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out" _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/ -- I am using the free version of SPAMfighter. We are a community of 6 million users fighting spam. SPAMfighter has removed 26930 of my spam emails to date. Get the free SPAMfighter here: http://www.spamfighter.com/len The Professional version does not have this message
Danny Pearson wrote:
Hi all, I finally managed to find an hour or two to do some more on this based on the good suggestions I got and I think it's pretty complete, either way with a new baby about to arrive I think it's all I can do on this for now. I've uploaded the script (Jedi.9lc) to the /incoming directory on the FTP server. I'd appreciate if someone could give it a once over (a test would be great) and check that I've got the right IC's for each designated test.
Thanks to James at QuarterArcade for the great script generator that provided most of the structure for this script.
Cheers,
Dan
I have put this file (Jedi.9lc) in the Fluke directory on TTL. Thanks Dan! John :-#)#
-----Original Message----- From: techtoolslist-bounces@flippers.com [mailto:techtoolslist-bounces@flippers.com] On Behalf Of John Robertson Sent: 03 December 2009 18:06 To: Technical Tools Mail List Subject: Re: [Techtoolslist] Jedi RAM testing
John Robertson wrote:
Danny Pearson wrote:
Hi, I've got a noob question regarding ram testing and using the 9010. I'm trying to build a script to do some basic testing on Return of the Jedi using a known working board as a benchmark. So far I'm just concentrating on the main CPU, not the sound CPU and I've got the ROM test all working, now I'm moving on to the RAM. The schematics for Jedi list a ram area at 2400-27FF as Scrolling Playfield(high) and this appears to me to only have 4 data bits. If you run the built in RAM test on the Fluke for this area it fails, and from what I've managed to glean from the reading I've done this is as it should be as only 4 bits of data area are returned (a nibble?), whereas I assume the RAM test algorithm uses a whole 8 bits (byte). I've written the following script to exercise this (and other similar RAM areas). Can you tell me if I'm on the right lines? So far I've never done anything other than the built in 9010 tests so forgive me if this is a stupid question;
REG1 = 2400 1: !LABEL 1 IF REG1 = 2800 GOTO 3 WRITE @ REG1 = FF WRITE @ REG1 = AA READ @ REG1 IF REGE = FA GOTO 2 dpy Failed Response = $1 = $E aux Failed Response = $1 = $E GOTO 3 2: !LABEL 2 aux Success Response = $1 = $E INC REG1 GOTO 1
3: !LABEL 3 dpy TEST COMPLETE aux TEST COMPLETE
Cheers,
Dan
Looks like a good solution to the problems encountered with other 4-bit RAM (2101/5101/etc.) as well. However your test should include (at a minimum) F5 and FA to check that bits aren't locked.
However if you only use FA and F5 then you have no way of finding stuck address nodes.
So it wouldn't hurt to add an offset count - something like F0, F1, F2, F3, F4, F5, F6, F7...FE, then skip one space and run that again - this is to try and catch data/address rows or columns that are stuck - trying to check that bits in (for example) location 000h are not the same as location 010h which can happen if RAM internal (or external) addressing has problems.
John :-#)#
Actually what would work is if you have the data count climb in one direction then fall in the other.
Address - Data 000h - F0 001h - F1 002h - F2 ... 00Eh - FE 00Fh - FF 010h - FF 011h - FE 012h - FD ... 01Eh - F1 01Fh - F0
I think that would catch stuck address nodes...
John :-#)#
-- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out" _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
Hi John, I realised about 5 mins after posting that I would need an additional step with 'F5' as 'FA' only covered 2 of the 4 bits :) Thanks for backing that up though. I had a discussion with someone on IRC today very much along the same lines as you suggested for the testing of Address Node issues. I'll see if my rudimentary 9010 programming skills are up to it and maybe post the result back. Incidentally is there a place to put completed scripts once (if!?!?) I ever complete it? Is there a community source repository? Cheers, Dan -----Original Message----- From: techtoolslist-bounces@flippers.com [mailto:techtoolslist-bounces@flippers.com] On Behalf Of John Robertson Sent: 02 December 2009 21:10 To: Technical Tools Mail List Subject: Re: [Techtoolslist] Jedi RAM testing Danny Pearson wrote:
Hi, I've got a noob question regarding ram testing and using the 9010. I'm trying to build a script to do some basic testing on Return of the Jedi using a known working board as a benchmark. So far I'm just concentrating on the main CPU, not the sound CPU and I've got the ROM test all working, now I'm moving on to the RAM. The schematics for Jedi list a ram area at 2400-27FF as Scrolling Playfield(high) and this appears to me to only have 4 data bits. If you run the built in RAM test on the Fluke for this area it fails, and from what I've managed to glean from the reading I've done this is as it should be as only 4 bits of data area are returned (a nibble?), whereas I assume the RAM test algorithm uses a whole 8 bits (byte). I've written the following script to exercise this (and other similar RAM areas). Can you tell me if I'm on the right lines? So far I've never done anything other than the built in 9010 tests so forgive me if this is a stupid question;
REG1 = 2400 1: !LABEL 1 IF REG1 = 2800 GOTO 3 WRITE @ REG1 = FF WRITE @ REG1 = AA READ @ REG1 IF REGE = FA GOTO 2 dpy Failed Response = $1 = $E aux Failed Response = $1 = $E GOTO 3 2: !LABEL 2 aux Success Response = $1 = $E INC REG1 GOTO 1
3: !LABEL 3 dpy TEST COMPLETE aux TEST COMPLETE
Cheers,
Dan
Looks like a good solution to the problems encountered with other 4-bit RAM (2101/5101/etc.) as well. However your test should include (at a minimum) F5 and FA to check that bits aren't locked. However if you only use FA and F5 then you have no way of finding stuck address nodes. So it wouldn't hurt to add an offset count - something like F0, F1, F2, F3, F4, F5, F6, F7...FE, then skip one space and run that again - this is to try and catch data/address rows or columns that are stuck - trying to check that bits in (for example) location 000h are not the same as location 010h which can happen if RAM internal (or external) addressing has problems. John :-#)# -- John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9 Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames) www.flippers.com "Old pinballers never die, they just flip out" _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/ -- I am using the free version of SPAMfighter. We are a community of 6 million users fighting spam. SPAMfighter has removed 25816 of my spam emails to date. Get the free SPAMfighter here: http://www.spamfighter.com/len The Professional version does not have this message _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
2009/12/3 Danny Pearson <dannypearson@hotmail.com>
it and maybe post the result back. Incidentally is there a place to put completed scripts once (if!?!?) I ever complete it? Is there a community source repository?
Hi Dan, I believe John has a directory inside the Flippers FTP site for these (upload to /incoming). And (shameless plug :) I am in the stages of testing a new site which will act as a repository for Fluke scripts & tips too. I'll post a link to this list once it's up and running. cheers tim _______________________________________________ Techtoolslist mailing list Techtoolslist@flippers.com http://seven.pairlist.net/mailman/listinfo/techtoolslist FTP site is: ftp://ftp.flippers.com/TTL/TestEquipment Archive site: http://seven.pairlist.net/pipermail/techtoolslist/
participants (4)
-
Danny Pearson -
John Robertson -
Kevin Moore -
Tim Matthews