{"id":201,"date":"2015-09-14T05:09:45","date_gmt":"2015-09-14T01:09:45","guid":{"rendered":"http:\/\/www.jrtwine.com\/blog\/?p=201"},"modified":"2016-02-02T09:18:02","modified_gmt":"2016-02-02T05:18:02","slug":"joust-showing-1-3-5-and-a-really-effed-up-screen","status":"publish","type":"post","link":"https:\/\/jrtwine.com\/blog\/joust-showing-1-3-5-and-a-really-effed-up-screen\/","title":{"rendered":"Joust Showing 1 3 5 and a REALLY Effed-Up Screen"},"content":{"rendered":"

[This was extracted from a large article about getting a dead Joust operational. \u00a0I thought it made sense to put this part in its own post to help anyone else with a similar issue. \u00a0This post may reference content from an earlier post<\/a>, so keep that in mind when reading.]<\/p>\n

So\u00a0at this point the Joust\u00a0will run through its self-tests, show 1 3 5<\/strong> on the LED, and will eventually enter attract mode and can even be coined up and it will play for a few seconds before crashing again. \u00a0While the screen is AFU, you can actually read text on it if you look carefully (just turn the audio off). \u00a0Pay attention to how the left 1\/3 screen is being drawn differently than the rest – this becomes important later:<\/p>\n

http:\/\/jrtwine.com\/blog\/wp-content\/uploads\/2015\/09\/DJoustBadRAM.mp4<\/a><\/video><\/div>\n

Going back to the board to run some tests, I\u00a0discover that pin 8 on a 74LS374<\/strong> (octal latch) located at 1H<\/strong>\u00a0is floating. \u00a0This latch is connected to the first RAM bank and is part of a Q\/D pair connected to D7<\/strong>.\u00a0 \u00a0So I now have to see if the ‘374<\/strong> is bad, or if there is some other defect on the board that is keeping it disconnected from D7<\/strong> of the data bus. \u00a0…like maybe one of those pads\/traces I effed-up earlier…<\/em><\/p>\n

Well, after thinking about it a while, I realize that it does not make sense for that pin to float, because it is connected to the RAMs – something should be present on it even if it is not being “driven” by the ‘374<\/strong>. \u00a0So I had that in my head as I was removing the board to solder the pins that I clipped earlier, and notice that the bottom-most RAM in row 1 was not in its socket correctly! \u00a0I wired the board back up and powered-up and I still had a corrupted screen and a 1 3 5<\/strong> error, but it was drawing a bit differently, and the behavior of the ‘374<\/strong> was now correct.<\/p>\n

After disconnecting the board again I brought it down to my rework station and noticed some crud under that ‘133<\/strong> near the pin that was behaving strangely. \u00a0I removed it, wondering if it was causing the issue. \u00a0Anyway, after repairing the clipped pins, I remembered something Mark had mentioned to me earlier as I was troubleshooting the board. \u00a0I had seen the board try to rug a few times and it always looked like it was drawing the run incorrectly, jumping around the screen. \u00a0I had mentioned to him how the screen seemed like it was getting drawn in quadrants (for lack of a better word), and he mentioned that having the incorrect decoder ROMs would make strange things like that happen. \u00a0I double-checked the locations of the decoder ROMs, and it turns out that I accidentally swapped their relative positions when I did the sockets on the CPU board!<\/p>\n

So I swapped them back and put the board back in, and damn! \u00a0<\/strong><\/em>Had a perfectly clear and correctly-drawn rug pattern! \u00a0Did not have to touch that ‘133<\/strong> either, so I guess the crud really was the cause.<\/p>\n

Game reported a ROM 3 error, but came up correctly into attract mode (after restoring factory settings), but would crash after showing the high-score table. \u00a0I pulled ROM 3 hoping to find a bent pin, and not a situation where flow-through of solder caused a problem, and as luck would have it, I had bent a pin! \u00a0Straightened the pin, powered her back up and I everything comes up great:<\/p>\n\n\n\n
\"JoustLivesForReal1\"<\/a><\/td>\n\"JoustLivesForReal2\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

However, after coining it up and starting a game, player 1 starts running to the left non-stop. \u00a0(This issue was moved to its own post<\/a>.)<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

[This was extracted from a large article about getting a dead Joust operational. \u00a0I thought it made sense to put this part in its own post to help anyone else with a similar issue. \u00a0This post may reference content from an earlier post, so keep that in mind when reading.] So\u00a0at this point the Joust\u00a0will […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,7,58],"tags":[20,67,69,60,21,26,68,59],"class_list":["post-201","post","type-post","status-publish","format-standard","hentry","category-repair-logs","category-repair-logs-2","category-williams","tag-arcade","tag-decoder","tag-graphics","tag-joust","tag-repair","tag-repair-log","tag-roms","tag-williams"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t