Query on adding driver to a platform

Hi all,

I need to add a device driver to a platform created...I did the
following steps.

1) Added the driver to the respective BSP through the BSP wizard
2) edited the platform.reg and added the respective entries
3) edited the platform.bib and added the name of the dll as
required...

when I build the platform, the driver.dll file is getting created,
which is displayed on the output of the IDE...

But when i download the OS image and check for the driver whether
loaded or not

using the CE Target control,

I typed the command :

gi mod

This doesn't list my driver and so I take it as it's not included in
the nK.bin...

What would have gone wrong...

Can anybody throw somelight on this topic...

Thanks,

Shiva P

Yannick
Wed Nov 12 08:17:52 CST 2003

in the build log, do you see your dll listed in the make image step ?
If yes, the dll is included in the image. Then, if is not mounted, it is
probably an issue around your registry settings
If no, the driver is not included in the image -> issue in the .bib file

--
----------------------------------------------------------------
Yannick Chamming's
ADESET
Windows Embedded Manager
ychammings_AT_adeset_DOT_com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"Shiva Prasad T.S." <tsshivaprasad@yahoo.com> wrote in message
news:9abba1ea.0311120305.6c856967@posting.google.com...
> Hi all,
>
> I need to add a device driver to a platform created...I did the
> following steps.
>
> 1) Added the driver to the respective BSP through the BSP wizard
> 2) edited the platform.reg and added the respective entries
> 3) edited the platform.bib and added the name of the dll as
> required...
>
> when I build the platform, the driver.dll file is getting created,
> which is displayed on the output of the IDE...
>
> But when i download the OS image and check for the driver whether
> loaded or not
>
> using the CE Target control,
>
> I typed the command :
>
> gi mod
>
> This doesn't list my driver and so I take it as it's not included in
> the nK.bin...
>
> What would have gone wrong...
>
> Can anybody throw somelight on this topic...
>
> Thanks,
>
> Shiva P

tsshivaprasad
Thu Nov 13 01:21:36 CST 2003

> in the build log, do you see your dll listed in the make image step ?
> If yes, the dll is included in the image. Then, if is not mounted, it is
> probably an issue around your registry settings
> If no, the driver is not included in the image -> issue in the .bib file
>
> --
> ----------------------------------------------------------------


Hi, Yannick,

Thanks for your suggestion...No, In th build log of PB 4.2 ,I don't
see my dll listed in the make image step..

But I see my driver dll(mydriver.dll) listed in the build log, pls see
the following :



Pass 1...
Pass 2...
RAM AutoSize: RAM Start=811ac000 RAM Size=00a54000
..........
.............
Module Mydriver.dll at offset 01ec2000 data, 02fc1000 code
.......
.......
.........


Processing NK
MODULES Section
Module Section Start Length psize vsize
Filler
---------------------- -------- --------- ------- ------- -------
------
Mydriver.dll .text 80e72000 36864 34304
34299 o32_rva=00001000
....
....
Mydriver.dll .data 80eb4664 44889 44889 62396
.......
........
Mydriver.dll E32 80ba6c0c 108
FILLER
........
.......
Mydriver.dll O32 80ba6c78 48
FILLER
....
...
Mydriver.dll FileName 80364ec4 13
FILLER

This is all the entries I have in the Build Log...

In the platform.bib,I had given the following entry.

Mydriver.dll $(_FLATRELEASEDIR)\Mydriver.dll NK SH

In the Platform.reg, I had given the following entry.

;*******************************************************************************

[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\MYDRIVER]
"Dll"="ndis.dll"
"Prefix"="NDS"
"Miniport"="MYDRIVER"

[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\Detect\101]
"Dll"="MYDRIVER"
"Entry"="DetectMyDrv"

[HKEY_LOCAL_MACHINE\Comm\MYDRIVER]
"DisplayName"="MYDRIVER"
"Group"="NDIS"
"ImagePath"="MYDRIVER.dll"

