Re: Windows CE 6.0 remote tools broken?
- From: "Yan Sun [MS]" <yansun@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 5 Mar 2007 11:16:54 -0800
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" <BDawg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C585AAC8-8945-4E02-A8FF-F7B12245D08B@xxxxxxxxxxxxxxxx
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.
Cheers,
Bevan
"Yan Sun [MS]" wrote:
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" <ramsiernospam@xxxxxxxxxx> wrote in message
news:O$92Cl5VHHA.4668@xxxxxxxxxxxxxxxxxxxxxxx
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" <BDawg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B08F6899-2F1D-4CC9-99DF-64E721BB372C@xxxxxxxxxxxxxxxx
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.
Cheers,
Bevan
"Gary Swalling" wrote:
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" <BDawg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:52683CDE-DF34-4ABD-B331-997620FAF41E@xxxxxxxxxxxxxxxx
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
"Yan Sun [MS]" wrote:
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" <BDawg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:08125C2B-DFB0-44A7-B557-315D4CEFE30D@xxxxxxxxxxxxxxxx
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
"Gary Swalling" wrote:
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" <ramsiernospam@xxxxxxxxxx> wrote in message
news:%23nANLZSUHHA.4404@xxxxxxxxxxxxxxxxxxxxxxx
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.swalling@xxxxxxxxxxxxxxxxxxx> wrote
in
message
news:eXNbPMIUHHA.4832@xxxxxxxxxxxxxxxxxxxxxxx
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-Dawg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5BAC8FB9-69BE-42A3-90B4-8AE1FB5FBBB2@xxxxxxxxxxxxxxxx
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
"alext@xxxxxxxxxxxxx" wrote:
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
.
- References:
- Re: Windows CE 6.0 remote tools broken?
- From: B-Dawg
- Re: Windows CE 6.0 remote tools broken?
- Prev by Date: Re: about how to using of touch screen driver
- Next by Date: Problem with AMD Rumba Design Reference
- Previous by thread: Re: Windows CE 6.0 remote tools broken?
- Next by thread: Re: Windows CE 6.0 remote tools broken?
- Index(es):
Relevant Pages
|
