#: 18197 S12/OS9/68000 (OSK)
    28-May-93  03:12:58
Sb: #18195-#68k bus errors
Fm: Chris Hann (Mass UK) 100064,1431
To: Bob van der Poel 76510,2203 (X)

Pardon my ignorance but how exactly do I run something in system mode? If there
is a way I can always run in system mode then fine I'll do it!

What I have been able to do after talking to Radstone is interrupt the system
to get to the ROM debugger and type the command 'ov2' which traps bus errors to
the rom monitor. This lets me find a particular hard error more quickly.
However the thing I really need is a software fix that I can leave in the
system permanently which will trap all bus errors. Part of my problem is that
the customer is keen to point the finger at our system for any failure as the
unit under test is more than a year late and they desperately need excuses, if
I can add a facility which will point to the problem directly then so much the
better. I should add that the system contains seven third party boards, three
Mass boards and five customer supplied boards ( three of which are
modifications of previous designs supplied by ourselves ), all but one of the
reported faults have been in the customer supplied boards (generally in their
two homebuilt boards but occasionally in the modified boards and then always in
the modifications). Sorry that's a load of political stuff but my backside is
getting singed every time they have a fault and I am getting a little tired of
having to break the news to them.

In general the OS-9 error messages "000:102" are very poor, almost all other
opperating systems will give an execution and access address.

If I find a good solution I'll let you know.

Chann 

There are 2 Replies.