ThingMagic Mercury xPRESS Platform v1.7 - Manual (Page 102)

A D I V I S I O N O F T R I M B L E
102 Using the Developer Toolkit
Pull down the menu next to the Debug button and select the
configuration there.
Running the Program
Once you have successfully started the debugger, press Resume to run the program.
Toolbar button
or Press F8
or Menu Run / Resume
Relaunching the Program
If you make changes to your code,
1. First, rebuild (right-click on project, Build Project, or just press Ctrl+B if you left the
Project Explorer selection in the correct project.) The debug launch does invoke an
automatic build, but for some reason, this tends not to pick up all the same
dependencies as an explicit build.
2. Right-click anywhere in the process in the Debug tab and select Terminate and
Relaunch.

For hardware debugging, you must terminate the current process before
relaunching, or Eclipse will try to run multiple instances of the program.
Since there is only one copy of the hardware, this will not work. Eclipse will
try to talk to all instances, most of which will not actually exist. This will
break sync with the debugger and you will have to restart Eclipse to
recover.
 If the process was already terminated, just select Relaunch.
 Sometimes, you may get an Errors in Workspace popup.
Press Cancel and check the Console. If it shows no errors, then this is
probably a false positive from Eclipse’s code analysis module (Codan),
which runs code checks beyond those performed by the toolchain. In this
case, try again and press Proceed.
To resolve Codan false positives, use the Problems tab. If it looks like it’s
not a real error, try deleting the problems from the Problems tab.