<div class="bbWrapper">The beeps. It should play 5 for bad vidram, 6 for bad colour.<br />
<br />
The way it was, you'll only hear 3 for bad vidram & 4 for bad colour on real hardware, I need to play with the timing to get them all out. <br />
<br />
I think you should hear all intended beeps now in Test 1.0<br />
<br />
Test 1.0<br />
<br />
http://www.pastefile.com/5ZCmjdshoestring2015-08-16 00:59:28</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="Purity" data-source=""
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
Purity said:
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
Anything else you need me to look at ?<br />
<br />
I probably have some partial faulty 2114's in my junk pile. I can swap the good ones out for the faulty ones if you want me to see what happens?
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
It's really up to you. I think you've done so much already & I appreciate your help and everyone elses.<br />
<br />
Caius has recently purchased some faulty boards and is going to do a thorough test on it as well.<br />
<br />
Edit: I think I should suspend further checks if video or colour ram is bad ( since nothing can be seen on the screen / worst case scenario ) because someone is bound to be pissed off if high scores are erased.shoestring2015-08-16 01:13:01</div>
<div class="bbWrapper">I've added BETA 1.2 to JAMMArcade.<br />
<br />
<a href="http://www.jammarcade.net/track-field-test-rom-beta/" target="_blank" class="link link--external" rel="nofollow ugc noopener">http://www.jammarcade.net/track-field-test-rom-beta/</a><br />
<br />
Only difference between Test 1.0 and BETA 1.2 is that further checks are suspended when video/colour ram is detected as bad. Everything else should be the same <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />shoestring2015-08-16 06:44:50</div>
<div class="bbWrapper">Whoops, I think it was because I had it in A4. If I put A1 in A2 it idents ok<br />
<br />
BTW I tested my 502 on another PCB and it works fine :-(<br />
Purity2015-08-17 22:33:37</div>
<div class="bbWrapper">Same thing will happen if you put rom1 in socket 5 but I just fixed both of these issues. <br />
<br />
Edit: Well actually it's not possible to swap rom A5, see explanation in next post regarding reset vector.<br />
<br />
Good thing the 502 works. They can be hard to replace.<br />
<br />
Maybe it's time to look at the supporting ttls around the 502 ?<br />
shoestring2015-08-18 05:35:02</div>
<div class="bbWrapper">Just a small important note.<br />
<br />
The A5 rom needs to remain in socket5A. This is because the reset vector is obtained right at the end of this rom.<br />
<br />
<b>Edit: having thought more about this I've decided to re-write the test rom so that it installs in socket 5a. I will be able to set the reset vector <br />
and free up the first 4 sockets ( 1a,2a,3a and 4a ) for the rom utility.<br />
<br />
Main reason for this change is that if A5 is bad, there's a chance that the game/test rom will boot to garbage if the reset vector is corrupted. Having direct control over the reset vector is the best way forward.</b>shoestring2015-08-19 03:21:42</div>
<div class="bbWrapper">Latest TEST 1.1<br />
<br />
http://www.pastefile.com/wZNsqb<br />
<br />
<div class="bbImageWrapper js-lbImage" title="test_1.1.png"
data-src="https://www.ukvac.com/forum/data/uploads/2827/test_1.1.png" data-lb-sidebar-href="" data-lb-caption-extra-html="" data-single-image="1">
<img src="https://www.ukvac.com/forum/data/uploads/2827/test_1.1.png"
data-url="https://www.ukvac.com/forum/data/uploads/2827/test_1.1.png"
class="bbImage"
data-zoom-target="1"
style=""
alt="test_1.1.png"
title=""
width="" height="" loading="lazy" />
</div>
<br />
<br />
Test ROM now installs in <b>SOCKET 5A</b> as proposed.<br />
<br />
This allows sockets 1a - 4a available for swapping out roms. ROM A5 can be tested in any of the first 4 available sockets.<br />
<br />
Much less confusing and more useful now.<br />
shoestring2015-08-19 03:23:02</div>
<div class="bbWrapper">Cool will check that out.<br />
<br />
BTW I found the issue with my runners. I now have them back!<br />
<br />
I notcied some stuck pins on two of the eproms, and traced this back to a faulty LS04<br />
Purity2015-08-20 14:00:54</div>
<div class="bbWrapper">The new rom seems fine in 5A. I agree that it seems a more convenient place to put it<br />
<br />
The 74LS04 had no markings on it, so strangely not a Fujitsu this time <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /><br />
<br />
Still need to fix the issues wth the background, and text. It still is not right. Might be more trickier as it is actually showing content<br />
<br />
Purity2015-08-20 22:18:22</div>
<div class="bbWrapper">Great. I did update JAMMArcade already with this test version only, I won't release it as BETA until I'm 100% sure because it was a large enough code change even though it passed all my test cases. You just never know on real hardware. <br />
<br />
How about the sound alerts for video/color ram? Are you hearing 5 or 6 depending on which is pulled ?shoestring2015-08-20 22:59:11</div>
<div class="bbWrapper"><blockquote data-attributes="" data-quote="shoestring" data-source=""
class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch">
<div class="bbCodeBlock-title">
shoestring said:
</div>
<div class="bbCodeBlock-content">
<div class="bbCodeBlock-expandContent js-expandContent ">
How about the sound alerts for video/color ram? Are you hearing 5 or 6 depending on which is pulled ?
</div>
<div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div>
</div>
</blockquote><br />
Dude did you still need this testing?</div>
<div class="bbWrapper">Is Beta 1.3 the latest or Test 1.1? The <a href="http://www.jammarcade.net/track-field-test-rom-beta/" target="_blank" class="link link--external" rel="nofollow ugc noopener">Blog post</a> indicates it is Test 1.1.<br />
<br />
The Test 1.1 link from the blog post is 404, but I figured out the mistake in the URL to find the correct path:<br />
<br />
<a href="http://www.jammarcade.net/files/ROMs/Diagnostic/trkdiag-test1.1.bin" target="_blank" class="link link--external" rel="nofollow ugc noopener">http://www.jammarcade.net/files/ROMs/Diagnostic/trkdiag-test1.1.bin</a><br />
<br />
I tried it on two different faulty boardsets and both passed all tests. How do you invoke the NVRAM test?</div>
<div class="bbWrapper">Test is the latest. But I will move it into beta since it<br />
appears to be fairly happy in the other socket. <br />
<br />
Nvram test is automatic. You can turn it off / on<br />
via dip or wait for the countdown. <br />
<br />
I think you're asking about how to enter the diagnostic mode?<br />
<br />
What's your actual problem ?</div>