16 July 2024, 02:08 | #741 |
Registered User
Join Date: Jun 2023
Location: New Zealand
Posts: 11
|
I thought you mightve been onto something for a minute there, as I had been wondering along similar lines. But alas pin 2 (pin1 on the 40pin socket) is connected to where it's supposed to be on the CPU. The A2000 does have a 2.04 mask rom in it so not likely a problem there. I guess I should retrieve that chip and sanity check it in the A500 as well.
Have been using the A500 for Rom testing since is much easier to get at the chip. :Edit: With a bizarre twist, the 2.04 mask ROM works fine in the A500, I figured I'd test a 3.2 in the A2000 again while the drive tray was out.. and it kindof works?! but is unstable as heck, like most of the time Guru's within a few seconds on the kickstart screen. Same chip that only gives a red or yellow screen on the A500. No I'm just even more confused than I was before ?? do I just have 2 machines that are rock stable on older but not on 3.2 Last edited by 3VILC; 16 July 2024 at 05:24. |
16 July 2024, 09:28 | #742 |
Registered User
Join Date: May 2022
Location: UK South East
Posts: 85
|
hmmm, I'm out of ideas then. I would be cleaing socket and pins, they are not getting any younger! I dont have a functioning A500, but I guess I could try your bin file in my A600 if you want to send it to me.
|
17 July 2024, 00:11 | #743 |
Registered User
Join Date: Jun 2023
Location: New Zealand
Posts: 11
|
I guess it couldn't hurt to verify my file/programmer isn't the issue, if you have some 27c800 kicking around.
I tried DiagROM in the A2000 again and learned that ram on the A2091 that I had to disable because it random started making the machine not boot, is actually because it generates a "bus error" when its enabled, so wonder if theres some dying bus logic also playing a role in later kickstarts not working properly as well. Might start up a new thread on that |
18 July 2024, 14:35 | #744 |
Registered User
Join Date: Jun 2023
Location: New Zealand
Posts: 11
|
Posting solution here incase it helps someone else. Even though I had already tried this, I tried again with some of the newer burns.. if using 27C800s in 40pin sockets, pin 1 must be pulled to ground. I had read somewhere it shouldn't be much issue if the image is duplicated it doesnt matter which half is being addressed, but clearly it is an issue. Pulling the pin to ground works every time in both machines.
Insanity check, I grabbed one of the chips I had burned earlier and that did not work still..so I was obviously thrown a red herring with a burn that just didn't work at all to begin with |
18 July 2024, 14:49 | #745 |
Registered User
Join Date: May 2022
Location: UK South East
Posts: 85
|
Glad you sorted it.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problems with 3.1 kickstart in WHDload | zap64uk | project.WHDLoad | 7 | 30 March 2010 00:23 |
Burning Kickstart Roms | clueless | Hardware mods | 8 | 06 January 2010 13:31 |
Kickstart problems... | asm1 | project.WHDLoad | 2 | 14 March 2009 15:29 |
Problems with Kickstart 3.1 [was: various posts in a thread in News] | ARTHUR071169 | project.GameBase Amiga | 33 | 15 October 2006 13:33 |
Kickstart 3.1 problems | adgloride | support.Hardware | 5 | 08 June 2004 03:57 |
|
|