Home Page Forums MAME MAME VME boards

Great! I'd love to do the 960 board one day. Thx!

New VME board added: Mizar VME8105, a simple 68000 based 3U (half height) board with a OS9 bootstrap on.

The emulation includes a serial device that really isn't on the board but being expected to be found by the bootstrap on a serial VME board nearby. The bootstrap also presumably requires a memory board and boot device board. Anyone with experience of booting OS9/68000, please have a look, layout and details is found here:

https://drive.google.com/file/d/0B685nj_1DkduTG53ZEZldzJZMVk/view?usp=sharing

Let me know what you know about booting a full system.

Since the main UI on vanilla VME boards usually is a RS232 based terminal of some sort I am trying to figure out the way forward here. While I like the idea of diserial.c it seems to drain a lot CPU cycles. I got Average speed 45% for the fccpu1 board wich has three ACIA6850 and a PIT68230.

I can have done something wrong myself admitedly but when I study the code it seems to do a lot of updating of various signals in the RS232/diserial hook up.

For instance in device_serial_interface where the clock drive calls to rcv_edge which calls rcv_callback for every clock cycle, even when the line has no data on it. This is when my fan is working hard despite I am not typing anything on the terminal.

Why not update the signal in an event driven fashion, only when it changes state? I might have missed something fundamental about emulation though, let me know.

I have also looked at:
1) use one of the emulated VTxxx terminals but that would require firmwares
2) build a live socket connection to a native VTxxx terminal emulator or build in a simple telnet/ssh server

Any advice here is appreciated

If you have an rs232 connection, you can redirect the serial out to a TCP socket instead of the built-in terminal.

Any serial implementation is going to have a fairly decent CPU load because of timing, although 3 of them shouldn't slow down emulation unless you're on a really dire machine. Any half-recent i5/i7 should handle that fine.

I've borrowed Force ISCSI-1 hardware manual and going to scan it soon, guess that bitsavers would be interested in that?

Yes.

Scan it at around 300dpi greyscale (600dpi for schematics or high-res line art), I think Al can postprocess it to bilevel using imagemagick or something similar.

Al?

that's ok. do the text at 600 so I don't have to interpolate from 300, and save it with lossless compression (NO JPEG!)

OK, I can do that.

Do you accept text files into the archive? There are quite a few, for the Besta itself and others.

sure. just need a pointer to what you'd like to archive. directory and file naming to match the bitsavers style is helpful

There are also quite a few scans made by others, often from sources that are no longer available -- would you accept those as well? These are often in djvu format. F.e. the manual that I used to write ie15.c driver is: https://docs.google.com/file/d/0B55cuwBw5HR-MHdocUZISVVlQW8/edit?usp=sharing