I have an amiga 4000 D /040 and yesterday I tried to upgrade the ROMs to 3.2.2 . I used chip 29F1615, 27c800, and 27c400 all attempts failed to boot. The power led was flashing. I put back the original 3.0 ROMs and still didn't boot (but the led was not flashing). Then I used diagROM and not only did it work but it passed all tests! I really don't understand why this is happening. I used the right sockets for Hi and Low, double checked that it was correct! I am thinking that maybe I damaged the ROM sockets when I removed the original ROMs, but then how does the diagROM works and passes all Tests?
Problem with updating my amiga 4000 to 3.2.2 ROMs
- Thread starter Nek3d
- Start date
- Replies 21
- Views 1017
May help to post pictures up of both the mainboard and close up of the sockets and the chip pins. Plus how you are fitting the chips in the board.
You have made sure that the ROM chip pins are seating correctly in the sockets? Good firm push etc..?
This is where the photos come in. You could try that option. But I and others don’t know (Except from your description) what condition both your sockets and chips are in……
I will take photos to show you the parts involved. But can you explain how the diagROM worked and all tests were successful? All other roms I tried including the original 3.0 failed to boot. And do you know what error code is 7 flashes of the power led?
AFAIK there is no 7 LED flash error code on any Amiga. You are most probably seeing a software failure (which does flash the LED over 5 times) culminating in a reset and/or a Guru Meditation error displayed on-screen.
Check the on-screen colour sequence when you first switch on the A4000. The colours denote various checks and balances before everything boots up.
The following colours are valid for all versions of AmigaDOS since Kickstart 1.3. However, there were several more colours in 1.3 compared to anything included after Kickstart 2.0 was released. All of the colours listed below are the same for all versions of Amiga kickstart.
The system performs the following test sequence:
1. Delays beginning the tests a fraction of a second to allow the hardware to stabilize.
2. Jumps to ROM code in diagnostic card (if found)
3. Disables and clears all DMA and interrupts.
4. Turns on the screen.
5. Checks the general hardware configuration.
If the screen remains a light grey colour and the tests continue, the hardware is OK.
If an error occurs, the system halts.
6. Performs checksum test on ROMs.
If the system fails the ROM test, the screen display turns red and the system halts.
When the Amiga is first switched on the keyboard might blink a number of times to indicate one of the following errors.
Check the on-screen colour sequence when you first switch on the A4000. The colours denote various checks and balances before everything boots up.
The following colours are valid for all versions of AmigaDOS since Kickstart 1.3. However, there were several more colours in 1.3 compared to anything included after Kickstart 2.0 was released. All of the colours listed below are the same for all versions of Amiga kickstart.
- Red - An error in the Kickstart rom as detected.
- Green - An error in the Chip Ram was detected.
- Blue - An error in the custom chip set was detected.
- Yellow - The CPU encountered an error before the system's error-trapping code (the code the calls up the Guru) was in place.
- Black - No CPU detected.
- Grey - CPU Passed the test.
- White - CPU failure.
The system performs the following test sequence:
1. Delays beginning the tests a fraction of a second to allow the hardware to stabilize.
2. Jumps to ROM code in diagnostic card (if found)
3. Disables and clears all DMA and interrupts.
4. Turns on the screen.
5. Checks the general hardware configuration.
If the screen remains a light grey colour and the tests continue, the hardware is OK.
If an error occurs, the system halts.
6. Performs checksum test on ROMs.
If the system fails the ROM test, the screen display turns red and the system halts.
When the Amiga is first switched on the keyboard might blink a number of times to indicate one of the following errors.
- One Blink = ROM Checksum failure
- Two Blinks = RAM test failed
- Three Blinks = Watchdog timer failed
- Four Blinks = A short exists between two row lines or one of the seven special keys (not implemented)
The code for diagrom is less than a genuine ROM and , if the fault is on one of the address lines for addresses above the end of the Diagrom code , then diagrom will run fine .
Thanks for all the info, I just wanted to ask if by "keyboard blinking" you mean the CAPS Lock on the amiga 4000 keyboard.
Yes
I tested it with my original a4000 keyboard but there was no blink. Does that mean something? Also when I boot with any ROM set (except from diagROM which works) I don't see any color on screen, It looks like it's not turned on.
If the power LED is flashing, the Rom is loading since that flashing comes from a Rom routine.
The 4000 is not happy about something else. E.g. bad connections to the CPU board, memory or any socketed chips like Buster.
Try reseating all chips etc...
The Diagrom for example does not need Ramsey or Buster to work.
Olli.
The 4000 is not happy about something else. E.g. bad connections to the CPU board, memory or any socketed chips like Buster.
Try reseating all chips etc...
The Diagrom for example does not need Ramsey or Buster to work.
Olli.
Thanks for the info Olli, the strange thing is that when I put the original 3.1 ROMs, the power Led doesn't flash, when I try the 3.2.2 it flashes!
The machine was working perfectly with the original 3.1 ROMs. It booted very fast from an SD adapter connected on the mobo's IDE port. Once I removed the ROMs to put the ones I burned, no configuration boots! But when I put the diagROM it runs and passes all tests! The truth is that a couple of times it didn't detect the 16mb fast ram, so I reseated the simms and diagROM registered the ram correctly. But even then when I put the 3.2.2 ROMs, the power Led flashes and nothing happens!
The problem seems to lie with your Kickstart 3.2.2 ROM chips. This is the only thing that has changed in the system.
I think you have to troubleshoot the original 3.1 configuration to get it working reliably.
Like I said, the Diagrom boots even without the Buster, Ramsey or IDE working. Even with slightly bad Chipram, the DIagrom might boot.
If no success with the original 3.1, you might want to try the 3.2.2 Roms for A1200 to see if you get the boot screen or early startup menu (all peripherals and boot drives removed).
A1200 Roms will boot on an A4000 even if Buster/Ramsey or IDE are not working.
Olli.
Like I said, the Diagrom boots even without the Buster, Ramsey or IDE working. Even with slightly bad Chipram, the DIagrom might boot.
If no success with the original 3.1, you might want to try the 3.2.2 Roms for A1200 to see if you get the boot screen or early startup menu (all peripherals and boot drives removed).
A1200 Roms will boot on an A4000 even if Buster/Ramsey or IDE are not working.
Olli.
This seems reasonable to me, but then what did I mess up and the original setup (3.1 ROM) is not working? Maybe the sockets got damaged when pulling the chips out?
I burned 3 different sets of 3.2.2 ROMs (using chip 29F1615, 27c800, and 27c400) so I am thinking that with so many pulls, maybe the ROM sockets are the culprit. The diagROM works because it's much smaller than the ROMs and maybe not using the addresses that are off...
Just out of a matter of interest. You have programmed the correct ROMs? I.e NOT 4000T or A1200 versions?
The A4000D uses different modules.
The A4000D uses different modules.
yes, it was the first thing I checked when it didn't boot!
Similar threads
