User`s guide

10 Interrupts Versus Polling
10-10
If the target application execution finally reaches the stop time and polling
mode execution is stopped, host-target communication will begin functioning
again. However, the host-target communication link might be in a bad state. If
you still get communication error messages after polling mode execution stops,
type the command
xpctargetping
to reset the host-target communication link.
After the communication link is working again, type
tg
to resync the target object on the host side with the most current status of the
target application.
Target Screen Does Not Update During the Execution of the Target
Application
As with the restriction mentioned above, target screen updating is disabled
during the entire execution of the target application. Using the kernel with the
Enable target scope option enabled (see xpcexplr GUI) does not work. You
should therefore use the kernel with the
Enable target scope property
disabled (text output only). The kernel enabled with text mode actually
provides more information when running in polling mode.
Session Time Does Not Advance During the Execution of the Target
Application
Because all interrupts are disabled during a run, the session time does not
advance. The session time right before and after the run is therefore the same.
This is a minor restriction and should not pose a problem.
The Only Rapid-Prototyping Feature Available Is Data Logging
Because host-target communication and target screen updating are disabled
during the entire run, most of the common rapid-prototyping features of xPC
Target are not available in polling mode. These are
• Parameter tuning — Neither through the command-line interface nor
through External mode