Re: Need Help in Debugging StandAlone WInCE 6.0 App using PB/VS 20

On Apr 8, 1:50 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT no
instrument no spam DOT com> wrote:
Ethernet must have a driver in your OS or there will be no networking (of
course!).  When you've built a DEBUG build previously, you must have had the
Virtual Miniport Driver, VMINI, in the OS.  This allows the
KITL-over-Ethernet connection created between the device and Platform
Builder to also appear as a network adapter to the Windows CE OS.

When you no longer have KITL-over-Ethernet, you should remove VMINI and
include the driver for your network adapter.  If you don't, you'll have no
network, just like on your desktop where, if you don't have a driver for
your network card, you don't have a network card, as far as Windows is
concerned.

Paul T.

"DRAM" <D...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:9D3D819E-2D34-4192-B01E-447D4EB2616D@xxxxxxxxxxxxxxxx

OK. I see.

Yes, the device and the PC are on the same N/W. I will try to build as you
said with KITL off. It was on until now. But I don't need to build any
device
driver for the Ethernet H/W - do I?

All I need to do is have TCP and Networking components installed during
design phase (which I already have) . And I did include ActiveSycn in the
build as well.

Thanks. I will let you know in few minutes how things went. Thanks for all
the help.

Hi,

I've spent the past 3 days trying to get VS 2005 to allow me to debug
my application
code with my x86 CE 6.0 target device. I'm running two instances of
VS
2005 SP1; one for downloading my OS kernel image and debugging it via
KITL, and
the other instance of VS is to be used to debug application code
(built using SDK generated from the OS image).
I have solid connectivity with my target via KITL debugging, so I know
my
TCP/IP connection is solid.

I carefully followed instructions about setting up CoreCon in various
posts.
I copied (all files from 1.0\Target\<CPU>) the CoreCon files to the
\Windows folder on my target device. I can see
from the PB debug messages that ConManClient2.exe and CMAccept.exe are
starting up properly, when I launch them from the Target Control
window (CE
command prompt) of VS instance #1. In VS instance #2, I have
specified the
proper IP address for the CE device (it happens to be 192.168.1.10 for
me).
When I press the Connect button in VS, it pops up a "Connecting..."
dialog,
during which time I see a TCP packet fly out (Checked in wireshark)
from my dev workstation from
TCP port 1377, destined for my CE target device's TCP port 5655. The
packet
repeats about every 3 seconds, until VS eventually gives up and
reports,
"Connection failed. The device is not ready."

So it looks like my target is not seeing, or reacting to, the incoming
TCP
packet from my dev workstation. Do I need to have any special TCP/IP
catalog items installed in order to debug via ConManClient2.exe? I
assume
that ConManClient2 would complain when it starts up if necessary DLLs
were
missing on my target device. But it just sits there as a running
process.

I could able to ping the device. I couldn't able to telnet to it.
Telnet connection also fails.

Any suggestions are appreciated!

Ram
.

Loading