Vampire 500 V2+ compatablity with other expansions????

[sim085]

It means a Vampire has been reserved for you. You should have had an email asking for payment so I would check your spam folder in case its in there.

Thanks will contact majista to see how to sort it out.

[psxphill]

An A2000 with a vampire and a 486 bridgeboard would be kinda awesome.
But a scsi card or 16 bit memory or even an Ethernet card is not quite like the issues a bridgeboard can have.

An A500 with a 486 pc emulation in the vampire FPGA would be awesome too. Although you probably couldn't fit both at the same time.

[OlafS3]

An A500 with a 486 pc emulation in the vampire FPGA would be awesome too. Although you probably couldn't fit both at the same time.

I think they already added commands to inprove emulation speed, one emulator is in development I think

[SamuraiCrow]

I think the only non-autoconfig part of the Vampire is the RAM  addition.  And the reason it's done that way is because the chipset  functionality is being slowly but methodically absorbed into the SAGA  core.  Would anyone care for 128 Megs of Chip RAM?

Seriously,  https://vimeo.com/206380147 shows the V500 working with a Picasso IV  graphics card in an A2000.  https://vimeo.com/206998554 shows a Vampire  system running Chocolate Heretic using a Prisma Megamix Z2 sound card.   Memory cards work with it too, as do SCSI controllers and other old Z2  expansions.

[SamuraiCrow]

I think they already added commands to inprove emulation speed, one emulator is in development I think

I think they were talking about hardware emulator boards like a Bridgeboard.

[OlafS3]

I think they were talking about hardware emulator boards like a Bridgeboard.

why on earth should anyone reimplement 486er in a Vampire FPGA? That is even more senseless than reimplementing PPC in FPGA

[ShK]

I think the only non-autoconfig part of the Vampire is the RAM  addition.

Actually autoconfig does works with Vampire fastmem if you update expansion lib on kick from 32bit Amiga. e.g. "expansion_40.2(A500-600-2000) -> expansion_40.2(A1200)".

[kolla]

Would anyone care for 128 Megs of Chip RAM?

Ideally, all the RAM should be ChipRAM.
"UMA" is the most current buzz TLA for this, iirc :laughing:

[guest11527]

Actually autoconfig does works with Vampire fastmem if you update expansion lib on kick from 32bit Amiga. e.g. "expansion_40.2(A500-600-2000) -> expansion_40.2(A1200)".

That is *not* autoconfig RAM. It is motherboard RAM (on the A1200) with a custom detection logic build into this particular version of expansion, though it is not using the autoconfig mechanism. In particular, there is no configdev for this RAM, no vendor ID and no product ID. It is similar to the "ranger memory" in this respect which is neither detected by an autoconfig type mechanism, but rather a detection logic that is hard-coded into the ROM.

[SpeedGeek]

That part of expansion is at least identical over all versions, i.e. decoding of the Z-III extended flags in the config defs. It would not make much of a difference anyhow as the A2000 does not have the ability to address anything beyond the 24-bit space on its Zorro.

Well, since there are different model specific versions of expansion.library it certainly implies that the model specific memory maps are an issue. But even if this is not an issue for the latest versions of expansion.library it could be for older library versions.

... and even though the A500/A2000 motherboards are limited to the ZorroII 24 bit address space accelerators with 32 bit CPUs can access 32 bit local bus hardware which could be implemented in ZorroIII format.

[Motormouth]

I think they were talking about hardware emulator boards like a Bridgeboard.

Yeah, I was referring to an actual hardware bridgeboard like a A2386sx.  I am lucky to have one with a 486slc and a couple of ISA cards.  It would be interesting if the bridgeboards were compatible with the vampire.  They, the bridgeboards, can be a bit finicky with some non-standard accelerators and zorro cards, it usuallly is a problem with overlap in the 24 bit address space or DMA issues, which should not be a problem with the vampire.

Maybe a couple months from now when I get my vampire 500 I can check it out and post it here.

[psxphill]

why on earth should anyone reimplement 486er in a Vampire FPGA?

why not?

That is even more senseless than reimplementing PPC in FPGA

Emulating a 486dx100 in an fpga would be much more doable than a 300mhz ppc. So less senseless.