Windows CE 6.0 remote tools broken?

[al...@idxonline.com]

I'm having lots of problems trying to connect to a CE 6.0 device using
the remote tools like registry viewer. The device is connected via
Ethernet and debugging via Visual Studio 2005 works fine. I haven't
been able to resolve it, after doing/checking the following:

- made sure KITL enabled build setting is on and all the KITL settings
in the connectivity options are checked.

-Tried debug and release builds

- I am trying to use KITL Tranpsort as transport and CESH as startup
server - I get the error "Unable to load device side components. Please
check server configuration settings". These settings worked fine under
CE 5.0 platform builder (and still does).

- tried running both the CE 5.0 and CE 6.0 versions of the remote tools
directly by launching the .exe's without success.

- I have tried all other remote connection methods/combos
(KITL/CESH/MANUAL) without success.

What should I check I should have component-wise in my build to get
this working - as far as I can tell, my build has the same components
as my CE 5.0 version.

[Naveen]

Hi alext,

I am not sure whether this will work. but it worked fine for me...

Go to tools ... Click Device Emulator Manager.. Find out your device in
the list.. Connect to your device ( right click option).. IF device is
connected a green icon will be seen.. Now Right click and say cradle..
once this process finishes you will be able to see the remote reg
editor and use them.

Transport and start up server is both Microsoft Active Sync....

[al...@idxonline.com]

Thanks for your reply Naveen.

Unfortunately I am not using Activesync so the Device Emulator Manager
doesn't behave the same way :(

[Yan Sun [MSFT]]

Alex,

It seems you have two version of CE (5.0, and 6.0) on your machine. It could
cause mis-match on corecon connetion. Can you take a try on following steps
to see if that works for you:

1.. Copy c:\Program Files\Common Files\Microsoft
Shared\corecon\1.0\Target\wce400\%_TGTCPU%\* to the release dir
2.. Copy c:\Program Files\Windows CE Platform
Builder\5.00\CORECON\TARGET\%_TGTCPU%\tlkitlc.dll to the release dir (Or, in
CE6, c:\Program Files\Microsoft Platform
Builder\6.00\CORECON\TARGET\%_TGTCPU%\tlkitlc.dll)
3.. Boot the CEPC image inside PB
4.. Open a VS remote tool through Start Menu -> VS2005 -> Remote Tools and
connect.

<al...@idxonline.com> wrote in message
news:1164607235.7...@14g2000cws.googlegroups.com...

[al...@idxonline.com]

Yan,

I tried the following:

1) Copied files as in 1.. of your suggestion
2) Tried an image with 2.. of your suggestion for connection using CE 5
tools - still get the same error
3) Tried an image with 3.. of your suggestion using CE 6.0 tools - if I
use the TCP/Activesync connection combination as with the CE 5 device
template for example, I get a "Device not Ready" error. If I try use
the CE device template using KITL, I get an "unspecified error".

Are the files you have specified all the ones I need for connection
purposes. Anything else I should check in terms of connection settings?

[Javier Grijalba]

Hi ALex,
1)are you trying to connect without activesync like it is described here
http://msdn2.microsoft.com/en-us/library/ms228708(VS.80).aspx ?

2)are you unsing the files
-Clientshutdown.exe
-ConmanClient2.exe
-CMaccept.exe
-eDbgTL.dll
-TcpConnectionA.dll

found here
C:\Program Files\Common Files\Microsoft
Shared\CoreCon\1.0\Target\wce400\armv4i (depends of hardware)

3) or are you unsing the files
-Clientshutdown.exe
-ConmanClient2.exe
-tlkitlc.dll

found here
D:\Program Files\Windows CE Platform Builder\5.00\CORECON\TARGET\ARMV4I
(depends of hardware)

Regards
Javier

--
Javier Grijalba
www.positivesystems.com
Touch Panel PC systems
JGrijalba at Positivesystems dot com

[Yan Sun [MSFT]]

Alex,

