"Add Driver" catalog/BSP dependency issue

Tutorials Win: Microsoft Windows Forum

I'm using the PXA27x developer's kit (WinCE 5.0) and have cloned the
MainstoneII platform. Using the BSP wizard I've added a NDIS driver for
the LAN91C111 Ethernet controller. In the catalog, the driver seems to end
up in the right place, i.e. in the cloned BSP under "Device
Drivers\Networking\Local Area Networking (LAN) devices\LAN91C111".
Inspecting the generated cec-file entries for my added driver, these look
(as expected) very similar to the corresponding entries for the global LAN
drivers (defined in netcard.cec). I can't e.g. find any added dependencies
for my added driver.

However, when I add my added driver to my OS design, the driver ends up
with a red cross in the driver list, indicating that it will not be
included in my build. When inspecting why my driver is excluded I'm told
to add any of the following features;
- USB Flash Config Tool
- RNDIS client
- Wireless LAN (802.11) STA - Automatic Configuration and 802.1x
- USB Remote NDIS class driver

If I include one of the global LAN drivers instead, e.g. RealTek RTL8139,
I get no dependency errors (i.e. no red cross).

Since the cec-dependencies look the same, why am I getting these
dependencies for my own added BSP driver when I don't get them for a
global driver ? Where can I find (and change) these dependencies when
adding my driver to the BSP ?

Regards,
Leif O

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Top

Re: "Add Driver" catalog/BSP dependency issue by Yannick

Yannick
Fri Oct 22 00:43:32 CDT 2004

Do you have a MODULE_NAME entry in your CEC ? Does this module is listed in
your Platform.bib file ?

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
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
----------------------------------------------------------------

"Leif O" <leif_nospam@vmetro.no> wrote in message
news:opsf740ozv0siefu@msnews.microsoft.com...
> I'm using the PXA27x developer's kit (WinCE 5.0) and have cloned the
> MainstoneII platform. Using the BSP wizard I've added a NDIS driver for
> the LAN91C111 Ethernet controller. In the catalog, the driver seems to end
> up in the right place, i.e. in the cloned BSP under "Device
> Drivers\Networking\Local Area Networking (LAN) devices\LAN91C111".
> Inspecting the generated cec-file entries for my added driver, these look
> (as expected) very similar to the corresponding entries for the global LAN
> drivers (defined in netcard.cec). I can't e.g. find any added dependencies
> for my added driver.
>
> However, when I add my added driver to my OS design, the driver ends up
> with a red cross in the driver list, indicating that it will not be
> included in my build. When inspecting why my driver is excluded I'm told
> to add any of the following features;
> - USB Flash Config Tool
> - RNDIS client
> - Wireless LAN (802.11) STA - Automatic Configuration and 802.1x
> - USB Remote NDIS class driver
>
> If I include one of the global LAN drivers instead, e.g. RealTek RTL8139,
> I get no dependency errors (i.e. no red cross).
>
> Since the cec-dependencies look the same, why am I getting these
> dependencies for my own added BSP driver when I don't get them for a
> global driver ? Where can I find (and change) these dependencies when
> adding my driver to the BSP ?
>
> Regards,
> Leif O
>
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/


Top

Re: "Add Driver" catalog/BSP dependency issue by Leif

Leif
Fri Oct 22 02:12:37 CDT 2004

Thanks for the tip, Yannick! Yes, I have a MODULE_NAME entry in my cec and
had the corresponding module included in my platform.bib as follows:

; @CESYSGEN IF !CE_MODULES_VMINI
LAN91C111.dll $(_FLATRELEASEDIR)\LAN91C111.dll NK SH
; @CESYSGEN ENDIF !CE_MODULES_VMINI

This way, I was hoping to include my driver ONLY if I didn't already use
the adapter for KITL/vmini. Obviously this conditional statement is not
correct (or was evaluated FALSE for som reason), because if I remove the
CESYSGEN IF/ENDIF pair (i.e. always include my driver in the image) my
dependecy issues disappear. If I try other conditional statements that I
know will evaluate to TRUE, it also works fine.

However, now I suddenly got a driver removal dependency problem!!! If I
try to remove my LAN driver I get a dialog telling my that pretty much
every catalog item I've included (e.g. TCPIP, Serial, GDI, GWES) depends
on my driver. This is of course wrong. Is this also something that has to
do with my platform.bib or is it the cec-file ?

For reference my cec-file's driver part is as follows:

