Welcome, Guest. Please login or register.

Author Topic: Trying to call my A4000D back to life  (Read 2594 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline servitusTopic starter

  • Newbie
  • *
  • Join Date: Aug 2013
  • Posts: 14
    • Show only replies by servitus
Trying to call my A4000D back to life
« on: February 27, 2014, 03:22:08 PM »
Hi folks

... this is another sad A4000 story. I got it out of my cellar, opened it and recognized that most caps and battery have leaked. The last 3 weeks I have been soldering almost every evening. I replaced all the caps and most of the IC's surrounding the leaking caps. After that, I powered up and nothing happened... after reading some stories of others with similar problems, I re-soldered the video interface, all the solder joints on Lisa and some cold soldering joints on my A3640. All of a sudden, it booted to the disk-screen (with disk animation). I thought "wow, cool I got it" ... but now I'm facing the following strange behaviour:

Testing-Scenario 1:

Setup: Keyboard, Mouse, A3640 and Chip-/Fast-RAM

=> it boots to the disk-insert screen, then I insert Workbench 3.1, it loads the workbench and as soon as I double-click the workbench icon the system crashes and I get a red "software-failure" message:

Error: 8000 0004 / Task: 0780F1F4

Testing-Scenario 2:

Setup: Keyboard, Mouse, A3640 and only Chip-RAM

=> the screen goes dark-gray, light-gray, flickering white cpu-line across the screen, waiting for some seconds, then I get directly the following "software-failure":

Error: 8000 0004 / Task: 00003318

What might be the problem? I already tried another SIMM for Chip-Mem, same result. I measured voltage between GND and the 5V line and I got 4.91V with the setup described above. I already cleaned the CPU/MB connection and the power supply plugs on both sides. The CPU card is seated well. There should no short circuits exists between MB and chassis.

Any ideas how to proceed? Any help is highly appreciated, since I want to bring that lovely Amiga back to life :banana:
 

Offline spirantho

Re: Trying to call my A4000D back to life
« Reply #1 on: February 27, 2014, 04:10:58 PM »
Possibly a Chip RAM problem...? If it works ok with Fast RAM (at least at first) then it'll be using less Chip RAM. Do a memory test on the Chip RAM (there are various memory test programs on Aminet) - and Fast RAM too for that matter. It's possible one of the addressing lines is dodgy.
Have you tried booting a game?
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!
 

Offline servitusTopic starter

  • Newbie
  • *
  • Join Date: Aug 2013
  • Posts: 14
    • Show only replies by servitus
Re: Trying to call my A4000D back to life
« Reply #2 on: February 27, 2014, 04:50:00 PM »
Unfortunately I don't have a reference machine to test the Chip RAM and the A4000 crashes as soon as I want to open any folder or program on the workbench... But I have plenty of other SIMMs which I'll try after work.

You're right, possibly the lines under the Chip-RAM sockets are dodgy. I'll solder out that socket to have a better look at them. But honestly said, the Amiga worked more or less stable before I began to change the IC's and caps - except it sometimes didn't identified all of the 16mb Fast-RAM - that was initially the reason why I began to replace all the elements... Which chips are involved in memory management?

I'll try to boot a game as soon as I am at home and will report what happens...

Btw: When I replaced the Poly-Switch (F175) near the parallel-/serial-interface, I pulled out both VIA-connections :-/ Do you know if these are connected to an intermediate level of the multi-layered mainboard? I successfully bridged the lines on the upper- and lower-side, but I'll have a big problem if there are more connections inbetween... :-o
« Last Edit: February 27, 2014, 05:02:16 PM by servitus »
 

Offline spirantho

Re: Trying to call my A4000D back to life
« Reply #3 on: February 27, 2014, 05:10:08 PM »
I think you'll be ok on the VIA connections....

For the sockets, this page is your friend:
http://www.amigawiki.org/doku.php?id=en:service:schematics

The schematics on this page are simply awesome (and searchable). :) If it didn't always identify all the Fast RAM that sounds like something dodgy that could be a more serious problem.
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!
 

Offline Oldsmobile_Mike

Re: Trying to call my A4000D back to life
« Reply #4 on: February 27, 2014, 06:59:53 PM »
Quote from: spirantho;759848
The schematics on this page are simply awesome (and searchable).

Wow, those are amazing! Whoever spent the time to make those documents, great job! :drink:
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 servitusTopic starter

  • Newbie
  • *
  • Join Date: Aug 2013
  • Posts: 14
    • Show only replies by servitus
Re: Trying to call my A4000D back to life
« Reply #5 on: February 27, 2014, 09:30:54 PM »
basically I don't fear serious problems at all, as long as they are somehow solvable :-) I want that Amiga bring alive again..!

