Amiga A4000T fails to boot

[leericmarvin]

My Amiga A4000T fails to boot.  I cannot get the "BIOS" screen when I hold both mouse buttons down.
I checked Power Supply voltages going into mother board and all look good.  
The 68040 CPU does warm up to 100 degrees or so.  I removed and reseated the CPU chip.  Have not done same to A3640 daughter board yet, as the standoff posts need to be undone.
I'd like to suspect the CPU and replace that first.  Would folks agree this the next best step?   Chip:   XC68040HRC25M
 
Are there any sources for old CPU chips?
 
Thanks,  LeEric Marvin   leeric@ak.net

[fitzsteve]

In my experience the CPU it's self is not normally the cause of issues, unless you ran it without a heatsink and it was under high load for a long period of time I'd say your issue is almost certainly elsewhere.

Common issues include capacitor leakage, particularly on the A3640, I would suggest finding someone to service the Motherboard and A3640.  I would suggest trying to get your hands on a cheap A3630 for testing purposes, this will rule out any issues with the Motherboard.

The early boot screen wont tell you much for fault finding however your screen might display some colours, this is like the POST in a modern PC, check this list:  (Look for the ones I put in BOLD)

GURU CODES

General error codes

01 - Not enough memory
02 - Couldn't make library
03 - Can't open library
04 - Can't open device
05 - Can't open resource
06 - I/O error
07 - No signal
08 - Bad parameters
09 - Close library failed: usually too many closes
0A - Close device failed: or a mismatched close
0B - Process creation failed

Specific Alert Codes

EXEC Library
0001 - 68000 exception vector checksum (obs)
0002 - Execbase checksum bad (obs)
0003 - Library checksum failure
0005 - Corrupt memory list detected in FreeMem
0006 - No memory for interrupt servers
0007 - InitStruct() of an APTR source (obs)
0008 - A semaphore is in an illegal state of Rem Semaphore()
0009 - Freeing memory that is already free
000A - Illegal 68K exception taken (obs)
000B - Attempt to reuse active OIRequest
000C - Sanity check on memory list failed during AvailMem (MEMF_LARGEST)
000D - IO attempted on close IORequest
000E - Stack appears to extend out of range
000F - Memory header not located. Usually an invalid address passed to FreeMem
0010 - An attempt was made to use the old message semaphores
00FF - A quick interrupt has happened to an uninitialised vector

CPU Exceptions
0002 - Bus Error
0003 - Addressing error
0004 - Illegal instruction
0005 - Divide by zero
0006 - CHK instruction
0007 - TRAPV instruction
0008 - Privilege violation
0009 - Trace
000A - OpCode 1010
000B - OpCode 1111
000E - Stack frame format error
0018 - Spurious interrupt error
0019 to 001F - AutoVector Level 1 to 7 int error

Intuition Library
0001 - Unknown gadget type
0002 - Create port, no memory
0003 - Item plane alloc, no memory
0004 - Sub alloc, no memory
0005 - Plane alloc, no memory
0006 - Item box top 0007 - Open screen, no memory
0008 - Open screen, raster alloc, no memory
0009 - Open sys screen, unknown type
000A - Add SW gadgets, no memory
000B - Open window, no memory
000C - Bad Stare Return entering Intuition
000D - Bad message received by IDCMP
000E - Weird echo causing incomprehension
000F - Couldn't open the Console Device
0010 - Intuition skipped obtaining a sem
0011 - Intuition obtained a sem in bad order

Graphics Library
0000 - Graphics out of memory
0001 - MonitorSpec alloc, no memory
0006 - Long frame, no memory
0007 - Short frame, no memory
0009 - Text, no memory for TmpRas
000A - BitBitMap, no memory
000B - regions, memory not available
0030 - Make V Por, no memory
000C - (GFX New Error)
000D - (GFX Free Error)
1234 - Emergency memory not available
0401 - Unsupported font description used