...
ComponentType
(
Name ( "Local Area Networking (LAN) devices" )
GUID ( {591933E4-F657-11D4-98BF-00105AC7334D} )
Description ( "Network" )
Group ( "\Device Drivers\Networking" )
Vendor ( "Microsoft" )
HelpID ( 482 )
MaxResolvedImpsAllowed( 999 )
RequiredCEModules( ALL, "device ndis" )
Implementations
(
Implementation
(
Name ( "LAN91C111 NDIS miniport" )
GUID ( {D988F449-C8CC-4AE6-AA64-EDCE2FFE21C4} )
Description ( "SMSC LAN91C111" )
BSPPlatformDir ( "MAINSTONECLONE" )
Version ( "5.0.0.0" )
Locale ( 0409 )
Vendor ( "Microsoft" )
Date ( "21/10/2004" )
Variable( "MODULE_NAME", "LAN91C111.dll" )
SizeIsCPUDependent( 1 )
BuildMethods
(
BuildMethod
(
GUID ( {0EC946F7-A0F0-4B78-9631-F1C08EFFD0FC} )
Step ( BSP )
CPU ( "ARMV4I" )
Action
( '#SRCCODE(SOURCES,"$(_WINCEROOT)\PLATFORM\MAINSTONECLONE\SRC\DRIVERS\LAN91C111",
"LAN91C111")' )
)
)
)
)
)
...

Regards,
Leif O



On Fri, 22 Oct 2004 07:43:32 +0200, Yannick Chamming's [eMVP]
<ychammings_nospam@adeset.com> wrote:

> Do you have a MODULE_NAME entry in your CEC ? Does this module is listed
> in
> your Platform.bib file ?
>
> --
> ----------------------------------------------------------------
> Yannick Chamming's (eMVP)
> 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
> ----------------------------------------------------------------
>
> "Leif O" <leif_nospam@vmetro.no> wrote in message
> news:opsf740ozv0siefu@msnews.microsoft.com...
>> I'm using the PXA27x developer's kit (WinCE 5.0) and have cloned the
>> MainstoneII platform. Using the BSP wizard I've added a NDIS driver for
>> the LAN91C111 Ethernet controller. In the catalog, the driver seems to
>> end
>> up in the right place, i.e. in the cloned BSP under "Device
>> Drivers\Networking\Local Area Networking (LAN) devices\LAN91C111".
>> Inspecting the generated cec-file entries for my added driver, these
>> look
>> (as expected) very similar to the corresponding entries for the global
>> LAN
>> drivers (defined in netcard.cec). I can't e.g. find any added
>> dependencies
>> for my added driver.
>>
>> However, when I add my added driver to my OS design, the driver ends up
>> with a red cross in the driver list, indicating that it will not be
>> included in my build. When inspecting why my driver is excluded I'm told
>> to add any of the following features;
>> - USB Flash Config Tool
>> - RNDIS client
>> - Wireless LAN (802.11) STA - Automatic Configuration and 802.1x
>> - USB Remote NDIS class driver
>>
>> If I include one of the global LAN drivers instead, e.g. RealTek
>> RTL8139,
>> I get no dependency errors (i.e. no red cross).
>>
>> Since the cec-dependencies look the same, why am I getting these
>> dependencies for my own added BSP driver when I don't get them for a
>> global driver ? Where can I find (and change) these dependencies when
>> adding my driver to the BSP ?
>>
>> Regards,
>> Leif O
>>
>> --
>> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
>



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Top

Re: "Add Driver" catalog/BSP dependency issue by charlz

charlz
Fri Oct 22 11:02:23 CDT 2004

Leif,
Try this...
* Choose your own BSP variable for your driver. Something like
BSP_SMSC_LAN91C11
* Put the CESYSGEN filtering back in the platform.bib file like you used to
have for VMINI, but use your BSP_SMSC_LAN91C11 instead
(you should probably also do something similar for any registry entries
specific to this driver by editing the platform.reg file)
* Edit the CEC file to have
Variable( "BSP_SMSC_LAN91C11", "1" )

put this right after the MODULE_NAME variable in the CEC file

I hope this helps.

/Chuck

Top

Re: "Add Driver" catalog/BSP dependency issue by Leif

Leif
Mon Oct 25 02:02:40 CDT 2004

Thanks Chuck!

I got it all working as expected now.

Regards,
Leif O

On Fri, 22 Oct 2004 16:02:23 GMT, Chuck Zalinski
<charlz@online.microsoft.com> wrote:

> Leif,
> Try this...
> * Choose your own BSP variable for your driver. Something like
> BSP_SMSC_LAN91C11
> * Put the CESYSGEN filtering back in the platform.bib file like you used
> to
> have for VMINI, but use your BSP_SMSC_LAN91C11 instead
> (you should probably also do something similar for any registry entries
> specific to this driver by editing the platform.reg file)
> * Edit the CEC file to have
> Variable( "BSP_SMSC_LAN91C11", "1" )
>
> put this right after the MODULE_NAME variable in the CEC file
>
> I hope this helps.
>
> /Chuck
>



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Top