Sorry for the late reply!
For 3), It seems the device connection setting is not right. Can you clean
up "C:\Documents and Settings\Your Name\Local Settings\Application
Data\Microsoft\CoreCon\1.0"(make a copy at your local) and try to reset your
connection setting? Thats what I did before.

<al...@idxonline.com> wrote in message
news:1164690004.9...@j44g2000cwa.googlegroups.com...

[B-Dawg]

Hi, Sorry this is a slightly different question but I can't find any way to
start a new message thread.... (I even clicked on something that said new
thread but nothing happened - firefox issue perhaps?)

I have an ARM board with a Cirrus EDB9302 processor. I have downloaded
their BSP for platform builder 6.0 and it compiles fine (in VS2005 with
platform builder 6.0) )and provides the correct output files etc. In the
project properties I enable KTL and the kernel debugger and I also select
debug mode as opposed to release for the build type. Everything seems to
build fine - no errors etc. I can install the generated eboot loader onto
the board through an application that came from Cirrus.

My problem is that under the target/connectivity options menu it does not
show any options for download/transport/debugger. It just has "None" in all
three boxes. I know I should get an option for ethernet in transport at
least along with some other options. What has gone wrong here? Is it
because this is the evaluation platform builder? I am running Visual Studio
2005 professional edition. Do I need to uninstall Active Sync perhaps? I've
already tried shutting it down and running multiple instances of VS2005.
There must be a setting I have missed somewhere.

Anyones help would be much appreciated.

Thank you

[Gary Swalling]

Hi B-Dawg,
The eval of CE6 (until it expires) is equivalent to the full version, except
for licensing....

VS2005 pro is what I'm using with CE6.

I'm using outlook express for the newsgroup and I have a button "New Post"
to start a new thread.

Have you included corecon in your platform? It's my understanding that
corecon replaces platform manager in CE6 as the mechanism for KITL to
operate.

Regards,
Gary

"B-Dawg" <B-D...@discussions.microsoft.com> wrote in message
news:5BAC8FB9-69BE-42A3...@microsoft.com...

[Dean Ramsier]

Kitl is its own transport, it has nothing to do with Platman/Corecon. This
should have just worked, it sounds like something is corrupted in your
install. Try deleting all the named devices, then create a new one (or use
the default).

If you build a reference BSP that comes with the kit, are your connectivity
options ok?

--
Dean Ramsier - eMVP
BSQUARE Corporation

"Gary Swalling" <garret....@spansion.com.nospam> wrote in message
news:eXNbPMIU...@TK2MSFTNGP04.phx.gbl...

[Gary Swalling]

Hi Dean,
So KITL is the transport used by the debugger, and on top of that
platman/corecon is used by the remote tools and CETK. Is that right?

Thanks,
Gary

"Dean Ramsier" <ramsie...@nospam.com> wrote in message
news:%23nANLZS...@TK2MSFTNGP03.phx.gbl...

[B-Dawg]

Hi Dean, Gary

Thanks for your replies - much appreciated.

I am out of town at the moment Gary so I cannot verify that I have included
corecon in the build so I will need to do that and get back to you.

