Giter Club home page Giter Club logo

Comments (25)

jasonsbeer avatar jasonsbeer commented on June 8, 2024 1

No worries @jasonsbeer I've had a look and it looks good to me!

Thanks, Matt!

from amiga-2000-eatx.

texneus avatar texneus commented on June 8, 2024 1

I'm going to reopen this as I think there are ways to eliminate jumpers that are worthy of further discussion, and personally I would like to see this as one board layout for a variety of reasons including those already discussed. Focusing on 2Mb SRAM only and spring boarding of some schematics created earlier by @jasonsbeer, the following gets us down to "only" 14 jumpers and (assuming my eyes didn't get crossed somewhere) this should work with either Agnus.

This particular design takes advantage of the fact that most of the Agnus RAM address lines (DRA0-9) are still address signals even though they are not in the same place between Agnus chips. In the end, the SRAM won't care as long as it's addressed consistently. In 1Mb mode A0 is logical 0 at all times, effectively allowing only half of the 2Mb SRAM to be addressed. The other addresses lines are skewed as shown on the second sheet. For 2Mb all address lines line up. Feel free to review and point out the error of my ways.

Also, at least one jumper (at the bottom of the first sheet) is redundant and can be removed. The silk screen could be changed to "Short for NTSC or 8375 Agnus".

Please excuse the crudity of these drawings, I did not have time to paint it or build it to scale...I will learn KiCAD at some point, but until then I will do layouts like its 1989 :-)

I have not looked at other jumpers yet but there are probably opportunities to reduce these further as well.

sheet1
sheet2

(edited for grammar)

from amiga-2000-eatx.

LIV2 avatar LIV2 commented on June 8, 2024

No worries @jasonsbeer I've had a look and it looks good to me!

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

Will it be backwards compatible with a 1 MB Agnus, even with the 2 MB SRAM? I.e. will the uppermost address line to the SRAM be a constant during access?

If so, you could build a 2 MB board, and then go searching for the 2 MB Agnus sometime later. This is especially relevant if someone makes up a batch of boards without the custom chips.

If not, would it be hard to add a jumper for forcing it to only see 1 MB of the SRAM?

from amiga-2000-eatx.

jasonsbeer avatar jasonsbeer commented on June 8, 2024

Will it be backwards compatible with a 1 MB Agnus, even with the 2 MB SRAM? I.e. will the uppermost address line to the SRAM be a constant during access?

If so, you could build a 2 MB board, and then go searching for the 2 MB Agnus sometime later. This is especially relevant if someone makes up a batch of boards without the custom chips.

If not, would it be hard to add a jumper for forcing it to only see 1 MB of the SRAM?

I have been thinking a lot about this concept. Unfortunately, the 8375 is not pin compatible with the 8372A. By quick count, there are 21 signals on a different pin. Using a single board to support both versions would require a considerably large field of jumpers and a mess of traces to make it work. This would take a lot of rework to implement, but I certainly agree a single board approach is preferable. I will see what I can do.

from amiga-2000-eatx.

jasonsbeer avatar jasonsbeer commented on June 8, 2024

In order to explore a single board to support both 8372A and 8375...I worked up the schematics. I ended up with 34 jumpers that would need to be configured to support either configuration. 21 to configure Agnus, and 12 to configure the SRAM. I call it the Insane Jumper Edition. I'll upload it to the dev branch if anyone gets a desire to check it out. I do not intend to follow that path any further at this time.

Edit: Might make more sense to just use a different SRAM chip than try to leverage the same one for both Agnus versions. That might help...I'll keep thinking.

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

What about two sockets? Could you make enough room to place them side by side, and you only populate one?

from amiga-2000-eatx.

LIV2 avatar LIV2 commented on June 8, 2024

It might be possible to fit two sockets, perhaps if the footprints were overlapping but offset diagonally by 1.27MM (kinda like I did on my A500 8375 adapter).
I wouldn't recommend this though, adding dual sockets/footprints will result in stubs for every signal going to Agnus which can result in instability and radiated noise.

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

Stubs won't be an issue at this clock frequency, they will just add a tiny lumped capacitance. (The capacitance of the traces on the four-layer ATX version will be completely different to the original.) The Agnus is 30 years old, and the original B2000 board was two layers and used 1 kOhm terminations.

The two-socket PCB would be an alternative to the Mini Megi style of adaptor, and those ran an address line over a twisted pair.

Here's one for comparison, on a real rev 6.2 board: https://www.ebay.com.au/itm/203532038100