I realized that I can test the Fast-RAM SIMM's on my A1200 with Blizzard IV - I checked them with a couple of ram testing apps and they seem to be okay. I also try some other SIM-modules, same problem...

Games also don't work. They load until some point and then the system crashes again with some kind of red "software failure" message. What's the idea behind the "game-test" ?

I removed the "unrecognized" Fast-RAM for further testing.

Also I'm able to get into the early boot menu where all my devices are listed (even the hard-drive and the two external floppies which I once attached) DF0, DF2, DF3, HD0, HD1, HD2. What does "Disable CPU caches" mean by the way?

Someone any idea how to proceed ? Any measurement-based or mechanical approach? :rofl:

Btw: Thanks for the link to the schematics - I used them alot to identify which parts I need to order for replacement.
« Last Edit: February 27, 2014, 10:07:16 PM by servitus »
 

Offline spirantho

Re: Trying to call my A4000D back to life
« Reply #6 on: February 27, 2014, 10:06:23 PM »
The purpose of the RAM test is less to check the RAM and more to check the connections to the RAM. Testing in another machine won't help here. :)
The purpose of a game test is just to rule out as many variables as possible (bad floppies etc.) - if a simple 512KB A500 game (Which is tested as normally working on an 040) fails, it'll give us a bit more idea. Still sounds like a bus error to me.

That thing about only 8MB RAM detected.... I presume you're fitting 4 4MB SIMMs? If it's supposed to be 16MB but only 8MB is detected, then something's squiffy with the RAM bus or connector, probably.
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!
 

Offline paul1981

Re: Trying to call my A4000D back to life
« Reply #7 on: February 27, 2014, 10:25:50 PM »
Kickstart ROM?
 

Offline servitusTopic starter

  • Newbie
  • *
  • Join Date: Aug 2013
  • Posts: 14
    • Show only replies by servitus
Re: Trying to call my A4000D back to life
« Reply #8 on: March 08, 2014, 06:12:43 PM »
Thanks for the hint to the Kickstart-ROMs... I replaced the original ROMs from my A4000D with those of my A1200. Wow - now it boots within 1-2 sec to the boot-screen, but Fast-RAM is not recognized. Using the original ROM's, Fast-RAM is now recognized, but the system works very unstable and crashes all the times. Btw I replaced all the SIMM sockets with new ones...

Here's a quick summary of my two testing scenarios:

with A1200 ROM: very fast boot (1-2 sec), Fast-RAM not recognized (only Chip-RAM), system works stable

with original A4000 ROM: very slow boot (~1 min), Fast-RAM + Chip-RAM is recognized, system works very unstable

So my big question at the moment:

Are the Kickstart-ROMs v3.1 for the A1200 and the A4000 Desktop not the same :angry: ??
 

Offline stachu100

  • Sr. Member
  • ****
  • Join Date: Aug 2009
  • Posts: 292
    • Show only replies by stachu100
Re: Trying to call my A4000D back to life
« Reply #9 on: March 09, 2014, 09:47:59 AM »
Kickstart ROM for A1200 is NOT the same as A4000.
Main differences:
 scsi.device, battery clock support for A4000, ZORRO support (Super Buster) for A4000, onboard FAST RAM support for A4000.
And few more.
If A4000 crashes with A4000 ROM and working with A1200 ROM, it means that you have problems with stuff not presebt in A1200: FAST, RTC, Super Buster. If your Super Buster is socketed, please remove socket and solder Super Buster directly to the PCB. This socket tends to loose contact with the chip over the time.
 

Offline spirantho

Re: Trying to call my A4000D back to life
« Reply #10 on: March 09, 2014, 11:12:04 AM »
How does it behave with all the Fast RAM removed? Does it work like with the A1200 or is still unstable?
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!
 

Offline servitusTopic starter

  • Newbie
  • *
  • Join Date: Aug 2013
  • Posts: 14
    • Show only replies by servitus
Re: Trying to call my A4000D back to life
« Reply #11 on: March 10, 2014, 09:51:51 AM »
@stachu100: many thanks for the valuable insights. so that explains my fast-ram issues in detail :-) since the original A4000 ROMs seem to have a defect (very long boot-time and problems addressing fast-ram), I'll try to replace them with new ones (I'll buy some from vesalia.de). Btw super-buster is not socketed and I already re-soldered all legs - thanks for the hint.

@spirantho: with all fast-ram removed and using the A1200 kickstart-roms, without any other devices except keyboard, mouse and chip-mem, the A4000 now works very stable again :insane:

summary: next step is to order new kickstart roms :-) It was a long and frustrating way until I got here - hope this finally solves my problems :-)

I will post my further findings as soon as I get the new roms... thank you so far for your help!
 

Offline stachu100

  • Sr. Member
  • ****
  • Join Date: Aug 2009
  • Posts: 292
    • Show only replies by stachu100
Re: Trying to call my A4000D back to life
« Reply #12 on: March 10, 2014, 09:55:08 AM »
I'm 99,99% sure that ROMs are fime. You still have hardware problem on your mobo.
 

Offline Castellen

Re: Trying to call my A4000D back to life
« Reply #13 on: March 10, 2014, 09:06:46 PM »
I agree, very unlikely that the ROMs are at fault.  If there was a data corruption problem within them, this would be picked up by the checksum test during early boot.



Quote from: servitus;759847
Unfortunately I don't have a reference machine to test the Chip RAM and the A4000 crashes as soon as I want to open any folder or program on the workbench... But I have plenty of other SIMMs which I'll try after work.?



As others have pointed out, this behavour is consistent with memory issues.  If you're able to boot without startup, run Memcheck from floppy, you may get results before it crashes due to memory issues.

Another problem which can cause this is clock synchronisation, which can happen if the A4000 is clocked from its own onboard oscillator while the external CPU board is running from its separate reference.  Though often this causes total boot failure, or failure during early boot.  With the A3640, both clock source jumpers on the A4000 main board must be set to EXT.

If there has been corrosion damage around U177 (RTC latch) this part should be replaced, else there can be issues with the latch causing corruption on the CPU address bus.  Likewise, if U178 is damaged, this can cause CPU data bus issues.  Though usually in this case, the machine just won't boot at all.  If in doubt you can remove U177 and U178, the machine will boot fine without them.  Use caution; if you had problems when removing F175 (below), then you're unlikely to remove these parts without causing more damage.



Quote from: servitus;759847

You're right, possibly the lines under the Chip-RAM sockets are dodgy. I'll solder out that socket to have a better look at them. But honestly said, the Amiga worked more or less stable before I began to change the IC's and caps - except it sometimes didn't identified all of the 16mb Fast-RAM - that was initially the reason why I began to replace all the elements... Which chips are involved in memory management?



In the A4000, half of U250/Bridgette forms the bidirectional bridge between chip memory and other devices on the chip memory bus.  But it's unlikely this is the problem.  Has there really been damage to the chip memory tracks?  This is the U261 socket.  There's nothing common in this area to cause much damage, aside from major leaking of C190, which is fairly rare, or worse than usual battery damage.  If there is visible damage to any tracks, these should be checked and repaired accordingly.  Most damaged tracks in this area will be picked up by the early chip memory test in ROM, which shows a green screen for chip memory failure.  Though this test isn't very thorough, it only does a simple write/read check at 16kB intervals.

There won't be soldering issues on the chip memory socket, but broken retaining clips or very dirty socket contacts are a possibility.  As others have said, you _MUST_ use a known good/working SIMM for chip memory, else you're chasing the unknown at this point.

The machine should run OK without fast memory.  But any fast memory access problems are usually caused by open circuit _R_W to pin 11 of the fast memory sockets and/or corrosion damage to U891 and/or damaged tracks/vias around U891.


Quote from: servitus;759847

Btw: When I replaced the Poly-Switch (F175) near the parallel-/serial-interface, I pulled out both VIA-connections :-/ Do you know if these are connected to an intermediate level of the multi-layered mainboard? I successfully bridged the lines on the upper- and lower-side, but I'll have a big problem if there are more connections inbetween... :-o



Why did you remove this for?  Anyway, one side of this connects to the internal +5V plane - specifically the side nearest U350.  The A4000D is a four layer board, the internal two layers mostly carry GND and +5V.  So measure it, and if the U350 side of F175 doesn't connect to +5V, then just run a small jumper on the bottom side of the board to the nearest convenient +5V source, which is practically everywhere.  If this connection is damaged, you'll just have no +5V_USR, so essentially you'll lose mouse movement.  The computer will boot fine without it.


If you can't resolve the issues yourself, feel free to contact me for a repair estimate.
http://amiga.serveftp.net
 

Offline spirantho

Re: Trying to call my A4000D back to life
« Reply #14 on: March 10, 2014, 10:38:15 PM »
I meant how does it run with the A4000 ROMs and no fast RAM? Very unlikely indeed it's your ROMs at fault.
--
Ian Gledhill
ian.gledhill@btinternit.com (except it should be internEt of course...!)
Check out my shop! http://www.mutant-caterpillar.co.uk/shop/ - for 8-bit (and soon 16-bit) goodness!