Welcome, Guest. Please login or register.

Author Topic: A500 Won't Recognize 3.1 ROM  (Read 4712 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline jammarobTopic starter

  • Newbie
  • *
  • Join Date: Jun 2012
  • Posts: 34
    • Show only replies by jammarob
Re: A500 Won't Recognize 3.1 ROM
« Reply #14 on: May 29, 2015, 01:43:16 PM »
Continuity checks ok.

I'm stumped.

At this point I think i'll just pick up another A500 :(
 

Offline ElPolloDiabl

  • Hero Member
  • *****
  • Join Date: May 2009
  • Posts: 1702
    • Show only replies by ElPolloDiabl
Re: A500 Won't Recognize 3.1 ROM
« Reply #15 on: May 29, 2015, 05:22:41 PM »
Check here. I'm sure the error code is in one of those old books.

http://www.bombjack.org/commodore/amiga-books.htm

Other than that, someone has gotten that error code after their battery leaked.
Go Go Gadget Signature!
 

Offline orange

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2796
    • Show only replies by orange
Re: A500 Won't Recognize 3.1 ROM
« Reply #16 on: May 29, 2015, 07:11:13 PM »
if not mentioned already in thread, you might need to add missing resistor pack, iirc its near CPU.
Better sorry than worry.
 

Offline Faerytale

  • Full Member
  • ***
  • Join Date: Sep 2007
  • Posts: 187
    • Show only replies by Faerytale
Re: A500 Won't Recognize 3.1 ROM
« Reply #17 on: May 29, 2015, 07:58:04 PM »
U forgot to install Microsoft Plug & Play drivers!
 

Offline paul1981

Re: A500 Won't Recognize 3.1 ROM
« Reply #18 on: May 29, 2015, 08:15:05 PM »
Is it different jumbled characters each time?
 

Offline DutchinUSA

  • Full Member
  • ***
  • Join Date: Feb 2012
  • Posts: 222
    • Show only replies by DutchinUSA
Re: A500 Won't Recognize 3.1 ROM
« Reply #19 on: May 29, 2015, 08:48:04 PM »
Orange, you talking about the following?: (forgot who wrote it but I cut & pasted it into an email to myself).

I had burned an EPROM (AMD AM27C400) with Kickstart 3.1 image for my A500+ but when I replaced the original ROM I got a red screen with flashing power LED. Very similar situation to the one described by orange.

The kickstart was the 40.063 version intended for A500/A600/A2000. I had verified the CRC-32 checksum before burning it. The image wasn't corrupted or modified. I had checked it with the SKick. Everything had worked fine.

With the CPU replaced by the turbo board (030 CPU) the kickstart booted correctly (I'm sure it wasn't a 020+ image because it had been soft-kicked earlier and had worked with the stock 68000 CPU, the EPROM was also verified if it contained the programmed data).

Strangely when my Action Replay III card was connected the kickstart booted correctly but required disabling of the cartridge (actually it was A2000 version of the Action Replay III connected through a bus board). I have burned another EPROM with the same data but the story repeats.

Then I started to suspect that something strange must be happening on the CPU bus. I noticed that the Action Replay card had pull-down resistros on the data bus but my rev 8A motherboard was missing data bus pull-ups. I populated the missing resistor packs (RP108 and RP110) but nothing happened. I tried both pull up and pull down configurations without success.

Then I started to measure signals at the CPU socket with my scope and found out that when I touched with a probe some low order address lines the power LED flashing stopped. The system hung. It was deterministic behaviour.

I realized that also low order address lines (A16-A1) were missing their pull-up resistor packs (RP106 and RP107) so I removed data lines pull-ups and moved them to low order address lines. Since that moment everything works flawlessly.

You can locate aforementioned missing resistor packs next to the CPU socket on the A500+ rev 8A motherboard.

I don't really know why it initially worked with the original mask ROM but didn't with the CMOS EPROM. One possible explanation is an input leakage current of the ROM/EPROM chip. The 68000 CPU was manufactured using NMOS technology with relatively weak sourcing current of high output state (0.4mA). According to the datasheet of the ROM chip its input leakage current is ten times larger than the one of the EPROM.

I hope someone will find my description helpful.

just to see if i understood this. you installed two resistor packs at RP106 and RP107 to make the "AMD AM27C400" eprom working. what are the types/specs of these resistor packs?

Yes, I installed two resistor packs (aka resistor networks or resistor ladders) as specified in the rev 8A schematics: 9 x 4k7 in SIP-10 package.

One of the suitable components is BOURNS 4610X-101-472LF. You can buy them at Farnell.
 

Offline Oldsmobile_Mike

Re: A500 Won't Recognize 3.1 ROM
« Reply #20 on: May 29, 2015, 08:51:01 PM »
^^^  That is some danged amazing troubleshooting, there.  Not sure if Rev 8A is comparable to his Rev. 5, but couldn't hurt to inspect if those components exist.  You sir, win the dancing banana award for the day!  :banana:
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 DutchinUSA

  • Full Member
  • ***
  • Join Date: Feb 2012
  • Posts: 222
    • Show only replies by DutchinUSA
