Welcome, Guest. Please login or register.

Author Topic: Amiga 500 Hardware Problem - Advice Please  (Read 7415 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline GadgetUKTopic starter

  • Jr. Member
  • **
  • Join Date: Mar 2013
  • Posts: 89
    • Show only replies by GadgetUK
Re: Amiga 500 Hardware Problem - Advice Please
« Reply #14 from previous page: March 09, 2013, 10:15:17 PM »
I am on the home run now!  I found another game that had major graphical corruptions.  I ended up socketting all of the remaining RAM chips, only when I got to the very last chip did the corruption vanish after I tried a good chip in the socket.  The Days of Thunder corruption is still there but Lotus 3 is massively improved - can play for 2 or 3 mins now before it crashes and there are no graphical issues.  I suspect 1 of the chips I thought was OK isnt.  Just need to swap 1 at a time tomorrow until Days of Thunder looks OK.

I've also had to order 2 ceramic caps (0.33uF) to replace 2 that broke.
 

Offline Oldsmobile_Mike

Re: Amiga 500 Hardware Problem - Advice Please
« Reply #15 on: March 09, 2013, 10:57:10 PM »
That is some pretty serious troubleshooting, kudos!  :)
Amiga 500: 2MB Chip|16MB Fast|30MHz 68030+68882|3.9|Indivision ECS|GVP A500HD+|Mechware card reader + 8GB CF|Cocolino|SCSI DVD-RAM
Amiga 2000: 2MB Chip|136MB Fast|50MHz 68060|3.9|Indivision ECS + GVP Spectrum|Mechware card reader + 8GB CF|AD516|X-Surf 100|RapidRoad|Cocolino|SCSI CD-RW
 Amiga videos and other misc. stuff at https://www.youtube.com/CompTechMike/videos
 

Offline GadgetUKTopic starter

  • Jr. Member
  • **
  • Join Date: Mar 2013
  • Posts: 89
    • Show only replies by GadgetUK
Re: Amiga 500 Hardware Problem - Advice Please
« Reply #16 on: March 10, 2013, 12:41:07 AM »
Quote from: Oldsmobile_Mike;728675
That is some pretty serious troubleshooting, kudos!  :)


Lol, thanks, I believe i've done it!  All games work and look perfect, just played lotus 3 for 3 levels and no problems at all.  Since I socketed all RAM and had replaced 8 definite faulty chips and still had the odd crash I just swapped the 8 remaining chips for new ones and thats cracked it.

Days of Thunder still doesnt display the car dash but ive a strong suspicion its the disk at fault as everything else runs just fine.
 

Offline GadgetUKTopic starter

  • Jr. Member
  • **
  • Join Date: Mar 2013
  • Posts: 89
    • Show only replies by GadgetUK
Re: Amiga 500 Hardware Problem - Advice Please
« Reply #17 on: March 10, 2013, 09:36:21 AM »
Just thought I would expand with a 'lessons learnt' here, in the hope that my experience with this A500 might help someone else trying to repair one in the future.
 
When I first got the A500 it was described as working and in good condition. Upon booting the machine with a few games it seemed OK, but some games crashed at the same point each time. Now originally it had KS1.2 ROM so I assumed that all it needed was a KS1.3 and a good clean etc.
 
Stripped it down, fairly clean inside but the metal shielding had some corrosion - not a good sign as the flakes get onto the motherboard. Proceeded to remove the shielding and take a look at the motherboard. I could see several 'dark' coloured pins on Denise, the CIA nearest Paula, Paula, Agnus, and spill marks on the PCB. It smelt and looked like coffee from many years ago.
 
After removing those sockets chips and cleaning up the corroded pins with a wire brush I noticed the sockets were much worse - that green colour you get with corrosion in the same pins in the socket where the pins were 'dark' on the associated chips. EDIT: Cleaned the PCB using Isopropanol achohol, and after soldering a socket / chip, cleaned with the same stuff but used a fine wire brush to remove flux (PCB looks untouched as a result).
 
Replaced the Paula and Denise sockets with new ones (48 pin DIP), then replaced the CIA socket (40 pin DIP). Finally re-tested, it was a bit better but some games still crashed at the same point and it seemed to be sensitive to movement. Used PLCC extractor to remove Agnus... Agnus came out with the removal tool WITH the PLCC socket plastic component. So what was left on the board were 84 pins sat there on their lonesome, with the plastic part of the socket in my hands.
 
The socket then just litterally crubbled appart - I am not kidding the plastic was mega brittle with coffee and ageing. On inspection I could see what had gone on in the past. Firstly, the Agnus had at some point been levered out of the socket using the wrong kind of tool and the corner had split and been SUPER GLUED (OMG). The owner then proceeded to use a MEGA STICKY DOUBLE SIDED PAD to glue the Agnus INTO the socket (hence why Agnus was sat in my hand with a plastic socket glued to her ass). With coffee, corrosion and a partly split corner held with glue the little lass stood no chance of lasting.
 
