Thread Subject: How can I determine the cause of an xPC lock-up?

Hello,

I have an xPC executable that will run on the target, PC-104 stack, for a ramdom period of time then stop. I have not been able to determine any order of operations or specific I/O stimulation that cause the "crash". No error messages are printed to the VGA monitor attached to the xPC target. The indication of lock-up is that the seconds stop updating on the monitor. How can I determine where to look for possible issues?

On another note: If I do not disable the updates over the ethernet between the development host and xPC target I get a lock-up as well.

Mark

Mark,

When you have a problem with xPC Target like this, please contact
MathWorks tech support. Figuring out what's wrong will take more than
I'm willing to do here on the newsgroup.

Gordon Weast
xPC Target Development
MathWorks

Mark wrote:
> Hello,
>
> I have an xPC executable that will run on the target, PC-104 stack, for
> a ramdom period of time then stop. I have not been able to determine any
> order of operations or specific I/O stimulation that cause the "crash".
> No error messages are printed to the VGA monitor attached to the xPC
> target. The indication of lock-up is that the seconds stop updating on
> the monitor. How can I determine where to look for possible issues?
>
> On another note: If I do not disable the updates over the ethernet
> between the development host and xPC target I get a lock-up as well.
>
> Mark