ThingMagic Mercury xPRESS, Platform Manual, Page: 103 / 146

A D I V I S I O N O F T R I M B L E
Using the Developer Toolkit
103
Note that starting the debugger may take some time. Eclipse has to make sure the
binary is up-to-date, initialize the debugger, load the image, pause the program and
index into the source. You may need to wait a half minute or more. If you want to
see some interim status, check the GDBServer window -- it will usually show some
update for each step.
If unsuccessful, try the following fixes before attempting to start debug again:
Š
Kill and restart J-Link GDB Server. This helps if the GDB server has lost sync with
the J-Link hardware.
Š
Restart Eclipse (menu File / Restart ). This helps if Eclipse has lost sync with the
GDB server.
Š
Power cycle the J-Link hardware and the target board. This helps if the J-Link has
lost sync with the board or the target firmware has crashed.
Š
Make sure the target board watchdog is not enabled. This can reset the target
hardware at times when the J-Link is not expecting it, causing loss of sync.
Š
Erase the target board. In extreme cases, the programming fuse state may have
become corrupted, causing debug features to be disabled.
For subsequent debug runs, you don’t have to navigate all the way into the Debug
Configurations menu. Eclipse will remember recent ones in its toolbar.