none
using Remote Tools with WEC 2013 RRS feed

  • Question

  • Hi everyone,
    I am having trouble connecting Remote Tools in Visual studio 2015 with my target board running on WEC 2013.

    I built the OS Image in Release configuration with build options
     - Enable Kernel debugger : YES (IMGNODEBUGGER=)
     - Enable KITL : YES (IMGNOKITL=)
     - Enable kernel profiling : YES (IMGPROFILER=1)

    In bootloader menu I set
     - KITL Enable Mode : Enable
     - KITL Work Mode : Interrupt
     - KITL Passive Mode : Disable

    and when I tried Download Image Now in bootloader menu, Target device Started BOOTME messages for OS run time image download, connection was established with visual studio and successfully downloaded OS Image( nk.bin ). All the service states(Download, Transport, Debugger, Target Control) had turned into green in device status window in visual studio 2015.

    Remote tools such as Process Viewer, File Viewer and Remote registry editor are working good.

    But when I tried to connect using TOOLS | REMOTE TOOLS | PERFORMANCE MONITOR
    I am getting Exception trying to get the shell form as below :

    If I try TOOLS | REMOTE TOOLS | KERNEL TRACKER, timestamp and symbols issue is coming 

    and for TOOLS | REMOTE TOOLS | TIMELINE VIEWER, sometimes connection is made but the screen is left blank( black color) without any data as if it was not connected but showing Connection | Disconnect from desktop only remote tools shell.

    someone please help in resolving these issues,

    Many thanks in advance,
    Praveen.




    • Edited by Praveen105 Friday, January 5, 2018 7:44 AM
    Friday, January 5, 2018 7:26 AM

All replies

  • Adding some more updates,

    Connecting with Remote Device:
    When I try connecting, Remote Tools shell is opening and showing 3 options :
    1. Desktop Only
    2. Windows CE Application Builder.
    3. Windows Embedded Compact Platform Builder Devices.

    Connecting with Remote Tools:
    If I try Windows CE Application builder and give IP Address of Target device, Connection is made and showing data for below tools:

    Timeline Viewer, Profiler, Registry Editor, Resource Consumer, Resource Leak Detector, System Information

    But for TOOLS -> REMOTE TOOLS -> Kernel Tracker, Performance Monitor, It is giving below exception.

    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.
    
    ************** Exception Text **************
    System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.RemoteToolSdk.Shell.MainView.LaunchPlugin(String deviceGuid, CEToolFile cetoolFile, List`1 importFilenames, List`1 parameters, Boolean warnOnPluginAlreadyRunning, List`1 launchingCetoolFiles, LaunchTypes launchType)
       at Microsoft.RemoteToolSdk.Shell.MainView.LaunchPluginFromOptionsFile(String deviceGuid, CEToolFile cetoolFile, List`1 importFilenames, List`1 parameters, Boolean warnOnPluginAlreadyRunning, LaunchTypes launchType)
       at Microsoft.RemoteToolSdk.Shell.ShellView.<>c__DisplayClass4.<ProcessRTFxOptionsFile>b__3()
       at Microsoft.RemoteToolSdk.PluginComponents.CommonObjects.RunOnThread(Control control, AnonymousDelegate handler, Boolean asynchronous)
       at Microsoft.RemoteToolSdk.Shell.ShellView.ProcessRTFxOptionsFile(RTFxOptionsFile optionsFile, Boolean ignorePluginExplorerAttribute, LaunchTypes launchType)
       at Microsoft.RemoteToolSdk.Shell.ShellView.<>c__DisplayClass1.<mainView_ProcessRTFxOptions>b__0()
       at Microsoft.RemoteToolSdk.PluginComponents.CommonObjects.RunOnThread(Control control, AnonymousDelegate handler, Boolean asynchronous)
       at Microsoft.RemoteToolSdk.Shell.ShellView.mainView_ProcessRTFxOptions(Object sender, ProcessRTFxOptionsEventArgs e)
       at Microsoft.RemoteToolSdk.Shell.MainView.LoadFileList(String[] fileNames, String[] deviceGuids)
       at Microsoft.RemoteToolSdk.Shell.ShellView.Init(List`1 pluginXMLFileNames, List`1 deviceGuids)
       at Microsoft.RemoteToolSdk.Shell.RemoteToolsShellApp.BuildShellView()
       at Microsoft.RemoteToolSdk.Shell.RemoteToolsShellApp.InitializeCustomComponents()
       at Microsoft.RemoteToolSdk.Shell.RemoteToolsShellApp.RemoteToolsShellApp_Load(Object sender, EventArgs e)
       at System.EventHandler.Invoke(Object sender, EventArgs e)
       at System.Windows.Forms.Form.OnLoad(EventArgs e)
       at System.Windows.Forms.Form.OnCreateControl()
       at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
       at System.Windows.Forms.Control.CreateControl()
       at System.Windows.Forms.Control.WmShowWindow(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
       at System.Windows.Forms.Form.WmShowWindow(Message& m)
       at System.Windows.Forms.Form.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    
    
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    ----------------------------------------
    RemoteToolsShell
        Assembly Version: 8.0.0.0
        Win32 Version: 8.000.6248
        CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Remote%20Framework%20Tools/8.00/bin/RemoteToolsShell.exe
    ----------------------------------------
    Microsoft.RemoteToolSdk
        Assembly Version: 8.0.0.0
        Win32 Version: 8.000.6248
        CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Remote%20Framework%20Tools/8.00/bin/Microsoft.RemoteToolSdk.DLL
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Runtime.Remoting
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1099.0 built by: NETFXREL4STAGE
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    
    For example:
    
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    

    2. When I try through platform builder option in any remote tool, No connection is established with tools ( Performance monitor and Kernel Tracker give exception in this too).

    Settings for Platform builder is shown as below:

    Request you to please guide / help.

    Wednesday, January 10, 2018 2:43 PM