[evla-sw-discuss] MIB Study Group-Search for the MIB Processor

[Barry Clark]

What we have been talking about for a MIB is a pretty powerful machine,
and it is not clear to me that any modules will need to have a second
microprocessor in them.  The only one I can think of that might is a 
redesigned ACU.  So I would downgrade the importance of dual ported RAM.

I think a watchdog timer is absolutely critical.  If we don't have one,
we must build in the capability to remotely cycle power to any MIB.

I don't know what a SPI interface is, nor a JTAG.

One timer is a necessity.  Two are occasionally useful.  Three are overkill.

We haven't really discussed the philosophy of loading the particular 
software of the MIB.  Possibilities include:
    1.  Software for all possible MIBs lives in the on-board flash; MIB
        decides what sort of MIB it is, starts appropriate tasks.
    2.  Software lives in on-board flash, OS has routine to easily reload
        flash if the M/C system detects that it is for the wrong device
        or the version ID is out of date.
    3.  On boot, MIB realizes what sort of device it is in and requests
        M/C system to supply it with the requisite software.
All have their advantages and disadvantages.  It is quite likely that some
packages will support one better than the other, so we ought to make up 
our minds which one we want.

But in my mind the driving necessity is ease and compatibility of software
development.  I suspect that we shall spend as much money on the software
as on the design and construction put together.