Re: "No .rel file found for module "

Tech-Archive recommends: Fix windows errors by optimizing your registry

Sorry, I wasn't trying to ask you to go back through this thread, I was just
stating that it was there.

I started repling that way because that's how others seemed to be replying
(I thought maybe it was getting too deep in depth).

I aplogize for these things, I'm just getting frustrated overall. It seems
like a lot of the same questions get asked and I still am no further then
what I was on Monday when I started this whole mess.

To answer your question, the only debug message that came out was "11290
PID:c7f64ed6 TID:c7f640aa I2CClass::I2CClass: Error configuring IOMUX for
I2C."

And this occured only on the 2nd of 3 I2C devices registered. It is also
worth noting it occurs both on KITL and non-KITL loads, but on KITL loads all
3 of the devices are still registered as active. I also saw in code why this
occurs, (for some reason case 2 was left out of a switch statement).

"Bruce Eitman [eMVP]" wrote:

Please don't ask me to go through this entire thread to figure out what that
debug message was, I don't have time or energy for that to help you solve
your problem. What message and what function did that message come from?

Also, this would be easier to follow if you would reply to the message that
asks the question. For some reason you have started to reply to different
posts that the one that asked the question, that makes following the
discussion more difficult.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F2F97056-6EC2-4CC0-9DF2-5A624C42082A@xxxxxxxxxxxxxxxx
I do have source. All of the entrypoints that are expected exist, and I
compiled with debug messages in there and the only one that ever came out
is
what I mentioned earlier in this thread.

"Bruce Eitman [eMVP]" wrote:

Interesting. It doesn't look like this has the debug dev*.*. I expected
more output from loading the drivers. Could you also use the debug
shell.exe? Or better yet, remove the driver from the _FLATRELEASEDIR
before
starting the OS with KITL enabled.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5FB80F5E-3E33-4C83-8669-14819420B5B6@xxxxxxxxxxxxxxxx
Below is what I have logged for the output:

0 PID:0 TID:0 Sp=ffffc7cc
9034 PID:47f552a2 TID:47f6140a DeviceFolder::LoadDevice!Enumerate
Found
deprecated load instructions at (Drivers\BuiltIn\AFD). Driver cannot be
unloaded.
0 PID:0 TID:0 Sp=ffffc7cc
9435 PID:87f64ed6 TID:87f640aa SMSC_LAN911X Resource conflict! Base
address (0xB4000000) in use by KITL.
9435 PID:87f64ed6 TID:87f640aa SMSC_LAN911X Driver will not
initialize.
10666 PID:87f64ed6 TID:87f640aa DeviceFolder::LoadDevice!Enumerate
Found
deprecated load instructions at (Drivers\BuiltIn\AFD). Driver cannot be
unloaded.
10770 PID:87f64ed6 TID:87f640aa DeviceFolder::LoadDevice!Enumerate
Found
deprecated load instructions at (Drivers\BuiltIn\PPP). Driver cannot be
unloaded.
0 PID:0 TID:0 Sp=ffffc7cc
9438 PID:c7f64ed6 TID:c7f640aa VMini:: Kernel does not support
ethernet
sharing!
9447 PID:c7f64ed6 TID:c7f640aa SMSC_LAN911X Resource conflict! Base
address (0xB4000000) in use by KITL.
9447 PID:c7f64ed6 TID:c7f640aa SMSC_LAN911X Driver will not
initialize.
10678 PID:c7f64ed6 TID:c7f640aa DeviceFolder::LoadDevice!Enumerate
Found
deprecated load instructions at (Drivers\BuiltIn\AFD). Driver cannot be
unloaded.
10785 PID:c7f64ed6 TID:c7f640aa DeviceFolder::LoadDevice!Enumerate
Found
deprecated load instructions at (Drivers\BuiltIn\PPP). Driver cannot be
unloaded.
11290 PID:c7f64ed6 TID:c7f640aa I2CClass::I2CClass: Error configuring
IOMUX for I2C.
11474 PID:47dfea9e TID:47f647d6 Lyg.p: Layout Manager successfully
initialized to 1
16484 PID:c7f64ed6 TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\combined\lpd_imx31_mc13783\driver\main.cpp
line 1310: 16484 PID:c7f64ed6 TID:47f647d6 ADC operation timeout.
16484 PID:c7f64ed6 TID:47f647d6 MC13783_INT_STAT0 = 0x0
16484 PID:c7f64ed6 TID:47f647d6 MC13783_INT_MSK0 = 0x0
16484 PID:c7f64ed6 TID:47f647d6 MC13783_INT_STAT1 = 0x0
16484 PID:c7f64ed6 TID:47f647d6 MC13783_INT_MSK1 = 0x0
16484 PID:c7f64ed6 TID:47f647d6 GPIO1_ISR = 0x99fffc20 16484
PID:c7f64ed6
TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\combined\lpd_imx31_mc13783\driver\main.cpp
line 1471: 16484 PID:c7f64ed6 TID:47f647d6 PmicADCConvert failed!
16484 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\drvlib\mc13783_api\src\pmic_adc.cpp
line 387: 16484 PID:47dfea9e TID:47f647d6 PMIC_IOCTL_ADC_SET_MODE
failed!
16484 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\touch\lpd_imx31_touch\driver\bsptouch.cpp
line 153: 16484 PID:47dfea9e TID:47f647d6 PmicTouchInit:
PmicTouchStandby
failed
16484 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\touch\lpd_imx31_touch\driver\bsptouch.cpp
line 279: 16484 PID:47dfea9e TID:47f647d6 BSPTouchInit:
PmicTouchInit
failed
16484 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\touch\lpd_imx31_touch\driver\bsptouch.cpp
line 100: 16484 PID:47dfea9e TID:47f647d6 PmicTouchDeinit:
PmicInterruptDeregister failed
16484 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\drvlib\mc13783_api\src\pmic_adc.cpp
line 387: 16490 PID:47dfea9e TID:47f647d6 PMIC_IOCTL_ADC_SET_MODE
failed!
16490 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\touch\lpd_imx31_touch\driver\bsptouch.cpp
line 107: 16490 PID:47dfea9e TID:47f647d6 PmicTouchDeinit:
PmicTouchStandby failed
16505 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\touch\lpd_imx31_touch\driver\bsptouch.cpp
line 100: 16505 PID:47dfea9e TID:47f647d6 PmicTouchDeinit:
PmicInterruptDeregister failed
16521 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\drvlib\mc13783_api\src\pmic_adc.cpp
line 387: 16521 PID:47dfea9e TID:47f647d6 PMIC_IOCTL_ADC_SET_MODE
failed!
16521 PID:47dfea9e TID:47f647d6 ERROR:
d:\wince500\platform\loce\src\drivers\ce_drivers\touch\lpd_imx31_touch\driver\bsptouch.cpp
line 107: 16521 PID:47dfea9e TID:47f647d6 PmicTouchDeinit:
PmicTouchStandby failed
16976 PID:7d8eece TID:7d5c68a Explorer(V2.0) taskbar thread started.
924903 PID:c7f64ed6 TID:87e6a86a AUTORAS:: Dialer notifies: [1] [Dialer
Start]
926386 PID:a7cef3ae TID:a7cfe632 Posting WM_NETCONNECT(TRUE) message
926393 PID:c7f64ed6 TID:87e6a86a AUTORAS:: Dialer notifies: [4] [Dialer
Connected]

