{"id":564,"date":"2021-11-30T19:48:59","date_gmt":"2021-11-30T15:48:59","guid":{"rendered":"https:\/\/www.jrtwine.com\/blog\/?p=564"},"modified":"2021-11-30T19:48:59","modified_gmt":"2021-11-30T15:48:59","slug":"pac-man-with-strange-ram-issue","status":"publish","type":"post","link":"https:\/\/jrtwine.com\/blog\/pac-man-with-strange-ram-issue\/","title":{"rendered":"Pac-Man With Strange RAM Issue"},"content":{"rendered":"

So I was working on a Pac board for a friend that was dying at boot with symptoms of bad VRAM.\u00a0 I swapped out all of the RAMs only to have the problem persist. <\/p>\r\n

After hooking up the 9010A and screwing around for a while with diagnostic ROMs I realized that VRAM was getting written to correctly, but it could not be read from correctly – all reads returned the same value, regardless of the RAM address.\u00a0 I realized a bit later that any reads from ALL non-ROM locations (RAM, I\/O, etc.)\u00a0 were returning the same value<\/em>.\u00a0 This value ended up bring the value at memory location 0x00<\/strong>, or the first byte of the first ROM.<\/p>\r\n

I figured the VRAM addressor board was OK because since I could see correct stuff on screen, it was addressing VRAM correctly.\u00a0 I was also seeing the\u00a0WR<\/span>, and WE<\/span> lines toggle as expected on the CPU, and RAMs.\u00a0 However, it seems like data was not making it past the Z80 Sync Buss Controller (SBC).<\/p>\r\n

I reached out to a repair group I am in with the details of what I was seeing but got a whole lot of responses that indicated they did not actually read what I wrote since they kept asking about testing things I already discussed in the post, so I abandoned that effort.<\/p>\r\n

Turning my attention back to the Z80 SBC I started looking at things with a logic probe and scope and started clipping pins to see if I could figure out what was wrong.\u00a0 After socketing and replacing the parts that I clipped, I stumbled upon the problem.\u00a0 One of the ‘374s on the Z80 SBC was bad,\u00a0<\/p>\r\n

\"\"<\/a><\/p>\r\n

The behavior of the board and problem was the same with this chip removed.\u00a0 Once it was socketed and replaced, the diagnostic ROMs passed without issue and the game ROMs ran normally as well.<\/p>\r\n

An odd problem I had not seen documented before, but there you have it.<\/p>\r\n","protected":false},"excerpt":{"rendered":"

So I was working on a Pac board for a friend that was dying at boot with symptoms of bad VRAM.\u00a0 I swapped out all of the RAMs only to have the problem persist.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,10,7],"tags":[],"class_list":["post-564","post","type-post","status-publish","format-standard","hentry","category-repair-logs","category-ballymidway","category-repair-logs-2"],"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