Workbench
0001 - No fonts
0001 - WB Bad Startup Msg1
0002 - WB Bad Startup Msg2
0003 - WB Bad IO Msg
0004 - WB Init Potion Alloc Drawer
0005 - WB Create WB Menus Create Menus1
0006 - WB Create WB Menus Create Menus2
0007 - WB Layout WB Menus Layout Menus
0008 - WB Add Tool Menu Item
000A - WB InitTimer
000B - WB Init Layer Demon
000C - WB Init WB Gels
000D - WB Init Screen and Windows1
000E - WB Init Screen and Windows2
000F - WB Init Screen and Windows3
0010 - WBMAlloc

Layers Library
0000 - Layers out of memory

Expansion Library
0001 - Freed free memory

Trackdisk Device
0001 - Calibrate: seek error
0002 - Delay: error on timer wait

Disk Resource
0001 - Get unit: already has a disk
0002 - Interrupt: no active unit

RamLib Library
0001 - Overlays are illegal for library segments

Console Device
0001 - Console can't open initial window

Timer Device
0001 - Bad request
0002 - Power supply: no 50/60 Hz ticks

Bootstrap
0001 - Boot code returned an error

Dos Library
0001 - No memory at startup
0002 - EndTask didn't
0003 - Qpkt failure
0004 - Unexpected packet received
0005 - Freevec failed
0006 - Disk block sequence error
0007 - Bitmap corrupt
0008 - Key already free
0009 - Invalid checksum
000A - Disk error
000B - Key out of range
000C - Bad overlay
000D - Invalid init packet for CLI/SHELL

Alert Objects
8001 - ExecLib
8002 - GraphicsLib
8003 - LayersLib
8004 - Intuition
8005 - MathLib
8007 - DOSLib
8008 - RAMLib
8009 - IconLib
800A - ExpansionLib
800B - DiskfontLib
800C - UtilityLib
800D - KeyMapLib
8010 - AudioDev
8011 - ConsoleDev
8012 - GamePortDev
8013 - KeyboardDev
8014 - TrackDiskDev
8015 - TimerDev
8020 - CIARsrc
8021 - DiskRsrc
8022 - MiscRsrc
8030 - BootStrap
8031 - Workbench
8032 - Diskcopy
8033 - GadTools
8035 - Unknown

Keyboard Caps Lock light

1 Flash = ROM (internal to keyboard processor)
2 Flashes = RAM (internal to keyboard processor)
3 Flashes = watchdog timer (IC 741s 123 or associated circuitry)
4 Flashes = A shortcut exists between two row lines or one of the seven special keys (not implemented), thanks for that Juv!    
No Flashes = Main PCB fault

Amiga 1200 & 4000 Screen Colours

Colour Black:                                      Opening Screen  Initial hardware configuration passed. Initial system software passed.  Final initialisation test passed

Colour Red:                        ROM error, reseat or replace Kickstart ROMs

                                                                            Colour Green:                     CHIP RAM error

                                                                              Colour Blue:            Custom Chip(s) error

                                                                            Colour Yellow:                    68000 detected error before  software trapped it (software or hardware error)

AmigaDos Error Codes

Displayed in CLI or Shell
103 - No free store
105 - Task table full
114 - Bad temlate
115 - Bad number
116 - Required arg missing
117 - Key needs arg
118 - Too many args
119 - Unmatched quotes
120 - Line too long
121 - File no object
122 - Invalid resident library
201 - No default dir
202 - Object in use
203 - Object exists
204 - Dir not found
205 - Object not found
206 - Bad stream name
207 - Object too large
209 - Action not known
210 - Invalid component name
211 - Invalid lock
212 - Object wrong type
213 - Disk not validated
214 - Disk write protected
215 - Rename across devices
216 - Directory not empty
217 - Too many levels
218 - Device not mounted
219 - Seek error
220 - Comment too big
221 - Disk full
222 - Delete protected
223 - Write protected
224 - Read protected
225 - Not a DOS disk
226 - No disk
233 - Is soft linked
234 - Object linked
235 - Bad hunk
236 - Not implemented
240 - Record no locked
241 - Lock collision
242 - Lock timeout
243 - Unlock error
303 - Buffer overflow
304 - ***Break
305 - File not executable        

Good luck.

[leericmarvin]

This happened after a power glitch which rebooted the cableTV and cable modem systems here in my house. The Amiga is plugged into a surge protector.
 
 
OK, I have reseated the A3640 card.    I also knocked memory down to one stick and swapped through all 4 sticks and repeating boot attempts with each.  I also removed all expansion cards and devices plugged in not necessary to get to the "BIOS", (kickstart screen?) I am trying to remember the proper terminology for it.
 