Re: A500 Won't Recognize 3.1 ROM
« Reply #21 on: May 29, 2015, 08:57:21 PM »
That wasn't mine though :( and it was in reference to a burnt kickstart.

I have heard what Mechy mentioned before though .. certain rom speeds will be fine in one machine but will be too slow in another (same model and everything) .. weird but true :)
 

Offline jammarobTopic starter

  • Newbie
  • *
  • Join Date: Jun 2012
  • Posts: 34
    • Show only replies by jammarob
Re: A500 Won't Recognize 3.1 ROM
« Reply #22 on: May 29, 2015, 09:40:46 PM »
That is very helpful, thanks for that!

I'll get a hold of a logic probe and oscillator this weekend and start poking around the CPU.

It's certainly possible that one of these resistor packs could be faulty.
 

Offline jammarobTopic starter

  • Newbie
  • *
  • Join Date: Jun 2012
  • Posts: 34
    • Show only replies by jammarob
Re: A500 Won't Recognize 3.1 ROM
« Reply #23 on: May 31, 2015, 05:08:24 AM »
**UPDATE**

I couldn't figure out this revision 5 A500, so I picked up a revision 6A A500 from a local electronics junk store today.

None of the 10-pin resistor packs mentioned earlier are populated on this board. It would NOT recognize the 3.1 kickstart EPROM until I populated RP107 with a 9 x 47K resistor pack.

It now recognizes the kickstart and boots, but adding an A508IDE causes it to become unstable.

Does anyone have the values for RP106, RP108, RP110 on a revision 6A?
« Last Edit: May 31, 2015, 05:26:23 AM by jammarob »
 

Offline Oldsmobile_Mike

Re: A500 Won't Recognize 3.1 ROM
« Reply #24 on: May 31, 2015, 06:30:25 AM »
Quote from: jammarob;790245
I couldn't figure out this revision 5 A500, so I picked up a revision 6A A500 from a local electronics junk store today.

I'm impressed that they have "local electronics junk stores" in Texas that have Amiga parts!!!

I've got tickets to a tech event down there in Austin in September, anyplace you can recommend?

...btw, ripping my A500 apart in a few weeks for some upgrades.  It's a 6A, if you can't find those values before then I might be able to get them for you.  Not anxious about removing my VXL*30 though, haha.  ;)
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 jammarobTopic starter

  • Newbie
  • *
  • Join Date: Jun 2012
  • Posts: 34
    • Show only replies by jammarob
Re: A500 Won't Recognize 3.1 ROM
« Reply #25 on: May 31, 2015, 06:05:29 PM »
Yep! Unfortunately, they are about to permanently close. Everything is 80% off, so the A500 was pretty cheap.

https://www.youtube.com/watch?v=AIy__NX9SvQ
 

Offline mechy

Re: A500 Won't Recognize 3.1 ROM
« Reply #26 on: May 31, 2015, 06:34:15 PM »
Quote from: Oldsmobile_Mike;790251
I'm impressed that they have "local electronics junk stores" in Texas that have Amiga parts!!!

I've got tickets to a tech event down there in Austin in September, anyplace you can recommend?

...btw, ripping my A500 apart in a few weeks for some upgrades.  It's a 6A, if you can't find those values before then I might be able to get them for you.  Not anxious about removing my VXL*30 though, haha.  ;)

Lol, i am jealous, i am in texas and our junk stores have nothing amiga ever ;/
 I am in a small town though :)
 

Offline mechy

Re: A500 Won't Recognize 3.1 ROM
« Reply #27 on: May 31, 2015, 06:37:08 PM »
Quote from: jammarob;790163
That is very helpful, thanks for that!

I'll get a hold of a logic probe and oscillator this weekend and start poking around the CPU.

It's certainly possible that one of these resistor packs could be faulty.

when you burned the eprom,did you fill it completely, i.e. concatenate it to double it them burn it to the full 4mbit eprom... hope that makes sense?

if not,then iirc it may address the empty half or some such and not work.
 

Offline paul1981

Re: A500 Won't Recognize 3.1 ROM
« Reply #28 on: May 31, 2015, 09:44:23 PM »
Quote from: jammarob;790276
Yep! Unfortunately, they are about to permanently close. Everything is 80% off, so the A500 was pretty cheap.

https://www.youtube.com/watch?v=AIy__NX9SvQ


Wow!
 

Offline danbeaver

Re: A500 Won't Recognize 3.1 ROM
« Reply #29 from previous page: May 31, 2015, 10:06:23 PM »
Since this is still an Amigakit ROM (and we are on an Amigakit web site), do you really want to not involve them in an issue that really is in the realm of customer support?

I only point this out as this thread is heading towards its third page...