And yes, I am aware of the I2C error in there, that is what I had
mentioned
previously that I found once I connected via KITL.

"Bruce Eitman [eMVP]" wrote:

Do you have the debug output from loading with KITL enabled?

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:777A400D-AED4-41AB-A082-429A7B8778F9@xxxxxxxxxxxxxxxx
I would agree with that as well, yet I am taking a single binary
image,
loading it with and without KITL, and getting two different results.

Is it possible that the debug nature of KITL allows the driver to be
loaded
because of the timing difference you mentioned, or is the order
somehow
different with KITL?

"Dean Ramsier" wrote:

I tend to agree with Chris. KITL should have nothing to do with it
otherwise, except for a slight timing impact. Something isn't the
way
it
appears...

--
Dean Ramsier - eMVP
BSQUARE Corporation


"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2234DA29-AA05-475E-A2F7-958139BAAC01@xxxxxxxxxxxxxxxx
I wish it were that simple. It's definitely in the image, and the
registry
entry is present under "builtin", but there is just a blank spot
under
"active" where the number was skipped.

"<ctacke/>" wrote:

Sounds to me like it's not actually included in the image via a
bib
file,
but when loading using KITL relfsd might be pulling it in.


--

Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com



"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D84EBD59-5503-4302-A4F4-3F8A314EF767@xxxxxxxxxxxxxxxx
So in a strange twist to all of this mess, the driver loads
now.
Apparently
however, it will only load if I launch the image with KITL
enabled.
I
have
tried loading the exact same binary image several other ways
(serial
only
debug, auto loaded from the device on boot, etc), and it will
only
load
the
I2C driver when it is launched through KITL.



"AD" wrote:

I have been using a custom image, and I tried to pare it down
even
more,
but
still couldn't get very small.

Regardless, I was able to do a few things people mentioned
and
get
some
debug information out, and it turns out the driver code is
failing,
I
just
haven't figured out why yet. Since the driver is straight
from
the
vendor, I
was hoping it was something I was doing. Once I get this
taken
care
of,
I
should be good to go.

For future people with similar problems, I was able to get
the
information
out using a combination of Bruce's idea to copy the dev*.*
into
the
release
dir, and setting up KITL.


Thanks for all of the help!


"Dean Ramsier" wrote:

So use a different, more realistic (read, 'custom') OS
design.
In
my
experience, most people pick something 'standard' out of
the
wizard,
then
wonder why the image is so large. It's far better to set
up
your
OS
design
as custom and only pick the things you need. In many
cases,
devices
don't
really need all the network browsers, media player and
direct
Show
etc
that
eats up all the space.

Even if you do need this in your final device, you don't
need
it
to
.

Relevant Pages

  • Re: "No .rel file found for module "
    ... debug message was, I don't have time or energy for that to help you solve ... remove the driver from the _FLATRELEASEDIR ... address in use by KITL. ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... Could you also use the debug ... remove the driver from the _FLATRELEASEDIR ... address in use by KITL. ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... Could you also use the debug ... remove the driver from the _FLATRELEASEDIR before ... address in use by KITL. ...
    (microsoft.public.windowsce.app.development)
  • Re: just cut the kitl cord and my ethernet stopped working
    ... > I took out enable kitl out of the settings. ... > an ip address that was passed along to the debug ethernet connection. ... >> removes KITL support and other debug stuff. ... >> Also, I am not sure if you are aware, but KITl relies on ETHDBG driver to ...
    (microsoft.public.windowsce.platbuilder)
  • Re: "No .rel file found for module "
    ... KITL says that they are exported, but I double checked and they are ... remove the driver from the _FLATRELEASEDIR before ... "Dean Ramsier" wrote: ...
    (microsoft.public.windowsce.app.development)