Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

N2630 is not compatible with Agnus 8371 #20

Closed
coriolis1986 opened this issue Nov 11, 2023 · 5 comments
Closed

N2630 is not compatible with Agnus 8371 #20

coriolis1986 opened this issue Nov 11, 2023 · 5 comments

Comments

@coriolis1986
Copy link

Hi all.

Just tried to run my A2000 with N2630 and Agnus 8371. It crashes with an old firmware. I reflashed U600-U602 to latest versions and my Amiga just refuse to start anymore.

@LIV2
Copy link
Collaborator

LIV2 commented Nov 12, 2023

Hi @coriolis1986

Did you previously have an 8372 fitted and did it work with the N2630 in this machine?

If you did swap from an 8372 to 8371 did you also change J101 to match this and close J500?

What version of Kickstart are you using and do you have the 68000 installed in the motherboard?

@coriolis1986
Copy link
Author

The original configuration of this A2000 has an 8371. I replaced it for a 8372, which I took out from Amiga 500. And N2630 works perfectly after this.

I have a Kickstart switcher (1.3, 2.04, 3.1, 3.2.1) and any of them works with an accelerator. Also the 68000 installed in the motherboard.

Both of the 8371 and 8372 works with 68000.

So only when the Agnus is changed, N2630 started or stopped to work.

I'll try to look to the jumpers on motherboard (ver 4.4). May be some of them will change the situation.

@jasonsbeer
Copy link
Owner

jasonsbeer commented Nov 14, 2023

Does your board have the 1 meg chip RAM mod? (Sorry, LIV2 asked this already) Testing team reports 8370 (NTSC version of 8371) works with the N2630 in a Rev 6 board.

@jasonsbeer
Copy link
Owner

@coriolis1986 Any additional information?

@jasonsbeer
Copy link
Owner

The testing team was not able to reproduce this situation. Unless further information surfaces, there is not enough information to act upon. Open again if additional information surfaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants