Win CE 5.0 VS2005 connect

[at siconix @com Derek Ou]

Dear all,

I build a Win CE 5.0 image with .Net CF 2.0. Now, I would like to write
application in VS2005 and debug at the Win CE 5.0 system. But I couldn't
connect to the board through ethernet.

Using Win CE 5.0 remote tools, I can connect to the board using cemgrc.exe
/s /t ... Also, I generated an SDK from platform builder and build a C#
applicaiton to download to the board. Now, I follow the instructions on the
http://msdn2.microsoft.com/en-us/library/ms228708.aspx. The 5 files are
copied from the host PC \program files\...\Target\armv4i folder to device
\Windows\ folder through ftp server on board. But I just couldn't connect
to the board through VS2005 or VS2005 remote tools. In remote tools, it
will give me a message "The device is not ready". I verified the process
Conmanclient2.exe and cMaccept.exe running through Win CE 5.0 Remote Process
Viewer. So I don't know what else I can try. The debug serial port gave me
this message "Checking if extended
keep alive timeouts feature is set...No". I think it's the message when
cMaccept timeout.

I searched the newsgroup and found that people got problems as well. I
tried to remove the (user)\Local Settings\Application
Data\Microsoft\CoreCon\1.0. And it didn't help me. So any body has any
suggestion?

Thanks,
Derek

[at siconix @com Derek Ou]

I found the problem now. When I delete the

(user)\Local Settings\Application Data\Microsoft\CoreCon\1.0

folder, the VS2005 lost the connection configurations like TCPIP target
address. My problem is that I ran Remote Registry Editor before I ran
VS2005. As a result, VS2005 and remote tools both not working. After I
remofied the connection setting at VS2005, VS2005 connects. But it doesn't
seem to update the settings for remote tools.

So it's important to run VS 2005 and connect to the device right after
removing the CoreCon\1.0folder. Then everything connects.

Derek
"Derek Ou" <derek at siconix @ com> wrote in message
news:OGrc98zt...@TK2MSFTNGP02.phx.gbl...

[at siconix @com Derek Ou]

Now, I am running into a problem with the VS2005 debug. The connection is
fine. But when I deploy, VS2005 wants to download NETCFV2.wce5.armv4i.cab
to device \Windows. And it failed because I don't have enough spcae to
store this 5MB cab file.

But the why do I need this cab file? Is it for installing the .NET CF 2.0?
I aleady have .NET CF 2.0 included in the Win CE 5.0 image. If I build the
VS2005 C# project and copy this tst.exe to the device, it will run fine. I
think this mean that the .NET CF 2.0 is running fine on the device. Am I
right? If so, why do I need to download the cab file? Is the cab file for
debugging at VS2005?

Many thanks,
Derek

"Derek Ou" <derek at siconix @ com> wrote in message

news:uHMpAM0t...@TK2MSFTNGP02.phx.gbl...

[at siconix @com Derek Ou]

Found the answer from a previous post:
"If you go to the properties of your project in VS.NET 2005 and
click the 'Devices' tab you'll see 'Deploy the latest version
of the .NET Compact Framework (including Service packs)'. Uncheck
that and it shouldn't download any more."

"Derek Ou" <derek at siconix @ com> wrote in message

news:u30vc89t...@TK2MSFTNGP03.phx.gbl...

[Mario]

Hi Derek,

I am having some problems in setting up the system to debug from VS2005
as well. I am using i.MX21 ADS. The following are the steps that I
followed, please let me know if I missed something that you did to make
your setup successful:

1. Loaded image to board.
2. Copied files (Clientshutdown.exe, commanclient2.exe, CMaccept.ese,
eDbgTL.dll, and TcpConnectionA.dll) to the Windows folder in the device
using remote file viewer.
3.Ran commanclient2.exe from device command prompt.
4.Ran cMaccpet.exe from device command prompt (IP address setup in VS
2005 was set already).
5. VS2005 Debug/Start Debugging

After a little while, I get a message saying that it had problems
connecting. Did you do anything different that what I did? Thanks.

Regards,

Mario

[at siconix @com Derek Ou]

Hi, Mario,

Do you have problem just connecting VS2005 to Win CE 5.0? Or you have
problem deploying your project after connection is set up? I assume that
you are using the Remote File Viewer from Platform Builder, right? Have you
been able to use the remote tools for VS2005?

Derek
"Mario" <alpha...@hotmail.com> wrote in message
news:1155256396.2...@74g2000cwt.googlegroups.com...

[Mario]

Hi Derek,

I am trying to deployed my application to the WinCE device. I tried to
connect the device by going to VS2005/Tools/Coonect to Device... I get
an error that ActiveSync is not installed. I guess the answer to your
last question is that I have not been able to talk to my device from
VS2005. I have not problems talking to the device from Platform
builder. Any pointers is appreciated it. Thanks.

Cheers,

mario

[at siconix @com Derek Ou]

So did you set up the VS2005 device connection? It's from the menu,
tools->options and check devices. Which method are you going to connect
VS2005 to Win CE device? ActiveSync? Ethernet? USB?

"Mario" <alpha...@hotmail.com> wrote in message

news:1155336366.6...@i42g2000cwa.googlegroups.com...

[<ctacke/>]

PB and Studio use totally different connection mechanisms. Installing
ActiveSync is a good start - though not required. Google for connecting to
a CE 5.0 device without ActiveSync for the manual method.

-Chris

"Mario" <alpha...@hotmail.com> wrote in message

news:1155336366.6...@i42g2000cwa.googlegroups.com...

[Mario]

Hi Derek,

I have it set up with the following Device Tools/Device:

Transport: TCP Connect Transport
Use Specific IP Address (provided the IP of the device)
Unse fixed port number (unchecked)
Bootstrapper: ActiveSync Startup Provider

Under Transport and Bootstrapper I only have one option.

[Mario]

Hi Chris,

I did follow the msdn doc titled "How to: Connect Windows CE Device
Without ActiveSync" All steps were executed correctly until
deployment. From PB I checked that CMAccpet.exe and ConmanClient2.exe
were still running before I tried to deploy/debug the application from
VS2005. After going to Debug/Start Debugging, I got an error saying
that "There were deployment errors. Continue?" On the Error List, it
had "Connection failed" under Description and "Device Connectivity
Component" under File. I also tried to just connect to the device
through Tools/Connect to Device in VS2005 to no avail. The message was
"Connection failed. The device is not ready". All this was done while
ConmanClient2.exe and CMAccept.exe were still running in the device.

Thanks.

mario

[<ctacke/>]

Is the firewall part of the CE image? If so, make sure it's off.

-Chris

"Mario" <alpha...@hotmail.com> wrote in message

news:1155592470.7...@m79g2000cwm.googlegroups.com...

[Mario]

I do not think so. Which component shoulc I check for? Thanks.

Cheers,

Mario

[<ctacke/>]

The Firewall component.

SYSGEN_FIREWALL or
Core OS->Windows CE Devices->Communications Services and
Networking->Networking Features->Firewall

-Chris

"Mario" <alpha...@hotmail.com> wrote in message

news:1155599846....@b28g2000cwb.googlegroups.com...

[Mario]

Hi Chris,

I verified that firewall was not installed.

Cheers,

mario

[voidcoder]

What about your development PC? Are you running
a firewall? Also make sure the network connection
is configured properly on your device. You should
be able at least to ping the device.

[Mario]

I can ping the device without any lost packets. Does the image need to
be in debug or can I use the release version? I am using the release
version as PB fails to build a debug version of the OS.

Cheers,

mario

[voidcoder]

Do you use firewall on your development PC?

>> Does the image need to be in debug or can I usethe release version?

I think VS app level debugger will not run
together with PB kernel debugger, so Release
is the right choice.

[Srini]

Mario,

I am also having the exact same issue,
Did u get VS2005 to connect/debug/deploy with win ce 5.0 (PB) ?
Any info is much appreciated.

Thanks.

[Mario]

Hi,

Yes, I have it working. My fix was to change vmini.reg, under Hardware
Specific Files, to match the IP address and subnetmask that I had set.
Once you change that, you should be able to connect and debug from
VS2005. Hope this helps.

-- mario