Re: RNDIS USB KITL

From: Andrew (anonymous_at_discussions.microsoft.com)
Date: 02/27/04 

Date: Thu, 26 Feb 2004 16:24:10 -0800

Hi Glenn, I just seem to be having some trouble getting
the Net2890 to compile. I want to get it compiled and
linked with RNDIS now before I modify it to ensure that
all bugs are garenteed to be mine.

I copy and rename the Net2890 driver to my driver
directory:

...\<PLATFORM_NAME>\DRIVERS\ETHDBG\USBRNDIS

and add the following line to the TARGETLIBS:

$(_TARGETPLATROOT)\lib\$(_CPUDEPPATH)\usbrndis.lib

to:

...\<PLATFORM_NAME>\eboot\sources
...\<PLATFORM_NAME>\kernel\buildexe\kernkitl\sources
...\<PLATFORM_NAME>\kernel\buildexe\kernkitlprof\sources

I included the driver directory in the "dir" file,
changed the name of the *.def file and I changed the
sources file of the driver to:

################
DEFFILE=usbrndis.def

TARGETNAME=usbrndis
TARGETTYPE=DYNLINK
WINCEOEM=1
NOMIPS16CODE=1

RELEASETYPE=PLATFORM

DLLENTRY=DllEntry

SOURCELIBS= \
 $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\rndismini.lib

TARGETLIBS= \
 $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\ceddk.lib \
 $(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\ndis.lib \
 $(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib

SOURCES= \
 2890.c \
 pci.c \
 PlxEeprom.C

################

When I "rebuild platform", I can't link to the "Rndis"
functions in rne_mdd.

So I add:

$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\rne_mdd.lib

to the three sources files mentioned above and I get the
errors and warnings mentioned at the end of this post.

Q1) RNE_MDD\rndis.c calls "NKCreateStaticMapping()" which
doesn't seem to be included in the build. The PB help
says that I have to link "Coredll.lib" to include the
function but I seem to get the same error, even though I
have included it in my USB RNDIS driver "sources" file.

Q2) The "__rt_udiv" warnings still persist even though I
have placed "NOMIPS16CODE=1" in my three main "sources"
files (mentioned above) as well as in my driver sources
files.

Q3) The "rne_mdd" driver can't seem to see the "PDDInit"
function that is in the Net2890 driver. Not sure why
cause I'm assuming I have linked both libraries by adding
them both to my "sources" files.

The WinCE gods are not shining on me this week.

Any help would be appreciated, Andrew

P.S. warnings and errors follow
=========
e:\wince420\platform\rtunet\eboot\rne_mdd.lib
(rndis.obj) : warning LNK4217: locally defined symbol
__rt_udiv imported in function RndisPrepareRndisPacket

e:\wince420\platform\rtunet\eboot\rne_mdd.lib
(hostmini.obj) : warning LNK4049: locally defined symbol
__rt_udiv imported

e:\wince420\platform\rtunet\eboot\rne_mdd.lib(util.obj) :
warning LNK4049: locally defined symbol __rt_udiv imported

e:\wince420\platform\rtunet\eboot\rne_mdd.lib
(rndis.obj) : error LNK2019: unresolved external symbol
PDDInit referenced in function RndisInit

e:\wince420\platform\rtunet\eboot\rne_mdd.lib
(rndis.obj) : error LNK2019: unresolved external symbol
NKCreateStaticMapping referenced in function RndisInit

e:\wince420\platform\rtunet\eboot\rne_mdd.lib(util.obj) :
error LNK2019: unresolved external symbol
PCIGetBusDataByOffset referenced in function
HalGetBusDataByOffset

e:\wince420\platform\rtunet\target\armv4i\debug\eboot.exe
() : error LNK1120: 3 unresolved externals
=========

>-----Original Message-----
>Hi Andrew,
>
>Have a look at the Net2890 PDD for the RNDIS driver.
It's got all the
>functionality you need, you just need to modify it to
support your
>register set. It will allow you to create both a driver
and a KITL
>transport. Just a hint though, develop the PDD for the
driver first,
>then port it across to KITL, it's a lot easier to debug
that way...
>
>Glenn.
>
>In article <182101c3fbeb$00af9860$a501280a@phx.gbl>,
>anonymous@discussions.microsoft.com says...
>> Thanks again David. I couldn't find a USB Serial KITL
>> driver in the XSC1BD BSP so I guess I better just bite
>> the bullet and write a USB KITL driver that works with
>> RNDIS. Seems the simplest and most commonly used
>> solution.
>>
>>
>> >-----Original Message-----
>> >If you talking about the driver under
>> platform\xsc1bd\drivers\usb\function
>> >on WINCE 4.2, no, it is not kernel mode driver. It is
>> client mode driver. It
>> >can not either link with Kernal (NK) nor bootloader
>> (EBOOT) to establish
>> >KITL connection or downloading. If you have kernel
mode
>> USB Serial KITL
>> >driver, it should be able to link both Kernel (NK)
and
>> bootloader (Eboot).
>> >
>> >David Liao.
>> >
>> >"Andrew" <anonymous@discussions.microsoft.com> wrote
in
>> message
>> >news:0d5701c3fb3d$982a9450$a501280a@phx.gbl...
>> >> Thanks David.
>> >>
>> >> One more thing.
>> >>
>> >> Is the XSC1BD USB Function driver a kernel driver?
Can
>> >> you use the XSC1BD USB Function driver with Eboot?
>> Just
>> >> seems difficult as Eboot in the XSC1BD BSP seems to
be
>> >> Ethernet based.
>> >>
>> >> If I use the XSC1BD USB Function and run
wceusbsh.sys
>> on
>> >> my Host PC, I should be able to connect to the
device
>> >> with PB once the Kernel is running via a serial
>> >> connection. But how can I download/initialise the
>> Kernel
>> >> from PB if the USB interface isn't available during
>> Eboot?
>> >>
>> >> >-----Original Message-----
>> >> >The answer is Yes.
>> >> >You can do these on both USB RNDIS KITL and USB
Serial
>> >> Function KITL. The
>> >> >RNDIS KITL does give you more. It can run Vmini on
>> RNDIS
>> >> KITL (not on USB
>.
>

Relevant Pages