Re: "No .rel file found for module "

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
debug
your I2C driver. Build a 'lite' design that only has what you need for
driver development, then sit back and enjoy your 5MB (or far less if
headless) OS images.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:41504E8E-7C63-4C05-B98A-48AFE024B8D2@xxxxxxxxxxxxxxxx
That is what I would like to do. The problem is, a debug build is
too
large
and gives an error that it overlaps the rom area. Also, with the
source
code, I have not been able to get it in a fashion so that it will
allow me
to
step through it. The source is from Freescale's BSP, and I am using
a
different BSP and trying to integrate a driver from freescale. So
while I
have the source, I've only been able to integrate the driver as a
stand-alone
DLL, and even then not successfully (as mentioned in my first post on
this
thread).





"Dean Ramsier" wrote:

Have you done a debug build? That may tell you what device.exe
doesn't
like
about your dll, assuming it has gotten far enough to attempt to load
it.

You said you also have source? Use that to set a breakpoint in the
init
code and step through the loading process.
--
Dean Ramsier - eMVP
BSQUARE Corporation


"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1DEFDB2D-A4E5-470D-8D16-A3B6509B5A7A@xxxxxxxxxxxxxxxx
Thanks. I did see the information on the web, but nothing gives a
real
good
explanation for certain of what the problem is.

I thought maybe it was the registry data too, but it is pretty
basic:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\I2C]
"Prefix"="I2C"
"Dll"="i2c.dll"
"Index"=dword:1
"Order"=dword:30

The driver is straight from freescale and is supposedly good,
looking
at
the
source it looks pretty straight-forward.

For my call to ActivateDeviceEx, I simply passed the dll name and
then
zeros
for the rest. I would prefer to not even have to make the call
though,
I
would prefer the OS loads it automatically. It appears to be
trying to
(there is a gap in the number sequence of "Active" in the registry
when
this
device is present, but it never actually gets loaded.

Any other ideas or clues as to what I can look at?


"Bruce Eitman [eMVP]" wrote:

A quick google groups search would give you tell you about that
message.

http://groups.google.com/groups?as_q=No+.rel+file+found+for+module&num=10&scoring=r&hl=en&as_epq=&as_oq=&as_eq=&as_ugroup=microsoft.public.windowsce.*&as_usubject=&as_uauthors=&lr=&as_drrb=q&as_qdr=&as_mind=1&as_minm=1&as_miny=1981&as_maxd=28&as_maxm=1&as_maxy=2008&safe=off

So since that information is available, I will give you the short
answer.
That is not the problem. The problem is probably the information
in
the
registry, if we assume that the driver is good then it could also
be
your
code for ActivateDeviceEx. Have you contacted the vendor?

--
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:E0A51B6C-6EEE-42F1-80BE-C062128197E7@xxxxxxxxxxxxxxxx
I am trying to build a platform with a new driver file for which
I
only
have
the binary. I created a CEC file and all and was able to get
the
driver
added to the registry in the "builtin" folder, but cannot get
WindowsCE
(5.0)
to load the driver and place it in "Active". I tried doing it
manually
with
a call to "ActivateDeviceEx", and get a return of 1610 (bad
configuration).

Going back through my platform builder warnings, I found one
that
says
"No
.rel file found for module i2c.dll", which is the driver I'm
having
problems
with.

Does anyone know what this means and how to fix it?

Thanks in advance for any suggestions.

Adam












.

Relevant Pages

  • IRC Packets being generated. Dont know where from...
    ... *Registry value not found* ... Autorun entries from Registry: ... Enumerating ICQ Agent Autostart apps: ... RAS Asynchronous Media Driver: System32\DRIVERS\asyncmac.sys (manual ...
    (microsoft.public.security.virus)
  • Re: how to load in a build in driver whose index is greater 10 in Windows CE
    ... about the fact that numbers in the registry files are all hexadecimal, ... You must use the $device mount point to reference such a driver. ... Bruce Eitman [eMVP] wrote: ... But I likt this VCA12 as a build in driver, which will be load when the ...
    (microsoft.public.windowsce.platbuilder)
  • Re: "No .rel file found for module "
    ... about your dll, assuming it has gotten far enough to attempt to load it. ... I thought maybe it was the registry data too, ... The driver is straight from freescale and is supposedly good, ...
    (microsoft.public.windowsce.app.development)
  • hijack this startup - can someone tell me the hack i am experienci
    ... *Registry value not found* ... Enumerating ICQ Agent Autostart apps: ... Intel82801 Audio Driver Install Service: ... Application Management: %SystemRoot%\system32\svchost.exe -k netsvcs (manual ...
    (microsoft.public.windowsxp.security_admin)
  • Re: BSOD Error 0x000000B8
    ... *Registry value not found* ... Enumerating ICQ Agent Autostart apps: ... ADI UAA Function Driver for High Definition Audio Service: ... Application Management: %SystemRoot%\system32\svchost.exe -k netsvcs ...
    (microsoft.public.windowsxp.help_and_support)