In response to Dean I am building the standard Cirrus EDB9302 BSP (no mods)
it does not give me any options in the target/connectivity options menu but I
think it should because in the readme doc that comes with it it says that
after the build and the download of the bootloader I should then connect to
the device using VS2005 and download the nk.nb0 (I think they even give
pictures of the target/connectivity options menu showing the options I should
have but don't). This would be silly of them if they hadn't given me a build
that would be able to do that (ie missing corecon if Gary is right).

I haven't tried deleting all the named devices but I have tried creating my
own new ones - but still the same effect - "None" is the only option in all
the drop down boxes which is the case with the default "CE Device" which I
presume is the one I should be using.

What are you thoughts on Active Sync (on my PC) perhaps interferring in this
process? Seems unlikely to me. I have been using it to connect to a PDA to
develop some code recently.

I think it might be time for a reinstall of platform builder and/or VS2005
after checking the corecon thing...

Cheers,
Bevan

[B-Dawg]

Hi Gary,

I appreciate your help. Check my response to Dean if you want. I will
check corecon over the weekend and get back to you.

Cheers,
Bevan

[Dean Ramsier]

Kitl is always used by the kernel debugger, the Target | Connectivity
options don't give you any way to choose anything else. Applications can
ride on top of the existing kitl connection (if it exists), or they can use
a separate platman/corecon connection. Platman/Corecon don't sit on top of
Kitl, they are their own transport. The only connection between them would
be if kitl is also providing your ethernet link (vmini), so the ethernet
traffic generated by Corecon actually ends up going across the kitl link.

--
Dean Ramsier - eMVP
BSQUARE Corporation

"Gary Swalling" <garret....@spansion.com.nospam> wrote in message

news:eKgjEzTU...@TK2MSFTNGP04.phx.gbl...

[Yan Sun [MS]]

Try to delete Corecon data store by deleting following folder "C:\Documents

and Settings\Your Name\Local Settings\Application
Data\Microsoft\CoreCon\1.0"

yan

"B-Dawg" <BD...@discussions.microsoft.com> wrote in message
news:08125C2B-DFB0-44A7...@microsoft.com...

[B-Dawg]

Hey thanks Yan and the other guys for your suggestions.

After trying lots of various things I ended up just biting the bullet and
reinstalling Visual Studio and CE Platform Builder and it now works. I was
trying to avoid reinstalling platform builder as it is a massive download so
thank goodness it now works. I tried deleting the folder that Yan suggested
and it did nothing.

Therefore I must conclude that something got corrupted either at or soon
after the first install a couple of weeks or so ago of Platform Builder
(unless it was something in Visual Studio itself from before).

I'm looking forward to being able to finally play with the embedded ARM
board I've had for a while now.

Cheers,
Bevan

[Gary Swalling]

Hi Bevan,
I'm glad to hear you got it working.
Have you noticed any conflict with the Active Sync work you were doing?

Regards,
Gary

"B-Dawg" <BD...@discussions.microsoft.com> wrote in message

news:52683CDE-DF34-4ABD...@microsoft.com...

[B-Dawg]

Hi Gary,

I uninstalled Active Sync before I reinstalled everything else. It didn't
make any difference to my problem before but I don't think i'll reinstall it
for now since I aren't working with anything that needs it.

[B-Dawg]

Hi Gary,

Well I thought everything was going... I have spent the last day battling
through issues and have almost got it sorted. The stage I am at now is that
I can succesfully build an OS in platform builder CE 6.0, download it through
eboot to the board. I can then use KITL ethernet transport and Kdstub
debugging. I can access Remote Tools fine and check out various things on
the board.

Then came the connecting to VS2005 for managed application development in
C#. After several hours I discovered the need to have the have
ConmanClient2.exe and CMAccept.exe up and running on the board which I
achieved through including them in the build (with CEFileWiz) and then
manually starting them once things are booted up. I need to do this since I
don't have activesync going on the Target Board. This also corresponded with
me having to reinstall Active Sync.

I can successfully connect with Visual Studio 2005 (SP1) "Connect to
Device" and Remote Tools works fine from here too. The problem I have is
that after a build and Deploy or Debug, the application
"ConsoleApplication.exe" does not actually arrive over on the board as well
as edb.exe and whatever else it needs from the debug folder. I can get
around the extra debug files by including them in the build but that doesn't
fix the problem of the actual build file not being transfered across to the
target. With my previous activesync debugging experience the process of
getting the program over to the target happened automatically so I'm pretty
sure I'm not doing anything fundamentally wrong with clicking the right
buttons so to speak. There must be something else I have overlooked - either
in the OS build with regard to accepting new files outside the OS image into
RAM or a setting in VS2005.

Your help in this issue would be appreciated. I could have posted this to
the Application Development thread but I'll see what you or anyone else
thinks first.

[Gary Swalling]

Hi Bevan,
I've debugged and used remote tools with CE6 over enet, but I haven't used
activesync in a while, and I've never done managed applications. I'm not
sure that I will be much help on this, but one thing comes to mind when you
mention a scenario where things are automatically pulled from the debug
directory (I assume flatrelease directory on the host) and another scenario
where they are not transferred (but could be built into the image). Is the
difference retail vs debug builds of the OS?

If that's not it, then is there some step you need to take to push these
files over activesync?

Best regards,
Gary

"B-Dawg" <BD...@discussions.microsoft.com> wrote in message

news:B08F6899-2F1D-4CC9...@microsoft.com...

[Dean Ramsier]

I'm not an apps guy, but I did have to do this once. If I recall correctly,
the issues I ran into were:

- The versions of conmanclient/cmaccept etc that were included in the image
must be the ones from SP1. Note that they are updated with SP1, you need to
make sure they are insync
- Install the .NET Compact Framework 2.0 Service Pack 1 Patch

Once I got everything installed ( and I think I had to delete some database
stuff somewhere) everything magically started working. That patch was the
last key...

--
Dean Ramsier - eMVP
BSQUARE Corporation

"B-Dawg" <BD...@discussions.microsoft.com> wrote in message

news:B08F6899-2F1D-4CC9...@microsoft.com...

[Yan Sun [MS]]

There are some dependencies among VS, VS-SP1,PB, and PB-SP1. Before you
update VS-SP1, you might un-install PB, then install VS-SP1, and re-install
PB. Another dependency is that .NET Compact Framework depends on .NET 1.1.
Make sure you have both installed.
Speaking of the deploying problem Bevan got, I am not the root problem. If
he saw both "ConmanClient2.exe and CMAccept.exe " running, it means CoreCon
working fine. However, they should automatically start when you try "Remote
Tools". It seems there are still some problems on connectivity. I am not
sure if Bevan could send some debug messages.

thanks

yan

"Dean Ramsier" <ramsie...@nospam.com> wrote in message

news:O$92Cl5VH...@TK2MSFTNGP04.phx.gbl...

[B-Dawg]

Everything is magically going. I didn't really change anything that I can
think of - maybe just a few restarts etc and I can can run and debug a C#
application successfully on my WinCE board.

I don't quite follow the bit about conmanclient2.exe and cmaccept.exe
automatically running when I try remote tools. I thought remote tools used
the KITL transport or whatever it is called which is independant. These KITL
tools work fine. I have to use the "Target" menu items of "Target Control"
or "Run Programs" to run conmanclient2 and cmaccept. This was noted in
several blogs and online help webpages so I'm sure it doesn't start
automatically. I could put these programs into the registry though to make
them start on bootup. I just don't know how to make KITL use a fixed IP
address so I need to run ipconfig first to get the IP address before my
application can connect. If you know how to do that I'd love to hear from
you.

[Yan Sun [MS]]

Conmanclient2.exe,cmaccept.exe,ClientShutdown.exe, and dEbgTL.dll are part
of CoreCon structure. If you open "C:\Documents and Settings\Your Name\Local
Settings\Application Data\Microsoft\CoreCon\1.0\conman_ds_property.xsl", you
could see all those files there. If you use Visual Studio Remote
Tool(CoreCon based), those file should be automatically deploied, and run.
If you use platman Remote Tool(Kitl based), you dont have to run those
files. About fixed IP, I don't know the answer, and will try to ask around.

Thanks

yan

"B-Dawg" <BD...@discussions.microsoft.com> wrote in message

news:C585AAC8-8945-4E02...@microsoft.com...

[Yan Sun [MS]]

Bevan,

I got the answer regarding to your KITL fixed IP quesiton from our internal.
KITL uses auto-ip. For some mobile device like tonado uses fixed IP.
If you have further questions, please let me know.

yan

"B-Dawg" <BD...@discussions.microsoft.com> wrote in message

news:C585AAC8-8945-4E02...@microsoft.com...