View the NBEclipse log file to determine the cause of an error
The log file is an easy way to determine the cause of an error, and is very helpful to NetBurner support if you create a support request.
The log file is located in \nburn\nbeclipse\workspace\.metadata\.log. You can open this text file from the NBEclipse workspace, or with any text editor.
NBEclipse does not start, or you receive an error message: “An internal error occurred…”
Debugger reports error when trying to connect to a network target
The NetBurner target device is not running. This could be caused by an application that is crashing, or a previous debug session that has left the application stopped at a breakpoint.
The function call to initialize debugging is not present. For example: InitializeNetworkGDB( ) for network platforms or InitGDBStub( 1, 115200 ) for non-network platforms.
Network Platforms: The function call to initialize debugging is not in the correct location. It should be called as soon as possible after the call to initialize the network and autoupdate. If you are using DHCP, make sure it is after the call to get the DHCP address.
Debugger reports error when trying to connect to a non-network target
Non-network platforms: If “Fast Serial” has been selected you must have started the “Fast Serial Debug” application on your PC.
The application running on the target is a “release build” rather than a “debug build”
