Re: Connect VS 2005 to running platform without ActiveSync by Paul
Paul
Wed Jul 09 09:17:42 PDT 2008
Seems like there's at least one update to VS2005 after SP1. I've never seen
anything remotely like that. This sounds like something that would happen
if you tried to connect both debuggers from a single instance of VS2005,
which I see you're not doing, though. You don't have the firewall built
into CE, right? You could also try turning off any firewalling on the PC,
although I doubt that will fix it.
Paul T.
"Selin Metin" <nospams@this.mail> wrote in message
news:OUnsTrd4IHA.4492@TK2MSFTNGP04.phx.gbl...
>I already tried re-running CmAccept.exe several times, but the result never
>changes. I can use the Platman remote tools, but when I try to connect with
>the VSD remote tools, it says "connection is established" but nothing
>happens. For example, I don't see a list of available files & folders when
>I use remote file viewer. Also, when I test the connection, it says OK. But
>I cannot configure the settings for the connection.
>
> I have only one installation of VS SP1 + PB, and I used CeFileWiz to
> include all the required files as a catalog item, therefore I don't think
> that there is a conflict between the versions. The files on the target
> come from "C:\Program Files\Common Files\Microsoft
> Shared\CoreCon\1.0\Target\wce400\armv4i" directory, which, I believe, is
> the directory VS 2005 uses.
>
> And now, I can't even check the device properties because I get this
> error:
> ---------------------------
> Microsoft Visual Studio
> ---------------------------
> Error retrieving information from user datastore. Property not found.
> ---------------------------
> OK
> ---------------------------
> Well, nothing has changed, I just worked on some dialog resources for a
> couple of hours (on the same VS instance), and now I cannot even use the
> properties of the SDK!... cursed VS, maybe it's time to finish the day.
>
> Thanks for your ideas, I will try more tomorrow (sigh!)
>
> Selin
>
>
> Paul G. Tobey [eMVP] schrieb:
>> You might try rerunning CmAccept.exe, if that happens. I have a program
>> that handles my debug connections on our devices. It keeps the Platform
>> Manager running for eVC4 and its version of the tools and
>> ConManClient2/CmAccept for VS communications. Maybe there's some sort of
>> a two-step communication that requires a second connect. I don't know
>> what's causing the problem, but that's what I'd try. You *have* verified
>> that you have the latest version of the files for the communication on
>> the device, right? Installing a new version of Visual Studio updates
>> them and might leave you out of touch if what's on the PC and what's on
>> the device don't match.
>>
>> Paul T.
>>
>> "Selin Metin" <nospams@this.mail> wrote in message
>> news:OCRdqSZ4IHA.1428@TK2MSFTNGP06.phx.gbl...
>>> Thanks for the reply. Yes, the device on the list matches the device I'm
>>> trying to connect to. Strange, but after I shut down the PC last night,
>>> and started it today, I could connect to the device, with exactly the
>>> same settings.
>>>
>>> Now I have a different problem: Although it says the connection is
>>> succeeded, I cannot start debugging and get the following error:
>>>
>>> 1>Deployment and/or registration failed with error: 0x8973190e. Error
>>> writing file '%CSIDL_PROGRAM_FILES%\MyApp\MyApp.exe'. Error 0x8007274c:
>>> A connection attempt failed because the connected party did not properly
>>> respond after a period of time, or established connection failed because
>>> connected host has failed to respond.
>>>
>>> I run conmanclient2.exe and then cmaccept.exe on the target device and
>>> verify their processes exist by "gi proc" command. I noticed that as
>>> soon as I click start debugging on the VS instance for application
>>> development, cmaccept.exe dies without any clue. And then I get the
>>> above error. The OS log messages are below:
>>>
>>> 668007 PID:5e30012 TID:5e40012 OSAXST1: >>> Loading Module 'coredll.dll'
>>> (0x8FFF66CC) at address 0x40010000-0x40123000 in Process 'cmaccept.exe'
>>> (0x8E315624)
>>> 668010 PID:5e30012 TID:5e40012 OSAXST1: >>> Loading Module
>>> 'cmaccept.exe' (0x8E315624) at address 0x00010000-0x00019000 in Process
>>> 'cmaccept.exe' (0x8E315624)
>>> PB Debugger Loaded
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\CMACCEPT.EXE',
>>> no matching symbolic information found.
>>> 668158 PID:5e30012 TID:5e40012 Heap Statistics at 0x4010CAA8
>>> 711900 PID:5e30012 TID:5e40012 OSAXST1: <<< Unloading Module
>>> 'coredll.dll' (0x8FFF66CC) at address 0x40010000-0x40123000 in Process
>>> 'cmaccept.exe' (0x8E315624)
>>> 711903 PID:5e30012 TID:5e40012 OSAXST1: <<< Unloading Module
>>> 'cmaccept.exe' (0x8E315624) at address 0x00010000-0x00019000 in Process
>>> 'cmaccept.exe' (0x8E315624)
>>> PB Debugger Unloaded symbols for
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\CMACCEPT.EXE'
>>> 713016 PID:400002 TID:5fd0012 OSAXST1: >>> Loading Module 'mscoree.dll'
>>> (0x8E39475C) at address 0x422E0000-0x422F0000 in Process 'NK.EXE'
>>> (0x8B6F9AA0)
>>> PB Debugger Loaded
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\MSCOREE.DLL',
>>> no matching symbolic information found.
>>> 713019 PID:565000e TID:5fd0012 OSAXST1: >>> Loading Module
>>> 'mscoree.dll' (0x8E39475C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 713022 PID:565000e TID:5fd0012 OSAXST1: >>> Loading Module 'ole32.dll'
>>> (0x8DC40378) at address 0x40640000-0x4069D000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 713031 PID:565000e TID:5fd0012 OSAXST1: <<< Unloading Module
>>> 'ole32.dll' (0x8DC40378) at address 0x40640000-0x4069D000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 713033 PID:565000e TID:5fd0012 OSAXST1: <<< Unloading Module
>>> 'mscoree.dll' (0x8E39475C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 713035 PID:565000e TID:5fd0012 OSAXST1: <<< Unloading Module
>>> 'mscoree.dll' (0x8E39475C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> PB Debugger Unloaded symbols for
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\MSCOREE.DLL'
>>> 717423 PID:400002 TID:5fd0012 OSAXST1: >>> Loading Module 'mscoree.dll'
>>> (0x8E39475C) at address 0x422E0000-0x422F0000 in Process 'NK.EXE'
>>> (0x8B6F9AA0)
>>> PB Debugger Loaded
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\MSCOREE.DLL',
>>> no matching symbolic information found.
>>> 717426 PID:565000e TID:5fd0012 OSAXST1: >>> Loading Module
>>> 'mscoree.dll' (0x8E39475C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 717441 PID:565000e TID:5fd0012 OSAXST1: >>> Loading Module 'ole32.dll'
>>> (0x8DC40378) at address 0x40640000-0x4069D000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 717454 PID:565000e TID:5fd0012 OSAXST1: <<< Unloading Module
>>> 'ole32.dll' (0x8DC40378) at address 0x40640000-0x4069D000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 717455 PID:565000e TID:5fd0012 OSAXST1: <<< Unloading Module
>>> 'mscoree.dll' (0x8E39475C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 717457 PID:565000e TID:5fd0012 OSAXST1: <<< Unloading Module
>>> 'mscoree.dll' (0x8E39475C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> PB Debugger Unloaded symbols for
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\MSCOREE.DLL'
>>> 1246890 PID:400002 TID:4540016 OSAXST1: >>> Loading Module 'mscoree.dll'
>>> (0x8E39409C) at address 0x422E0000-0x422F0000 in Process 'NK.EXE'
>>> (0x8B6F9AA0)
>>> PB Debugger Loaded
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\MSCOREE.DLL',
>>> no matching symbolic information found.
>>> 1246898 PID:565000e TID:4540016 OSAXST1: >>> Loading Module
>>> 'mscoree.dll' (0x8E39409C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 1246901 PID:565000e TID:4540016 OSAXST1: >>> Loading Module 'ole32.dll'
>>> (0x8DC40378) at address 0x40640000-0x4069D000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 1246910 PID:565000e TID:4540016 OSAXST1: <<< Unloading Module
>>> 'ole32.dll' (0x8DC40378) at address 0x40640000-0x4069D000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 1246911 PID:565000e TID:4540016 OSAXST1: <<< Unloading Module
>>> 'mscoree.dll' (0x8E39409C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 1246913 PID:565000e TID:4540016 OSAXST1: <<< Unloading Module
>>> 'mscoree.dll' (0x8E39409C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> PB Debugger Unloaded symbols for
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\MSCOREE.DLL'
>>> 1253249 PID:400002 TID:4540016 OSAXST1: >>> Loading Module 'mscoree.dll'
>>> (0x8E39409C) at address 0x422E0000-0x422F0000 in Process 'NK.EXE'
>>> (0x8B6F9AA0)
>>> PB Debugger Loaded
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\MSCOREE.DLL',
>>> no matching symbolic information found.
>>> 1253251 PID:565000e TID:4540016 OSAXST1: >>> Loading Module
>>> 'mscoree.dll' (0x8E39409C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 1253254 PID:565000e TID:4540016 OSAXST1: >>> Loading Module 'ole32.dll'
>>> (0x8DC40378) at address 0x40640000-0x4069D000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 1253263 PID:565000e TID:4540016 OSAXST1: <<< Unloading Module
>>> 'ole32.dll' (0x8DC40378) at address 0x40640000-0x4069D000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 1253264 PID:565000e TID:4540016 OSAXST1: <<< Unloading Module
>>> 'mscoree.dll' (0x8E39409C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> 1253266 PID:565000e TID:4540016 OSAXST1: <<< Unloading Module
>>> 'mscoree.dll' (0x8E39409C) at address 0x422E0000-0x422F0000 in Process
>>> 'conmanclient2.exe' (0x8E315D0C)
>>> PB Debugger Unloaded symbols for
>>> 'D:\WINCE600\OSDESIGNS\OSDESIGN4\IMX31PROJECT\RELDIR\IMX31_PHYTEC_BINARY_ARMV4I_DEBUG\MSCOREE.DLL'
>>>
>>>
>>> What could cause this problem? What should I do to make cmaccept.exe
>>> persist for the mentioned 3 min in order to get connected?
>>>
>>> Regards,
>>> Selin
>>>
>>>
>>>
>>> Paul G. Tobey [eMVP] schrieb:
>>>> Are you sure that you set the target IP address in Device options in
>>>> VS2005 for the right device? That dialog has a lot of pull-down lists
>>>> and things that change who you are configuring. It should be apparent
>>>> that, if you've configured the wrong device, it's not going to work.
>>>> The pull-down list might show your SDK name, for example, or Windows
>>>> CE, either of which is reasonable and, depending on what the Target
>>>> selection for the current build is, will decide which is the right one.
>>>>
>>>> Paul T.
>>>>
>>>> "Selin Metin" <nospams@this.mail> wrote in message
>>>> news:uykUyPR4IHA.212@TK2MSFTNGP04.phx.gbl...
>>>>> Hi all,
>>>>>
>>>>> I develope an MFC application in VS 2005 and an OS design with PB (CE
>>>>> 6.0). I use two instances of VS 2005, one to download the image to the
>>>>> target device and other to write the application. So far, there is no
>>>>> problem in building the platform, downloading it to the target, and
>>>>> debugging through ethernet (using KITL). However, I cannot connect the
>>>>> second instance of VS 2005 to this running OS on the target device to
>>>>> debug the application. However, if the device boots with the
>>>>> pre-installed image, I can connect the VS 2005 instance with
>>>>> ActiveSync and debug my application.
>>>>>
>>>>> I read Mike Hall's blog, windows ce help, ms virtual labs, many
>>>>> newsgroup posts about this subject. The steps I have taken so far are:
>>>>> 1) Add the CoreCon functionality to the platform as a catalog
>>>>> component using CEFileWiz. Now the necessary files (conmanclient2.exe,
>>>>> cmaccept.exe, etc.) are in the windows directory of the target device.
>>>>> 2) When the system boots, I run conmanclient.exe and cmaccept.exe
>>>>> through Target Control, and verify that these are running with "gi
>>>>> proc" command.
>>>>> 3) I used ipconfig to check the ip address of the target and gave this
>>>>> ip address to the Tools/Options/Device Tools/Devices/<my
>>>>> target>/Properties/Configure. This did not work, and I couldn't ping
>>>>> the device.
>>>>> So I set a static ip address for the device in platform.reg file.
>>>>> Repeating the steps above, I could ping the device without any packet
>>>>> loss. But this did not work either.
>>>>> 4) I used connect to device icon on the device toolbar of the
>>>>> application dev. instance of VS. Got "Connection failed. The device is
>>>>> not ready" message.
>>>>> 5) With/out step 4 I did Debug/Start debugging and got the following
>>>>> error:
>>>>> 1>------ Deploy started: Project: REG-TAP, Configuration: Debug
>>>>> Heitec_MFC (ARMV4I) ------
>>>>> 1>Device is not ready. If target is an ActiveSync device, verify
>>>>> whether ActiveSync connection is running.
>>>>> 1>
>>>>> 1>Connect to device failed.
>>>>> 1>
>>>>>
>>>>> Since I am both developing the platform and the application, I do not
>>>>> want to use ActiveSync, because it doesn't work on the downloaded OS
>>>>> image (I don't know why) and I want to use the ethernet connection for
>>>>> both debugging. I read that establishing this connection is a painful
>>>>> experience, but I am out of ideas and I really need help on this. I
>>>>> will be very greatful for any kind of help.
>>>>>
>>>>> P.S. for the MS guys who read this: I think it was a terrible idea to
>>>>> integrate PB in VS, I find it very difficult to manage most of the
>>>>> things which I could do easily on CE 4.x. (Not being able to add MFC
>>>>> apps as subproject to a platform wasted my whole week for example)
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>> Selin
>>