I'm terribly sorry to bother you with this old problem once more, but I've just spent my 2nd day with getting my debug to work again and am rather frustrated.
After weeks of happily debugging on device, I had some problems with my WinXP machine that seemed to affect my toolchain. So I reinstalled the Symbian Developer Toolchain and ran into the problem, that I no longer can debug with TRK over USB cable connection. (At day 2) I reinstalled XP with a new harddisk but ran into the same problem:
Whenever I try to debug my S60 application with Carbide2.0, I get the error message: "Target request failed: TRKProtocolPlugin: Can't connect to TRK (TRK may not be running on the phone or the selected and connected com ports are mismatched)".
My N82 has the latest firmware (V31.0.016) and runs the latest TRK (3.0.9). I use Carbide 2.0 build 014. Connecting the N82 for the first time to a fresh Windows installation, the N82 grabbed COM3 and COM4. How do I know? The first is shown with Windows' Device Manager and named "Nokia N82 USB", the latter can be viewed with C:\Symbian\9.2\S60_3rd\Epoc32\tools\ecmt\ecmtgw.exe and is shown as USBSER001. Using Carbide's "Debug configurations" dialog I created a "Symbian OS Application TRK" configuration and defined a USB connection that used "TRK 2.x USB" and told it to use COM4 (after some time, it showed the attached names of COM3 and COM4 as well). With Device OS set to S60 3.1.0 I let Carbide test the service... and it responded perfectly by telling me my TRK is up to date.
Note, whenever I tried to change the COM port here (to COM3 as this is the one which gets the connection name "N82") or change the connection type to "USB" (since I use TRK 3.x instead of 2.x), Carbide wasn't able to tell me the TRK version number. Unfortunately, the hint found in another forum article to disconnect and reconnect the device until it works with a "USB" connection and the port announced by the Device Manager, didn't work for me.
However, when I tried to use this configuration to start my application, I always got the mentioned error.
I tried to use other COM ports as well, e.g. COM3, since this was obviously the COM port my machine used to talk to the N82 for some service. Same result. I found some article which had a detailed problem solution for an apparently similar problem. I manually mapped my N82 connection (formerly COM3) to some higher port, COM25, changed my debug configuration to use COM25 as well, ignored the fact that Carbide no longer could tell me the TRK version... and got the same.
Changing the Connection Type to "USB" for returns "Error: TRK version response was corrupted" if I use COM4 ("USBSER001"), "Error: TCFError: Connection type is supported, but there was an error in connecting. OSError: The device is currently in use" when I use COM25 ("Nokia N82 USB", without any application using the connection, no Explorer session opened, no PC Suite started of idling background) and "Error: TCFError: Connection type is supported, but there was an error in connecting. OSError: Could not open the device" for other ports.
Trying to use a bluetooth connection failied similarly.
I'm desperated. Any suggestion?