BeebEm and 68k co-pro support

[eelco]

So, for the past weeks I've been steadily working on a 68k module for the BeebEm emulator, and I've now made some substantial progress

I've managed to implement the Casper co-pro, the Cumana co-pro and my own creation, the CiscOS copro

It's all still a bit buggy, but it's working for now... If you want to experiment with this, just download the ZIP file and extract it. Currently only a Windows version is available. Since it uses some extra files in the Documents\BeebEm\BeebFile folder, you may need to rename any current Documents\BeebEm folder to Documents\BeebEm.bak. When you now start BeebEm, it wil ask you if it can create a new folder called BeebEm in Documents with all the correct ROM's.

To start the Casper co-pro:

• Start BeebEm
• Go to Hardware -> Edit ROM configuration
• Select an empty slot, and load the Casper6502.rom file
• Go to Hardware - Select second processor and select Casper 68000 Second Processor
• Enter *CASPER

To start the Cumana co-pro (doesn't boot yet):

• Start BeebEm
• Go to Hardware -> Edit ROM configuration
• Select an empty slot, and load the Cumana68k.rom file
• Go to Hardware - Select second processor and select Cumana 68k Second Processor
• Enter *OS9

To start the CiscOS co-pro (doesn't boot yet):

• Start BeebEm
• Go to Hardware - Select second processor and select CiscOS Second Processor

No need to say that any use of this beta-program is at your own risk!

[jgharston]

I'll have to get PDP-11 BASIC finished and make a start on 68K BASIC

[Pernod]

I tried your Cumana co-pro in your posted exe but it doesn't progress to the System Bootstrap message. I'm having the same issue in MAME. I have the memory mapped same as yours so that the 68008 and 6502 share RAM/ROM and devices, and can see the 68K code at &8662, and vectors are in place at &0000. All it needs is to reset the 68008 to start execution but it's not happening. If I reset the 68008 manually then I get the Bootstrap prompt, and the floppy drive comes to life but doesn't yet load anything..

Your circuit diagram suggests CB2 from the rtc_pia should trigger the reset, which I have hooked up, but is never written to.