from amiga-2000-eatx.

jasonsbeer avatar jasonsbeer commented on June 8, 2024

I am working with @texneus on this. We have a couple options we are evaluating. Stay tuned.

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

On my A500, I remember doing a mod for 1 MB chip instead of 512k chip and 512k pseudo-fast. IIRC that was a jumper implemented as three pads and a track between two of them, I had to cut the track and bridge the other two. (Forgive me if that's not quite right, it was in the early '90s!)

Such an approach, defaulting to the 1 MB Agnus, would make almost everyone happy. And it would be period-correct! :)

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

I also wonder, in relation to that 512k chip and 512k pseudo-fast. Was this done to allow boards with the older Agnus to address 512k of chip, while allowing the CPU to address the rest? Can this approach work with 2 MB of SRAM, and a 1 MB Agnus?

Or was it only ever possible to do that with a 1 MB Agnus, and they downgraded it for other reasons?

from amiga-2000-eatx.

LIV2 avatar LIV2 commented on June 8, 2024

@texneus that's clever! Very nice

I also wonder, in relation to that 512k chip and 512k pseudo-fast. Was this done to allow boards with the older Agnus to address 512k of chip, while allowing the CPU to address the rest?

Yes the older Agnus' internal registers could only make use of 512K Chip but the memory controller portion could address up to 1MB which allows the CPU access the slow ram

Presumably even when they came out with the 1MB Agnus they left it defaulting to 512K chip / 512K slow to ensure compatibility with existing software that might have assumed that configuration

Can this approach work with 2 MB of SRAM, and a 1 MB Agnus?

Unfortunately not. 1MB Agnus only has enough address inputs for 1MB so the memory controller can't address more than that.

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

Oh well. So, how about a jumpered configuration as per @texneus, but done using 0603 0R resistors? And including a default configuration of 1 MB, implemented using thin tracks that will be easy to cut.

If, at some point in the future, you're fortunate enough to get a 2 MB Agnus, you just install the 0R resistors (or solder blobs) across the pads that are not shorted, and then cut those tracks. It should be easy enough to get the resistors on the right pads, by making sure you can still see the tracks that you need to cut.

from amiga-2000-eatx.

jasonsbeer avatar jasonsbeer commented on June 8, 2024

Just to add some info to the schematics texneus uploaded. I drew up a symbol that would cover both Agnus versions in question (8375 and 8372A). On the symbol, you will see some pins identified with slashes in the name. These are (probably obviously) the pins that differ between the two versions of Agnus. The format is [8375 Signal]/[8372A Signal].

You guys can double check I drew it up correctly, as well.

from amiga-2000-eatx.

jasonsbeer avatar jasonsbeer commented on June 8, 2024

@texneus I have included your changes in the schematics. You can review the attached files for accuracy. The schematics you had were an older version, so these might look slightly different, but all the signals are there.

Agnus Multi Adapter.pdf
Memory and Kickstart.pdf

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

Some notes on the above PDFs.

  • you should annotate the schematic, on each of those sheets, to say that the jumper default configuration is for the 8375.
  • you should annotate the schematic, near Agnus, with the fact that the left pin-name is the 8375, the right pin-name is the 8372A.
  • how serious is it, if J102 is not installed, for the 8375? Perhaps you should add a three-way jumper like the rest, just so the person doing the mod will recognise it and install a permanent ground?
  • it's not clear which of the DRA lines is going to JA11
  • JA6 has one side going nowhere, is this a mistake?
  • JA7 is a two-pad jumper, while the rest are all three-pads. This invites mistakes, maybe make it three pads and add a does-nothing track that you can cut, just so people have a simpler recipe to follow?
  • you might rename DRA0 to DRA0-GND, as that's easier to understand on the memory sheet.

Also, I suggest that the 8372A be the default, because those are way more common. For testing a production run of boards, you're more likely to test with the common chip before shipping them out. (PLCC pins do get bent inwards if you do this often enough.) Right now, the price difference on eBay is about $100 vs $40.

from amiga-2000-eatx.

texneus avatar texneus commented on June 8, 2024

@jasonsbeer - on the original Memory and Kickstart schematic, was the _MRAS1 signal latched by RAS (top latch here)? This should match your rev 1.2 schematic. Just swap DRABx/DRAB0 at each latch if necessary. Otherwise no issues that I see.

