×

Discussion Board

Results 1 to 8 of 8
  1. #1
    Registered User
    Join Date
    Oct 2003
    Posts
    8

    Problems with on device debugging on N80 device

    Hello:
    I am attempting to figure out how to get on device debugging working by debug an extremely simple Java MIDP2.0 program on a unlocked N80 device. My development environment is as follows:

    Eclipse 3.1.2
    Carbide.j 1.5
    S60 3rd Edition FP1 SDK for MIDP
    Windows XP host
    Unlocked N80 device connected via USB
    EcmtAgent_MIDP.SIS (version 4.00) on the N80 device
    Device Connectivity Tool for S60 SDK


    Below is a description of the on device debugging problem scenario:

    I installed the ECMTAgent_MIDP.SIS from the C:\S60\devices\S60_3rd_MIDP_SDK_FP1\s60tools\Ecmt directory and changed the bearer on the phone to use USB. Then I activated the Device Connectivity Tool for S60 SDK and connected to the EcmtAgent on the device via USB using a COM interface.

    After that I tried to debug my very simple program using the S60Device using Eclipse. I used the debug as...command and immediately got a Symbian SDK error with a java.io.EOFException. The SDK progress window displayed an error while connecting to the agent. I was running diagnostics from the device connectivity tool and the spewage from the SystemOut panel is cut and paste below:

    -------Begin cut paste---

    MidpDebugSession: [20447700] created (00600830)
    MidpDebugSession: [20447700] port 35862
    MidpDebugSession: [20447700] starting \sys\bin\JDbgAgt.exe
    LEAVE: iDebugAgentProcess.Create(exe, arg)
    Error: -1
    File: \Series60SDK_dev\Series60_tools\EcmtServer\Server\Plugins\MidpDebug\src\ecmtmidpdebugsession.cpp
    Line: 183
    MidpDebugSession: [20447700] destroyed (00600830)
    MidpDebugPlugin: SEND: invalid sid 20447700
    MidpDebugPlugin: CLOSE: no such session: 20447700
    MidpDebugSession: [20645035] created (00600830)
    MidpDebugSession: [20645035] port 33764
    MidpDebugSession: [20645035] starting \sys\bin\JDbgAgt.exe
    LEAVE: iDebugAgentProcess.Create(exe, arg)
    Error: -1
    File: \Series60SDK_dev\Series60_tools\EcmtServer\Server\Plugins\MidpDebug\src\ecmtmidpdebugsession.cpp
    Line: 183
    MidpDebugSession: [20645035] destroyed (00600830)
    MidpDebugPlugin: SEND: invalid sid 20645035

    ------end cut paste

    Has anyone seen this problem? Has anyone been able to get on device debugging working with S60 3rd Edition devices? If so, what is the magic combination of software that was used? Any help or comments offering insights would be appreciated.

    Thanks...

  2. #2
    Super Contributor
    Join Date
    Nov 2003
    Location
    Bangalore , India
    Posts
    4,429

    Re: Problems with on device debugging on N80 device

    In case you have missed, have a look at the Video on On-Device Debugging with Carbide.j 1.5
    http://www.forum.nokia.com/info/sw.n..._1_en.exe.html

    Regards
    Gopal

    __________________
    MobiQuil.com
    An initiative by Developers for Developers.
    http://www.mobiquil.com - Alpha - Launched.

  3. #3
    Registered User
    Join Date
    Oct 2003
    Posts
    8

    Re: Problems with on device debugging on N80 device

    Gopal:
    I did. I could not get bluetooth working so decided to try via USB using the ECMTAgent_MIDP.SIS provided with the S60 tools of S60 3rd editition SDK FP1. This ECMT agent seems to support USB bearer in addition to the WLAN and Bluetooth bearers. I was able to connect using the USB bearer with the Device connectivity tool for the S60 SDK.

    Other than that difference, I followed the procedure in the screencast.

    Thanks..

  4. #4
    Nokia Developer Expert
    Join Date
    Mar 2003
    Location
    Tampere, Finland
    Posts
    47

    Re: Problems with on device debugging on N80 device

    Hi,

    there is a different debug agent for S60 3rd Edition devices and for S60 3rd Edition, Feature Pack 1 devices. For N80, which is a 3rd Edition device, you should use the debug agent from Carbide.j, not the one from the FP1 SDK. USB as a bearer is not supported for 3rd Edition devices (N80), it is only supported for 3rd Edition, FP1 devices.

    Regards,
    Jouko

  5. #5
    Registered User
    Join Date
    Jul 2004
    Posts
    3

    Re: Problems with on device debugging on N80 device

    I ran into the same problem too. However, I am caught in the middle of many problems:
    * The on-device debugging provided by FP1 does not work on S60 3rd Edition devices (N80, in my case).
    * The on-device debugging provided by 3rd Edition SDK officially does not work... They say "It will be delivered as a separate zip package." This package does not exist yet, to the best of my knowlegde. However, you say it exists in Carbide.j 1.5, which, ironically...
    * Carbide.j 1.5 is no longer maintained by Nokia and it is not available for download.


    I think there should be an official and complete answer to: What are the tools and procedures to perform on-device debugging for S60 3rd Edition (non-FP1) devices, such as N80?

    It is quite annoying to be provided with powerful tools that are actually unusable in many cases...
    Last edited by phaneb2004; 2007-07-30 at 10:10.

  6. #6
    Super Contributor
    Join Date
    Apr 2003
    Location
    USA, CA
    Posts
    7,191

    Re: Problems with on device debugging on N80 device

    phaneb2004

    The Carbide.j 1.5 package contains the necessary files to do ODD (I have used them).

    Here is the download link for Carbide.j
    http://www.forum.nokia.com/info/sw.n...f4157416a.html

    Hartti

  7. #7
    Registered User
    Join Date
    May 2007
    Posts
    20

    Re: Problems with on device debugging on N80 device

    Man this stuff is unstable. I can get it to work after about 5 tries of starting stopping the app, eclipse, Device Connectivity tool. The bug I run into the most is

    1. When running the app it installs and then just quits by itself and uninstalls. Never hits the breakpoints i set.

    2. If not that one, i get an EOFException and the app doesn't come up.

    Sometimes it runs and works just fine.

    Will

  8. #8
    Registered User
    Join Date
    May 2007
    Posts
    20

    Re: Problems with on device debugging on N80 device

    For those interested...I switched over to wlan debugging and so far seems to be more reliable than the bluetooth.

    Will

Similar Threads

  1. On Device Debugging Connectivity Problem
    By mpvosseller in forum Mobile Java Tools & SDKs
    Replies: 11
    Last Post: 2008-01-22, 15:31
  2. Blank error dialog with on device debugging
    By fullscale in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 10
    Last Post: 2007-11-28, 07:33
  3. Memory Leak, On device debugging.
    By jhsial in forum Mobile Java General
    Replies: 5
    Last Post: 2007-04-07, 10:44
  4. Debugging problems
    By SevenOfEleven in forum Mobile Java Tools & SDKs
    Replies: 7
    Last Post: 2007-03-27, 21:52
  5. TRKProtocolPlugin carbide.c++ ODD (on device debugging) problems ??
    By samooha_2020 in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 1
    Last Post: 2006-12-28, 17:01

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×