Re: Device driver crash ?? - in udevice.exe

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Chris,

Wow - I found a post from someone else who got an ebox going - it said that
he used the eboot.bin from the BSP package !!. I didn't even know that
existed ;-O. Anyway - I put that one onto my ebox and ITS BOOTED :-)) - using
eboot.bin :-O.

First time I have seen that in well over 6 months of using PB :-O.

Now I have to get the debugger installed onto my main OS - load up my own
app - and see what happens and if my system crashes :-O.

Thanks again - will get back once I've had a play with the debugger :-O.

Regards

Graham


"Chris Tacke, eMVP" wrote:

How are you getting the image to the device? Typically your bootloader will
have some bootme option, you select it, and it starts broadcasting. PB sees
that and then pushes down the image. If you built it with KITL enabled, you
then have a debugger. This certainly works with the eBox.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com




"GrahamS" <GrahamS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D63775A8-CDB7-44E5-9C26-80913AB1CE98@xxxxxxxxxxxxxxxx
Chris,

Thanks for the response - I am currently trying (again) to do this, and
having little success. As mentioned in my first post I have never yet
managed
to get any form of remote debugging working on this project - is there a
GOOD
document somewhere which explains this (KITL etc.) process ??.

I have followed instructions with my BSP quick-start guide, and I 'think'
that I have enabled KITL, but it won't connect over an ethernet
connection.
NB I need to use the serial ports for my app - so need KITL to use
Ethernet.

Its the documentation to understand KITL and debugging in general that i
have not been able to find :-((.

Many Thanks

Regards

Graham


"Chris Tacke, eMVP" wrote:

I'd do a Debug build of the OS and try running again with KITL attached.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

"GrahamS" <GrahamS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:596A1B28-1FED-4907-9B42-640D649C7A31@xxxxxxxxxxxxxxxx
Hi,
Have a CE 6 R2 based system running in an ICOP eBox 2300sx (x86-based)
box -
and am experiencing :

"Application udevice.exe has encountered a serious error and must shut
down"

My .Net CF 3.5 app uses multiple threads :

UI, Serial port (Com1) and Sockets interface

It used to use a USB device on the serial thread but that kept
stopping -
so
I moved to Com1. The devices connected are 9600 baud Modbus modules. I
have
also (I hope) disabled the CE debugger on Com1 - as advised by the
box/BSP
supplier.

I keep (not very often - sometimes after an hour, sometimes after a
couple
of days) getting a seemingly random crash with the above message. This
crash
is NOT highly repeatable and may be limited to this application/OS
build
version ;-O - so I need to understand it whilst its there ;-).

My threads all have exception handlers at various levels (writing to my
log
file) - including a catch-all wrapper to restart the thread and an
outer
catcg-all at app startup. The app is Form-based although the UI is for
development only.

All threads have logging capability and are writing to a local text
file
regularly.

The serial port thread is the one which stops when the above popup
message
box appears. No exception is caught in my app and thus no logging - all
I
can
see is what I was doing up to that point = nothing unusual.

The sockets interface continues to run and report up to my
Internet-based
database, and the UI has a time of day which continues to run in a
timer
event.

It 'looks' to me as though data just stops being received when this
popup
shows and my thread 'stops' - but I have no way to identify what the
actual
error is :-O

NB The application is built in 'Release mode' - and I have never yet
managed
to get the remote debug interface running - so have no access to remote
tools
- I can however read the registry and run Explorer etc. on the
development
system (normally there is NO UI - no screen, no keyboard etc.). I also
still
have FTP access, so can upload and run a test app it that helps.

I have tried to run a 'TaskManager' - and this shows me the various
processes and threads, but with insufficient detail to identify procs,
vs
threads etc. Yet to find a suitable 'Process Monitor' to run on this.

I find references which say that udevice.exe is a service handler for
all
device drivers - and it seems to be running some 33 threads - normally
:-O.
One thread seems VERY busy and consumes a lot of CPU time.

Could someone point me at some advice on how to track down what this
udevice.exe error really is (as the popup is all but meaningless :-O),
and
maybe how to add some code to identify process, device driver info etc.
etc.

Also - why is this happening 'outside' my app - so that my own
exception
handlers don't catch it ??. How can I catch this type of error.

Many thanks - (hopefully as this is a new product currently in field
trials
and I need to fix (or at least better understand and create a
workaround)
this problem soon....

Rapidly going bald with tearing my hair out on this one ;-O.

Regards

Graham







.

Relevant Pages

  • Re: A little experiment
    ... The most of You guys use kernel debugger and KITL enabled. ... > different templates and corresponding Platform SDKs for eVC. ... when the GUI app is closing (WinMain execution finishes ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Device driver crash ?? - in udevice.exe
    ... Cleared out the MS SerialPort ... Thanks again - will get back once I've had a play with the debugger:-O. ... document somewhere which explains this (KITL etc.) process ??. ... NB I need to use the serial ports for my app - so need KITL to use ...
    (microsoft.public.windowsce.embedded)
  • Re: Reprise: Pended IOCtrl + LoadLibrary == Deadlock?
    ... the original probelm in the debugger, ... and execute!htrace in both devenv.exe and the target app. ... > If I try to reproduce the error by launching the app from DevStudio, ... >>> ....looking at the docs for STARTUPINFO, ...
    (microsoft.public.development.device.drivers)
  • Re: Reprise: Pended IOCtrl + LoadLibrary == Deadlock?
    ... I have run appverifier and!htrace on the app. ... If I try to reproduce the error by launching the app from DevStudio, ... >> ....looking at the docs for STARTUPINFO, ... > you seem to have KD and a user mode debugger. ...
    (microsoft.public.development.device.drivers)
  • Re: Device driver crash ?? - in udevice.exe
    ... Chris Tacke, Embedded MVP ... document somewhere which explains this (KITL etc.) process ??. ... NB I need to use the serial ports for my app - so need KITL to use ... The serial port thread is the one which stops when the above popup ...
    (microsoft.public.windowsce.embedded)