When the connect button is pressed and the com-port settings are wrong (or the target is unresponsive for another reason). you get a message box saying there is no responce from the target. But, the application still thinks it’s connected.
You have to switch to the serial link manager to find out what the problem is, then go back to m2m studio to correct the problem (after first pressing ‘disconnect’ as the program wrongly thinks it’s connected to the target.)
this is not a very logical approach. and i hope this can be addressed in the next release.