@darrenfreeman - definitely more work is needed on nomenclatures and making this user friendly. At the moment I'm concentrating on eliminating as many jumpers as possible as part of "user friendly". I won't have time to look at the rest for a few days but I'm not sure anything else will give way quite so easily, although I do have a few ideas in the back of my head. In the mean time keep the suggestions coming, we'll get to them soon enough!

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

This was news to me - there are (at least) two different pin-outs for the 8375, depending on the CBM part number. It will not be sufficient to call the chip "8375". That designation should be dropped, going forwards, as baffling and inconvenient as this is.

https://www.amigawiki.org/lib/exe/fetch.php?media=de:parts:agnus-history.pdf

From my reading, the A3000 used a 2 MB Agnus, with a similar pinout to the 1 MB Agnus of the A500/A2000. The A500 Rev 8a, A500+, and A600, use the modified pinout that requires all these jumpers.

I think we can support all the 1 and 2 MB parts, it will just require a table of jumper settings for each CBM part number. Perhaps it can go on the bottom silk screen, with all the jumpers.

from amiga-2000-eatx.

LIV2 avatar LIV2 commented on June 8, 2024

The 2MB A3000 Agnus is practically unobtainable though

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

According to this thread, the A500 Rev 8a had the A3000 version, while the A500+ (same motherboard, different components) had the A600 version.

http://eab.abime.net/showthread.php?t=52072

So it will be interesting to look at the schematic for the Rev 8a, maybe we will find a lot of jumpers...

from amiga-2000-eatx.

darrenfreeman avatar darrenfreeman commented on June 8, 2024

I had a look, couldn't see anything related to that. Maybe the above thread is mistaken. Maybe the board didn't work, because someone put the wrong part on it.

from amiga-2000-eatx.

jasonsbeer avatar jasonsbeer commented on June 8, 2024

This was news to me - there are (at least) two different pin-outs for the 8375, depending on the CBM part number. It will not be sufficient to call the chip "8375". That designation should be dropped, going forwards, as baffling and inconvenient as this is.

CSG was really sloppy with its naming conventions of the 2MB Agnus chips. As you point out, not all 8375 Agni are pin compatible.

The A500+ and A600 schematics I'm using both show the same 8375 pinouts. As such, my base assumption is that all 8375 part numbers that appeared in the A500+ or A600 are pin compatible. This needs verification before final release to accurately enumerate the BOM.

EDIT: After further investigation, it seems 390544-xx part numbers are not compatible with the 318069-xx part numbers and some 318069-xx part numbers are not even compatible with each other. This whole thing is a mess. See https://www.amigawiki.org/lib/exe/fetch.php?media=de:parts:agnusliste_v09_120923.pdf It seems the 390544-xx part number only appears on the earliest revisions of the A500+ and A600? On some 318068-xx part numbers, pin 41 is VBB on some...I don't know the significance of that at the moment. Lots more homework to do here.

These are the part numbers that are under consideration...

PAL
318069-10
318069-19
390544-01

NTSC
318069-11
390544-02

from amiga-2000-eatx.

jasonsbeer avatar jasonsbeer commented on June 8, 2024

Guys, I apologize. This is such a mess. I found some additional info and update my table.

Here is a list of 8375 part numbers that I think we can support without going totally over the top. I would have to tweek existing jumpers, but not add any. Part 390544-01 is what I have been using on the schematics up to now.

Part Number PAL/NTSC Comment
390554-01 PAL 8375R0 Original Release
390554-02 NTSC 8375R0 Original Release
318069-10 PAL Differs from 390554-01, pin 40 is Vbb instead of 14MHz
318069-11 NTSC Differs from 390554-02, pin 40 is Vbb instead of 14MHz
318069-12 PAL New revision of 390544-01
318069-13 NTSC New revision of 390544-02
390544-01 PAL Pin compatible with 318069-10
390544-02 NTSC Pin compatible with 318069-11

This information is taken from https://www.amigawiki.org/lib/exe/fetch.php?media=de:parts:agnusliste_v09_120923.pdf, which has provenance. Anyone reading this is welcome to review this list. Let me know if you see any discrepancies.

Also referencing this: https://www.amigawiki.org/lib/exe/fetch.php?media=de:parts:agnus-history.pdf

from amiga-2000-eatx.

jasonsbeer avatar jasonsbeer commented on June 8, 2024

Good discussion here, everyone. I think this thread has gone as far as it could. The new board revision is routed and uses solder pad jumpers to configure the board for the Agni shown in my previous post.

from amiga-2000-eatx.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.