; default TCP/IP settings
[HKEY_LOCAL_MACHINE\Comm\EAGLEND51\Parms\TcpIp]
"EnableDHCP"=dword:1
; This should be MULTI_SZ
"DefaultGateway"=""
; Use zero for broadcast address? (or 255.255.255.255)
"UseZeroBroadcast"=dword:0
; Thus should be MULTI_SZ, the IP address list
"IpAddress"="192.168.0.99"
; This should be MULTI_SZ, the subnet masks for the above IP
addresses
"Subnetmask"="255.255.255.0"


;***********************************************************************

somebody told me that,the Mydriver.dll copy should also be there in
the
winceroot/platform/cepc/target/x86/retail directory....

I had made sure of that too...

So pls let me know what else to be done to have Mydriver.dll to be
included in the makeimg in the build process...

Pls let me know if i miss anything out here...

thanks Yannick...

bye,

Shiva P

Lakshman
Thu Nov 13 03:16:28 CST 2003

Hi Shiva,
U need to put an entry in the project.bib file
and not the platform.bib file
Lemme know if it worked.

Cheers,
Lakshman
>-----Original Message-----
>> in the build log, do you see your dll listed in the
make image step ?
>> If yes, the dll is included in the image. Then, if is
not mounted, it is
>> probably an issue around your registry settings
>> If no, the driver is not included in the image ->
issue in the .bib file
>>
>> --
>> -------------------------------------------------------
---------
>
>
>Hi, Yannick,
>
>Thanks for your suggestion...No, In th build log of PB
4.2 ,I don't
>see my dll listed in the make image step..
>
>But I see my driver dll(mydriver.dll) listed in the
build log, pls see
>the following :
>
>
>
>Pass 1...
>Pass 2...
>RAM AutoSize: RAM Start=811ac000 RAM Size=00a54000
>...........
>..............
>Module Mydriver.dll at offset 01ec2000 data, 02fc1000
code
>........
>........
>..........
>
>
>Processing NK
>MODULES Section
>Module Section Start Length
psize vsize
>Filler
>---------------------- -------- --------- ------- -------
-------
>------
>Mydriver.dll .text 80e72000
36864 34304
>34299 o32_rva=00001000
>.....
>.....
>Mydriver.dll .data 80eb4664 44889
44889 62396
>........
>.........
>Mydriver.dll E32 80ba6c0c
108
>FILLER
>.........
>........
>Mydriver.dll O32 80ba6c78
48
>FILLER
>.....
>....
>Mydriver.dll FileName 80364ec4
13
>FILLER
>
>This is all the entries I have in the Build Log...
>
>In the platform.bib,I had given the following entry.
>
>Mydriver.dll $(_FLATRELEASEDIR)
\Mydriver.dll NK SH
>
>In the Platform.reg, I had given the following entry.
>
>;********************************************************
***********************
>
>[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\MYDRIVER]
> "Dll"="ndis.dll"
> "Prefix"="NDS"
> "Miniport"="MYDRIVER"
>
>[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\Detect\101]
> "Dll"="MYDRIVER"
> "Entry"="DetectMyDrv"
>
>[HKEY_LOCAL_MACHINE\Comm\MYDRIVER]
> "DisplayName"="MYDRIVER"
> "Group"="NDIS"
> "ImagePath"="MYDRIVER.dll"
>
>; default TCP/IP settings
>[HKEY_LOCAL_MACHINE\Comm\EAGLEND51\Parms\TcpIp]
> "EnableDHCP"=dword:1
> ; This should be MULTI_SZ
> "DefaultGateway"=""
> ; Use zero for broadcast address? (or 255.255.255.255)
> "UseZeroBroadcast"=dword:0
> ; Thus should be MULTI_SZ, the IP address list
> "IpAddress"="192.168.0.99"
> ; This should be MULTI_SZ, the subnet masks for the
above IP
>addresses
> "Subnetmask"="255.255.255.0"
>
>
>;********************************************************
***************
>
>somebody told me that,the Mydriver.dll copy should also
be there in
>the
>winceroot/platform/cepc/target/x86/retail directory....
>
>I had made sure of that too...
>
>So pls let me know what else to be done to have
Mydriver.dll to be
>included in the makeimg in the build process...
>
>Pls let me know if i miss anything out here...
>
>thanks Yannick...
>
>bye,
>
>Shiva P
>.
>