FPGA Replay Board

[Belial6]

Sure, that is why there is so much now.  At some point you have to say, this is enough for this model.  It would be great if we could have 128 petabyte, but 32 on the basic board and 128 with the daughter card is fine.  Delaying the boards to squeeze in a little more that still won't be "enough" would have been a mistake.

[wizard66]

Sure, that is why there is so much now.  At some point you have to say, this is enough for this model.  It would be great if we could have 128 petabyte, but 32 on the basic board and 128 with the daughter card is fine.  Delaying the boards to squeeze in a little more that still won't be "enough" would have been a mistake.

The mainboard hase 64MB installed.
So the mainboard (replay) and the daughterboard together give a grant total of 192MB.
Looks enough to me.

[freqmax]

Where is the statement that it's 64 MB onboard?, last update on that issue said 32 MB asfaik.

[AJCopland]

_just_ 32MB would be plenty for most Amiga software and games. It's only newer workloads that might need more.

[Derfs]

The mainboard hase 64MB installed.

from sig..

1x FPGA Replay v1.0B (main Amiga)

im willing to believe it has 64MB ;-)

[yakumo9275]

The things that would be awesome to me to emulate on this board dont even need 32 (c64, coco2/3, ti99, etc).

32mb? awesome. 64mb,128mb? not sure what I'd do with it!

[XDelusion]

Will this have audio delay issues with OctaMED Sound Studio like WinUAE does?

[mongo]

Where is the statement that it's 64 MB onboard?, last update on that issue said 32 MB asfaik.

Page 5 of the schematic.

http://www.fpgaarcade.com/common/fpgaarcade_replay_b01_schematic_a2.pdf

[TheGoose]

Will this have audio delay issues with OctaMED Sound Studio like WinUAE does?

Gosh I hope not. But any time you start doing something that is not a real Paula, seems trouble is not far behind. But this is actual hardware shaped into a Paula, not emulated. So should be good.

Feel I asked this before, but how does the minimig perform with OSS ?

[XDelusion]

I think there's a small collective of us who judge our Amiga experience by how well and how accurate OSS runs.

[Darrin]

Where is the statement that it's 64 MB onboard?, last update on that issue said 32 MB asfaik.

There is 64MB as Wizard said, and it can be configured in several ways:

CHIP:  0.5, 1.0, 1.5, 2.0
SLOW:  None, 0.5, 1.0, 1.5
FAST:  None, 2.0, 4.0, 8.0
XRAM:  None, 48MB FAST, 48MB CHIP

[amigadave]

There is 64MB as Wizard said, and it can be configured in several ways:

CHIP:  0.5, 1.0, 1.5, 2.0
SLOW:  None, 0.5, 1.0, 1.5
FAST:  None, 2.0, 4.0, 8.0
XRAM:  None, 48MB FAST, 48MB CHIP

Is this a new math where 48 + 48 = 64?

[Belial6]

32, 64, 128.  Pretty much anything over 8 is fine and increasing it wouldn't be worth any delay in production.

You can be sure that if the boards make Mike a profit, and people find that they need more memory than what is currently offered, there will be an FPGAArcade 2.

[Darrin]

Is this a new math where 48 + 48 = 64?

Where do you get 48+48?  It is an either-or.  You either have no XRAM, 48 MB or CHIP or 48MB of FAST.

Currently you can have a maximum of 2+1.5+8+48 selected = 59.5MB.  Just like on the Minimig I'm sure some RAM is required by the hardware itself and the amounts allocated it the menu are subject to change with core revisions.

[freqmax]

Seems Mikej upgraded to 64 MB. Anyway any hinderance to make use of the full 16 MB maximum the 68000 can address ?, the full control should make this possible.

I don't think there will be any audio delay issues with OctaMED or anything else unless Minimig also have such issue. An FPGA can work cycle exact. Something software can't do unless the realtime capability is sacrified. Or you can run the whole hardware simulation loop in less than a cycle of the emulated system.

[yaqube]

Seems Mikej upgraded to 64 MB.

The design can accept 32 or 64 MB memory chips but all the produced boards are populated with 64 MB. Frankly speaking I don't know why some people spread around false information about installed memory size.

Anyway any hinderance to make use of the full 16 MB maximum the 68000 can address ?

The TG68K in 68000 mode can access full 32-bit address space (like a real 68012 CPU) and use additional 48 MB of RAM. But because some programs  cause problems when running in this configuration I have decided to limit address space to 16MB when 68000 mode is selected. Full address space is accessible in 68020 mode.