I replaced the Agnus socket - this was the most difficult to do as you cannot just cut the plastic part on the top of the PCB. I mentioned the plastic came off already, it did, but that was the square part that holds all the pins to the chip, underneath that is a very very thin piece of plastic that holds all the pins flat against the board, that doesnt come off as its pretty much molded with the pins. For DIP 40 and 48 sockets a nice safe way of removing them I found was to desolder all the pins, once the solder hole looks empty, wiggle the pin with a very small screw driver, and if the socket doesnt just fall off, proceed to CUT the black plastic of the socket into blocks of 2 / 3 pins - this way they come out much easier and if you get a stuck pin you can just heat that pin on its own whilst using the other hand to pull slightly at the block of pins you are trying to remove. Anyway, one 84 pin PLCC through pin hole socket later and Agnus had a new home, free from any problems - phew...
 
Testing again revealed a significant improvement, a few games worked now that didnt previously, but I just had problems with many games and they all had similar problems whereby they would crash at a specific point every time.
 
Using the piggyback method (just sit a new 41256 RAM chip on top of the existing one so it snuggly hugs the bottom chips pins), and testing Turrican one chip per reboot I found a chip that when it was piggybacked caused Turrican to NOT hang on the part it had before. To make this story a bit shorter, I repeated that process around 4 times until Turrican was almost flawless, and extended the testing to Lemmings, Days of Thunder, Rolling Thunder, and some shoot em up I can't remember the name of (coded by DMA), each exhibited either a hang at a certain point loading, or graphical corruptions. Now the graphical corruptions were by far the hardest to address because after piggybacking all chips the shootemup game and Turrican still had graphical wierdness with some sprites. At this point I had replaced like 3 or 4 RAM chips in sockets, but now I had to replace all of the remaining chips with sockets. After carrying out this work I started replacing the testing the newly socketed 'old RAM' one chip at a time against those games with garbage sprites. This approach worked well and at the end I had 8 X NEW RAM and 8 X OLD RAM. The system was 99.8% now, everything loaded, next to no crashes at all, but Lotus III only worked for a few minutes before a random reboot. I thought about this and came to the conclussion that my approach - ie. to try and save old RAM chips and only replace what was required had long since become a flawed approach, since I had ended up replacing 8 chips already (50%), and out of those 8, 4 allowed the piggyback approach, meaning that an address line or data line had gone open circuit, and the other 4 chips didn't allow that approach, meaning that they were bringing back random results (eg. a high instead of a low), and its not like these were all 8 of the top or bottom bank, they were randomly situated. So my reasoning at this point was, yes its much much better now but these really obscure crashes in Lotus that are very hard to re-create must be related to RAM timing, and possibly one of those remaining chips is glitching on an infrequent basis.
 
So I finally just replaced the last 8 old chips with 8 new ones. Unfortunately I didnt have any more - 15 (150ns) chips, only -12's. I seperated them into the 2 logical banks, 1 row of -12's and 1 row of -15's. It shouldnt make any difference at all, just one bank will be perkier than the other lol, but both within the design limits. For the first time I was able to play Lotus 3 until I SWITCHED IT OFF, rather than the system dictating I would have only 30 seconds to race. It worked flawless, no glitches of any kind, very stable. I also left it on the demo screens of Lotus 3 for a good 20 minutes with no crashes.
 
I declare this A500, 'back from the dead', to live another 20 to 25 years hopefully.
 
Final steps for me now are to solve a loose connection on the floppy power cable (probably needs a bit of solder), and to 'retrobrite' the case, a process which i've had good success with so far on the A1200 case I am doing at the mo. I've already serviced the floppy drive, and also added a KS1.3 ROM in very early on btw. I also plan to add a DSDT switch to toggle the expansion RAM between 1Mb chip or 50/50, but I will need the 1Mb Agnus before I do that. I may also add one of those 8Mb fastram boards to the CPU but I am not sure as I probably would never use it lol
 
