An error output shown below is representative of the debug probe/adapter being used does not match the setting. Pre-release EV Kits came with an Olimex ARM-USB-OCD-H adapter/probe. However, production release EV Kits come with a Olimex ARM-USB-TINY-H. So it is important that the toolchain is aware of the debugging adapter/probe that you are using.
"Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: No connection could be made because the target machine actively refused it.
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: No connection could be made because the target machine actively refused it.
localhost:3333: No connection could be made because the target machine actively refused it."
This error was a result of trying to use the Olimex ARM-USB-OCD-H debug adapter/probe, although the .launch file was specifying the Olimex ARM-USB-TINY-H.
The error was fixed by changing this line in the .launch file:
<stringAttribute key="ilg.gnuarmeclipse.debug.gdbjtag.openocd.gdbServerOther" value="-s ${env_var:TOOLCHAIN_PATH}/share/openocd/scripts -f interface/ftdi/olimex-arm-usb-tiny-h.cfg -f target/MAX32650.cfg"/>
When 'arm-usb-tiny-h' was changed to:
<stringAttribute key="ilg.gnuarmeclipse.debug.gdbjtag.openocd.gdbServerOther" value="-s ${env_var:TOOLCHAIN_PATH}/share/openocd/scripts -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -f target/MAX32650.cfg"/>
the error disappeared.