I am working on the Motorola MVME147 right now as I got hold of a ROM set. It has support for the MVME350 tape controller that I have already dumped so in theory I can put together everything and boot from tape over the VME bus when I am done.
I could need some help making the outline of the VME slot device, I have not figured out the best way of doing that yet, it always stumbles on my top down view on MAME, I need more understanding of the bottom part, by time or someone contribute a design, I can implement though. Once established I can populate all the boards with it.
but there are some wierd things going on with the serial emulation.
This ROM actually sets up 1 stop bit just like the default "terminal" requires but only works when I patched the z80scc.cpp to always use 2 stop bits, something I knew worked with the hk68v10 driver... and also the input from the terminal doesn't fully work so I need to dig into the diserial details before solving each of the errors on the screen. Progress non the less!
I found the bugs finally, it was due to that it is not possible to use diserial the way I did with local baudrate timer in the SCC device. I got it nearly to work one way as can be seen above but when sending keypresses the other way there was problems. The SCC device wasn't producing exactly the right baud rate but nearly enough to being able to send characters from the board to the terminal, but in the opposite direction there was not start bit detection and there was no mid bit alignment in the SCC device. Even after adding that it turned out that I didn't get the final transmitt_complete because it also had no stop bit detection... So I relized I was reimplementing diserial in the SCC device and after I relized that it took me just 20 minutes to implement the baudrate timer using the diserial setrate() functions. So that part is now rock solid compared to how it was and the MVME-147 driver was submitted a few days ago with a working 147-Bug> terminal. It has a lot of features to play with:
Some of this doesn't work yet since there are no devices behind the commands but it is a start and the 147-Bug supports booting an OS from disk and load code it is just a matter of complete the emulation :-)
The next board I am working on is the MVME-162 with a 68040 device and hve already got a prompt, or two actually! The first is called Raw-bug and is a ROM only monitor built in to the firmware. It requires no RAM and I was dropped into that after setting up the SCC but with no RAM in the system. Once I configured some RAM the 162-Bug started up:
The 162-Bug also has loads of commands to play with:
I hope to be able to submit the first version soon and then start to reduce the diagnostics errors.
Yeah me too, its kind of low hangning fruits though to just hook up the serial port but it gives a lot of possibilities to boot software. The problem is to get relevant software for these machines. Sure a UNIX or OS9 would be fun to hook up but it would be even better to get some ROM:s from an industrial system that really did something, from a sawmill or so