And now the keyboard works as well as some jumpers emulated so we fall into FORCEbug rather than trying to auto boot some so far non existing floppy disk. This is rather cool as it is FOREbug and not VMEprom, PDOS is not integrated but separated. later on the VMEprom replaces FORCEbug and all it s functionality and also integrating a PDOS kernel.

Next thing will be to load the fccpu20 in the miniforce chassi previously skeltonized and now I want to explore how the VME bus calls can be dispatched between the boards. Yet then we need to write the WFC1 mass storage controller board to get to the floppy controller.

Can't determine without knowing how the initialization was done, I will come back to the MPCC when I have PDoS booting to add interrupts and a few other things but it may take a while, feel free to contribute to the MPCC meanwhile. Here is the data sheet, it is quite good actually:

Cool, nice to see additional VME boards being added! I am not sure when I will get back to VME again, I need to get some of my other skeletons up to working first and then I have a pile of stuff in the garage that needs to be added to existing drivers or new ones. But sooner or later I will and by then we might have a chance to make an improved VME bus, contributions are welcome!

I think this board has the best chance of running an OS (everything is integrated - SCSI, floppy and Ethernet), but some reverse-engineering will need to happen first (there's a schematic somewhere but I don't have a copy). Right now it's stuck waiting for IRQ from DUSCC -- I was hoping you'd take a look at DUSCC code

Sure, that is maintenance, I can have a look at it soonish, just need the driver to be merged and the roms of course. It would be nice to know how the IRQ is actually hooked up to the CPU, usually there is an interrupt controller in between that also arbitrates the VME interrupts so it can get tricky if that is an unknown. At least we need to know the vector and the level used.