What are odds the Kickstart ROMS are damaged?
 
Thanks,  LeEric Marvin  leeric@ak.net

[Oldsmobile_Mike]

This might be obvious but have you reseated your Kickstart chip already?  Check around the edges of the caps for any leakage?

[leericmarvin]

OK, now I am really embarrassed...  I have discovered the RGB cable to the monitor is foobar.  So until I get that replaced or repaired, I am in the blind.
 
Are there any sources theses days for a 23pin to 9 pin RGB cable?  
 
LeEric Marvin  leeric@ak.net

[Erol]

I have an A4000T as well,  I gave Amiga hardware database a copy of the manual which you should follow.

http://www.bigbookofamigahardware.com/bboah/media/manuals/A4000T.pdf

what do you have installed in the system Hardware wise?

I've had this problem before but cannot clearly remember if it was the IDE/SCSI card is not firmly inserted. Re-seat the Processor card as the A4000T is temperamental if this is not firmly installed. Clean the connectors with a cotton bud and cleaning fluid.

Check your jumpers also on the motherboard see section C3 in manual.  there jumpers for the processor card. (page44)

Unplug all your hardware but leave the sound & scsi/ide installed and memory and also the floppy drive.

Make sure you are firmly grounded and power is unplugged as that case will fry your board.  

Let me know how you get on.

[Erol]

 
Are there any sources theses days for a 23pin to 9 pin RGB cable?  
 
LeEric Marvin  leeric@ak.net

http://www.vesalia.de/e_amigamonitorcables%5B6251%5D.htm

You need to check if its male or female..

Amigakit.co.uk  also sale them but you have to check with them for stock.

http://amigakit.leamancomputing.com/catalog/index.php?cPath=21_72

[danbeaver]

Check eBay for the cable as they come up often for sale. Also put a WTB in the Marketplace forum here and on Amibay.

[mechy]

OK, now I am really embarrassed...  I have discovered the RGB cable to the monitor is foobar.  So until I get that replaced or repaired, I am in the blind.
 
Are there any sources theses days for a 23pin to 9 pin RGB cable?  
 
LeEric Marvin  leeric@ak.net

inside the usa:

http://www.bestpricecables.com/6ft-grey-amiga-monitor-cable-with-db-23-female-to-db-9-male-connectors.html

or here:

http://www.connectworld.net/cgi-bin/ccc/process?Ld2Rx3vh;;1

[Oldsmobile_Mike]

inside the usa:
 
http://www.bestpricecables.com/6ft-grey-amiga-monitor-cable-with-db-23-female-to-db-9-male-connectors.html
 
or here:
 
http://www.connectworld.net/cgi-bin/ccc/process?Ld2Rx3vh;;1

 
Well that's pretty neat!  I like the description for the "inside the USA" part.  You can tell someone was a fan.    The other link comes back as "error", BTW.

[mechy]

Well that's pretty neat!  I like the description for the "inside the USA" part.  You can tell someone was a fan.    The other link comes back as "error", BTW.

the link was right, something funny about searched links on that site-hmm.if  goto the homepage, hit search,then type in AMIGA and it will bring all amiga cables up.

http://www.connectworld.net

[leericmarvin]

Ami is back up and running.   I'd like to thank Amigamech who emailed me and help me think straight.  Also those who provide links and troubleshooting steps my way.
 
I managed to jerryrig a fix on the video cable, but still wouldn't boot. tried various things, but finally removed my 3 SCSI drives one at a time until the computer booted.  Seems a bad SCSI drive can drag things down and prevent booting.  Fortunately, it wasn't the boot drive that was bad, so it booted up OK when the culprit was removed.
 
I have two new DB23M to DB9M cables on order.  
 
I also ordered up a SainSmart GBS-8220 RGB/CGA/EGA/YUV to VGA HD video converter.  Plan to wire up one of the 2 cables to this and see if I can finally output to a VGA LCD monitor.  It's really getting old seeing everything on the ole 1084S monitor.
 
Thanks,  LeEric