i´m getting an exception when i want to debug my project

IoT Modules Development tools
1

hi everyone.

When i click on the green bug, to start the debugging, it loads a while and changes into the debugging perspective. So far so good.
But then i get the error

org.eclipse.cdt.debug.mi.core.MIException: localhost:3333: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (which means: Couldn´t connect, because the target machine refused to)
	at org.eclipse.cdt.debug.mi.core.command.Command.throwMIException(Command.java:105)
	at org.eclipse.cdt.debug.mi.core.command.Command.getMIInfo(Command.java:79)
	at org.eclipse.cdt.debug.gdbjtag.core.GDBJtagDebugger.executeGDBScript(GDBJtagDebugger.java:267)
	at org.eclipse.cdt.debug.gdbjtag.core.GDBJtagDebugger.doStartSession(GDBJtagDebugger.java:125)
	at org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createSession(AbstractGDBCDIDebugger.java:84)
	at org.eclipse.cdt.debug.gdbjtag.core.GDBJtagDebugger.createSession(GDBJtagDebugger.java:58)
	at org.eclipse.cdt.debug.gdbjtag.core.GDBJtagLaunchConfigurationDelegate.launch(GDBJtagLaunchConfigurationDelegate.java:54)
	at com.wavecom.openat.ide.ebs.launch.target.TargetLaunchDelegate.launch(TargetLaunchDelegate.java:129)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

The firewall of my pc is deactivated, so the firewall shouldn´t be the source of the problem.

Also i get the error

org.eclipse.cdt.debug.mi.core.MIException: The program is not being run.
	at org.eclipse.cdt.debug.mi.core.command.Command.throwMIException(Command.java:105)
	at org.eclipse.cdt.debug.mi.core.command.Command.getMIInfo(Command.java:79)
	at org.eclipse.cdt.debug.gdbjtag.core.GDBJtagDebugger.executeGDBScript(GDBJtagDebugger.java:267)
	at org.eclipse.cdt.debug.gdbjtag.core.GDBJtagDebugger.doRunSession(GDBJtagDebugger.java:237)
	at org.eclipse.cdt.debug.gdbjtag.core.GDBJtagLaunchConfigurationDelegate.launch(GDBJtagLaunchConfigurationDelegate.java:74)
	at com.wavecom.openat.ide.ebs.launch.target.TargetLaunchDelegate.launch(TargetLaunchDelegate.java:129)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

I would like to debug my programm very much, because the entire module restarts after a while…
I´m missing the try-catch blocks from “modern” languages :smiley:

2

Please can you elaborate on the DS and FW version you’re using?
Are you really trying to setup a JTAG debug session (i.e. with a JTAG probe on a JTAG-able module)?

3

The Module:
Embedded module: SL 6087
Mode: DEBUG
Bootloader Version: V08b11
Firmware
-build date: 08/09/11 - 13:01
-version: R7.46.0.201108091301.SL6087
-Size: 2216044
Application
-Application OS: 06.32
-State: Running

Development-Kit-Version: wm0502301-12-20

Version of the Developer Suite: “M2M Developer Suite 2.5”

where can i find the information wether it is JTAG able or not (whatever JTAG might be… :smiley:)?

the specification page of the sl 6087 and the user guide of the development kit doesnt even contain the word JTAG :frowning:

4

Ok so there are several points to fix here:

  • “M2M Developer Suite” was a tool prototype which never became a real product. It was partially integrating Developer Studio, but certainly an old version. You should install Developer Studio instead.
  • SL6087 doesn’t support JTAG debugging… You’ll have to use embedded GDB debugging. But to do so, you’ll need:
    ** Developer Studio
    ** FW 7.46 or higher (already OK)
    ** Open AT OS 6.36 or higher

Hope it will help.