EDIT: Forgot to mention, that corrosion on the metal shielding - all dealt with early on, using metal polish (Brasso). Wiped down afterwards with paper towels to remove residue, then wiped again with a very fine oil in order stop future corrosion (don't use something like WD40, unless you want it to smell like a car engine forever lol).
« Last Edit: March 10, 2013, 09:42:47 AM by GadgetUK »
 

Offline paul1981

Re: Amiga 500 Hardware Problem - Advice Please
« Reply #18 on: March 10, 2013, 01:32:04 PM »
Quote from: GadgetUK;728712
EDIT: Forgot to mention, that corrosion on the metal shielding - all dealt with early on, using metal polish (Brasso). Wiped down afterwards with paper towels to remove residue, then wiped again with a very fine oil in order stop future corrosion (don't use something like WD40, unless you want it to smell like a car engine forever lol).

That's a brilliant job done Gadget. I'd have slung that A500 in the bin! Nice to see a lobster rescued. :)
I've had corrosion on an A1200 shield that was so bad that there was a hole in the shield. I admit, when I was younger I spilt drinks in my 1200...not deliberately of course.
 

Offline GadgetUKTopic starter

  • Jr. Member
  • **
  • Join Date: Mar 2013
  • Posts: 89
    • Show only replies by GadgetUK
Re: Amiga 500 Hardware Problem - Advice Please
« Reply #19 on: March 10, 2013, 02:08:10 PM »
Quote from: paul1981;728721
That's a brilliant job done Gadget. I'd have slung that A500 in the bin! Nice to see a lobster rescued. :)
I've had corrosion on an A1200 shield that was so bad that there was a hole in the shield. I admit, when I was younger I spilt drinks in my 1200...not deliberately of course.


Thanks lol, really pleased its tip top now.  Its passed the burn-in test, lotus 3 been looping demos for 4 hours, it seems rock solid now =). Now the fun begins!
 

Offline GadgetUKTopic starter

  • Jr. Member
  • **
  • Join Date: Mar 2013
  • Posts: 89
    • Show only replies by GadgetUK
Re: Amiga 500 Hardware Problem - Advice Please
« Reply #20 on: March 10, 2013, 03:48:19 PM »
Just for completeness I tested Days of Thunder on the A1200 - yay, it showed exactly the same problem on the car dash - a corruption of what looks like part of the title screen in the wrong palette mixed with garbage.
 
This means that my Days of Thunder is obviously corrupt =)
 
Been playing the A500 all day, not a single glitch or anything, it's 100%.
 
Case closed I think.
 

Offline sweetlilmre

  • Jr. Member
  • **
  • Join Date: Jul 2007
  • Posts: 75
    • Show only replies by sweetlilmre
Re: Amiga 500 Hardware Problem - Advice Please
« Reply #21 on: March 24, 2013, 07:07:38 PM »
Did you ever find a memcheck program that would run on < KS2.04?
Specifically 1.3? I have some similar issues to you but with an expansion board. I'd like to see if the memory scans as ok as a first step.

Thanks
-(e)
A1200: Blizzard 030 50Mhz 32Mb Ram, Micronik SD, CF 4GB with ClassicWB
 

Offline GadgetUKTopic starter

  • Jr. Member
  • **
  • Join Date: Mar 2013
  • Posts: 89
    • Show only replies by GadgetUK
Re: Amiga 500 Hardware Problem - Advice Please
« Reply #22 on: March 25, 2013, 06:42:42 PM »
Quote from: sweetlilmre;730199
Did you ever find a memcheck program that would run on < KS2.04?
Specifically 1.3? I have some similar issues to you but with an expansion board. I'd like to see if the memory scans as ok as a first step.
 
Thanks
-(e)

I have to admit that I gave up and followed other methods of testing. I do want a memory tester for KS1.3 in order that I can just give it a once over for good measure but since I ended up replacing all of my RAM with new RAM I ultimately didn't need to do it.
 
For the most part I would find it unusual to have more than 1 RAM chip fail at a time but I ended up with 8 that were definitely bad, and 1 or more that had timing / glitching issues out of the remaining 8, that's 9 or 10 out of 16 - not worth trying to work out which 4 or 5 chips to keep - after all, how long would the remaining ones last considering so many of the others failed?
 
That said, i've kept all 8 of the old chips and recently found I have some 256Kb SIMMS that have 1 x 41256 DRAM chip on each board - presumably for parity, I was thinking about adding a socket onto one of the SIMMS in order that I can plug Amiga and ST DRAM chips into it (one at a time) in order that I can test on an ST to determine which of my chips were at fault and which are still OK. If its on the parity chip that might not work though because I don't think the ST uses parity so it won't test it =/ Will post an update when I've had a closer look.
 
The best RAM test you are going to get are your games. If your PSU is OK, and its just random crashes and graphical corruption you are getting then ultimately you are going to end up socketting all the RAM and replacing any faulty chips. You can get some new 41256 chips and piggy back as described earlier in this thread.
 
 
The problem with all memory testers is they rely on the system loading workbench, drivers etc etc all into good working RAM, before they start testing all of the RAM. So if you get a problem like I had it will crash trying to even load a tester - despite workbench booting fine.