[ECOS] MBX8XX platform questions.

[Erik Theisen <etheisen at mindspring dot com>]

Hi,

I am setting up eCos on a MBX860-002B board and have
some questions.

There are 12 MBX8XX variants, 6 821s and 6 860s.
2 of the them are entry level boards.  Of these 12
variants, only the 2 entry level boards have 50MHz
clocks, the other 10 have 40MHz clocks.  I would
guess that most people would want one of the standard
boards, not the entry level ones, since only the
standard ones have PC/104 expansion capabilities.

In light of the above, Why is
CYGHWR_HAL_POWERPC_MBX_BOARD_SPEED defaulted
to 50MHz instead of the more common 40MHz clock.

Also, it appears the 10 standard boards are
configured by "eppcbug" firmware to use the SMsC
FDC37C672 SuperIO chip for COM1 and COM2.  Only the
entry level boards use the 860/821 onboard SMC1 for
COM1. I believe the entry level board lacks the SMsC
chip.  These are the default settings.  eCos seems to
be using the SMC1 for COM1. It doesn't appear that
eCos has a driver for the FDC37C672 chip.

If someone, (me?), was to write a driver for this chip,
how would one go about making the configuration
distinctions between the entry level board and a
normal one?

I've tried to run some tiny eCos applications without
using stubrom.  This seems to hang the board.  I
believe that eCos and "eppcbug" are using the same
vector table.  Why?

I suspect that even without the vector problem, it 
would not work because "eppcbug" is using the SMsC
chip for IO and eCos is using the 8XX SMC1.

Additionally, I would like to be able to interrupt
a process by pressing the abort switch, which should
generate an abort/stop interrupt IRQ7, to drop back
to the debugger.  It doesn't seem to be working and
neither does CTRL-C.  What is required to make this
work?

Another thought... Does eCos support the parity memory
versions of the MBX8XX board?

Thanks for the help,
Erik