Device hangs while loading

[Omkar Singh]

I have successfully build and downloaded the OS image for PXA255 board on the
device, but now my device hangs while loading the "iectl.dll". In debug
windows show the following msgs

"4294783641 PID:a3c9dca2 TID:c3a534ca 0x83a16400: RELFSD: Opening file
iectl.dll from desktop"
could you please explain me what is desktop here & what is the reason for
this problem.

I am using win ce 5.0 and choose 'internet applicance' from design template
while building the platform.

[Paul G. Tobey [eMVP]]

You've set up your image so that it can access files that it needs (DLLs,
mostly), from the flat release directory on your build machine. This is
useful for debugging a program, say, where you don't want to have to
download the whole OS, with the program built into nk.bin, every time you
make a little change to the program. You can just modify the code, rebuilt
the program alone, and making sure that the output gets put into the flat
release directory.

As for the problem, I can't tell you that. How is KITL set up? You're
seeing these messages in the debugger output window in Platform Builder, not
via the serial port on the actual device or something, right?

Paul T.

"Omkar Singh" <Omkar...@discussions.microsoft.com> wrote in message
news:EB947AB6-60C4-4ED6...@microsoft.com...

[Omkar Singh]

Yes I am seeing the msg in the debugger output window in Platform Builder.

You mean to say here desktop means the desktop computer on which I am
building the OS image. can you tell which folder it looks because the dll
'iectl.dll' is already prensent in '...\RelDir\EXA255_ARMV4I_Debug'
directory? Do I have to copy this dll somewhere else????

[Paul G. Tobey [eMVP]]

No, that's the right place. The file should be transferred, assuming you've
enabled that in the Target control settings in PB (Core Service Settings,
Enable Access to Desktop Files), to the device and loaded as though it was
in the \Windows folder on the device to begin with.

Paul T.

"Omkar Singh" <Omkar...@discussions.microsoft.com> wrote in message

news:E759D423-0F13-4B62...@microsoft.com...

[Dean Ramsier]

This is the classic symptom of the MTU size on your desktop set to a smaller
value than Platform Builder can handle. The result is that the packets sent
across the kitl transport link for relfsd are fragmented, and the transport
service can't handle that. The MTU size is often reduced when you install
some kind of VPN software on your desktop.

The symptom is the first attempt by relfsd to send a file across the debug
link appears to hang the kitl connection. It's not hung, if you snoop the
connection with an ethernet sniffer you'll see the packets being
continuously retried. It leaves no bandwidth for anything else to get done.

Figure out what the MTU is set to now, and increase it back to the normal
max (something like 1500)

--
Dean Ramsier - eMVP
BSQUARE Corporation

"Omkar Singh" <Omkar...@discussions.microsoft.com> wrote in message

news:E759D423-0F13-4B62...@microsoft.com...

[Omkar Singh]

Thanks Dean and Paul.
Its works. It was the MTU problem.