Hello!

I am using RTL 8139 In Wince 5.0.
In Platformbuilder they are given the RTL 8139 driver On Catalog item.
I was add that driver.
I am doing the following entry in Project.reg
;RTL8139 Driver
[HKEY_LOCAL_MACHINE\Comm\RTL8139]
"DisplayName"="Realtek RTL 8139 based Fast Ethernet Driver"
"Group"="NDIS"
"ImagePath"="rtl8139.dll"

[HKEY_LOCAL_MACHINE\Comm\RTL8139\Linkage]
"Route"=multi_sz:"RTL81391"

[HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage]
"Bind"=multi_sz:"PPP","RTL81391"


[HKEY_LOCAL_MACHINE\Comm\RTL81391\Parms]

"BusNumber"=dword:0
"BusType"=dword:5
"IoBaseAddress"=dword:e000
"Transceiver"=dword:3
"CardType"=dword:1
"SysIntr"=dword:1f

[HKEY_LOCAL_MACHINE\Comm\PCI\RTL81391\Parms\Tcpip]

"EnableDHCP"=dword:1
"DefaultGateway"=""
"UseZeroBroadcast"=dword:0
"IpAddress"="0.0.0.0"
"Subnetmask"="0.0.0.0"


But I was tried to ping other Pc It shows Me the following message
transmit failed,error code 11010.
Suppose this means my driver is not supported Then pls suggest proper
driver for RTL 8139 or give me the changes of the driver files.
Thnak you.

Re: RTL 8139 by Silver

Silver
Wed Apr 16 14:34:21 PDT 2008

Does the adapter have an IP address?
'ipconfig' will tell you.

Is the host routing setup?
'route print all'

did you ping by name or ip address?
try by ip address.

Geoff
--

Re: RTL 8139 by ashsantu

ashsantu
Sun Apr 20 23:04:05 PDT 2008

Hello
yes,Adpater have Ip address-192.168.10.81
I will ping by IP address.
Ping 192.168.10.179 -t
I was tried it shows "transmit failed,error code 11010."

Pls help me.

Re: RTL 8139 by Paul

Paul
Mon Apr 21 09:44:12 PDT 2008

You didn't answer Geoff's questions. What does 'Ipconfig /all' return for
the indicated adapter? *All* of the information. What does 'route print'
return? All of the information. People are trying to help and you're not
cooperating...

Paul T.

<ashsantu@gmail.com> wrote in message
news:7255a9e8-88e0-4549-8c52-ff3610e25473@k1g2000prb.googlegroups.com...
> Hello
> yes,Adpater have Ip address-192.168.10.81
> I will ping by IP address.
> Ping 192.168.10.179 -t
> I was tried it shows "transmit failed,error code 11010."
>
> Pls help me.



Re: RTL 8139 by ash

ash
Tue Apr 22 22:45:01 PDT 2008

Hello,
"Ipconfig" Show me following:
-------------------------------------------------------------------------------------------------
Windows IP configuration
Ethernet Adapter PCI\RTL 81391
IP Address------------------:192.168.10.81
subnet Mask----------------:255.255.255.0
Ip Address------------------:fe80:208:alff:fe45:a677%7
Default Gateway------------:192.168.10.2

Tunel adapter[]:
Interface Number -----:4
Tunel adapter[6 to 4 Pseudo -Interface]
Interface number : 3
Tunel adapter [Automatic tunneling pseudo interface]
interface number :2
Ip Address:fe80:5efc:192.168.10.81%2
------------------------------------------------------------------------------------------------
"route print" show me the following
Interface List
0x2002 00 81 al 45 a6 77 pci\RTL81391
-------------------------------------------------------------------------------------------------
Active Routes
The no of entries is:7
Destination Netmask gatewayAddress
Interface metric
0.0.0.0 0.0.0.0 192.168.10.2
192.168.10.81 20
127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
192.168.10.0 255.255.255.0 192.168.10.81
192.168.10.81 20
192.168.10.81 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.10.255 255.255.255.255 192.168.10.81
192.168.10.81 20
224.0.0 240.0.0 192.168.10.81
192.168.10.81 20
255.255.255.255 255.255.255.255 192.168.10.81 192.168.10.81
20
-------------------------------------------------------------------------------------------------
When I was given the command ti ping other Pc
"ping 192.168.10.179 -t"

it shows me
Pinging host 192.168.10.179
PING: transmit failed,error code 11010
I am using RTL 8139 Network card With Wince 5.0
In catalog item of platfiorm builder they are given the RTL 8139 driver .
I was add that driver to my OS design.
I was stuck this problem Last One week.
Pls help me this solution.
thank you.






Re: RTL 8139 by Paul

Paul
Wed Apr 23 08:52:25 PDT 2008

If you ping the device from the 192.168.10.179 side, what does *that* say?
Usually, that error is generated when there's no media on which to send the
packets (the cable is unplugged, the driver is not configured correctly in
the registry and so is not working right, etc.) Carefully scan the debug
messages printed during startup and, for that matter, during the ping
operation itself, for indications that the driver is not functional or that
it thinks that the cable is not connected.

Paul T.

"ash" <ash@discussions.microsoft.com> wrote in message
news:176E338B-834A-4020-871C-7A5BBE4EA61A@microsoft.com...
> Hello,
> "Ipconfig" Show me following:
> -------------------------------------------------------------------------------------------------
> Windows IP configuration
> Ethernet Adapter PCI\RTL 81391
> IP Address------------------:192.168.10.81
> subnet Mask----------------:255.255.255.0
> Ip Address------------------:fe80:208:alff:fe45:a677%7
> Default Gateway------------:192.168.10.2
>
> Tunel adapter[]:
> Interface Number -----:4
> Tunel adapter[6 to 4 Pseudo -Interface]
> Interface number : 3
> Tunel adapter [Automatic tunneling pseudo interface]
> interface number :2
> Ip Address:fe80:5efc:192.168.10.81%2
> ------------------------------------------------------------------------------------------------
> "route print" show me the following
> Interface List
> 0x2002 00 81 al 45 a6 77 pci\RTL81391
> -------------------------------------------------------------------------------------------------
> Active Routes
> The no of entries is:7
> Destination Netmask gatewayAddress
> Interface metric
> 0.0.0.0 0.0.0.0 192.168.10.2
> 192.168.10.81 20
> 127.0.0.0 255.0.0.0 127.0.0.1
> 127.0.0.1 1
> 192.168.10.0 255.255.255.0 192.168.10.81
> 192.168.10.81 20
> 192.168.10.81 255.255.255.255 127.0.0.1
> 127.0.0.1
> 20
> 192.168.10.255 255.255.255.255 192.168.10.81
> 192.168.10.81 20
> 224.0.0 240.0.0 192.168.10.81
> 192.168.10.81 20
> 255.255.255.255 255.255.255.255 192.168.10.81
> 192.168.10.81
> 20
> -------------------------------------------------------------------------------------------------
> When I was given the command ti ping other Pc
> "ping 192.168.10.179 -t"
>
> it shows me
> Pinging host 192.168.10.179
> PING: transmit failed,error code 11010
> I am using RTL 8139 Network card With Wince 5.0
> In catalog item of platfiorm builder they are given the RTL 8139 driver .
> I was add that driver to my OS design.
> I was stuck this problem Last One week.
> Pls help me this solution.
> thank you.
>
>
>
>
>



Re: RTL 8139 by Silver

Silver
Wed Apr 23 09:20:47 PDT 2008


Grab wireshark and sniff your network - look for an ARP from "00 81 al 45 a6
77 " looking for 192.168.10.179, you should see a reply.

Error 11010 is a ping timeout. If the ARP failed then the error would be
destination unreachable, 11003.

Kill the firewall on 179 so it will allow ICMP through perhaps.

Geoff
--


Re: RTL 8139 by ashsantu

ashsantu
Wed Apr 23 22:27:50 PDT 2008

hello
Thanks for the reply.
If i ping from "ping 192.168.10.81 " it shows request time out.
As per u r saying the driver is not configured correctly in registery,
so pls tell me how i configured RTL 8139 driver in registery.
I am using the Plaform builder -Catalog item-device driver-Networking-
LAN- Realtek8139
My RTL 8139 device id 10ec & vendor id 8139.
Pls tell me how i can see the debug message.
My nk.bin is booting from harddisk.
I was copied it permentatly.
If this driver is not working Then What is any other solution.?

Re: RTL 8139 by ashsantu

ashsantu
Thu Apr 24 06:02:11 PDT 2008

Hello
I was tried run time debug message,
Its shows me following.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Debug Serial Init

SysInit: GDTBase=80fa70e8 IDTBase=80fc8860
KData=80fd1800
Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
g_pPageDir = 80fd4000
RTC - Status Reg B - 0x02
X86Init done, OEMAddressTable = 80224fb8.
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Driver
s\BuiltIn\AFD). Driver cannot be unloaded.
DeviceFolder::LoadDevice!
Enumerate Fou
nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
cannot be unloa
ded.
PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
Lyg.p: Layout Manager successfully initialized to 1
Explorer(V2.0) taskbar thread started.
NDISPWR:: Found adapter [PCI\RTL81391]
CTLPNL: cmdline=\Windows\connpnl.cpl,0
--->>>CTLPNL: CPL='\Windows\connpnl.cpl' icon=0 tab=0
NDISPWR:: BIND notification for adapter [PCI\RTL81391]
cetsc.exe started. Cmdline : ''
CTLPNL: cmdline=\Windows\connpnl.cpl,0
--->>>CTLPNL: CPL='\Windows\connpnl.cpl' icon=0 tab=0
NDISPWR:: BIND notification for adapter [PCI\RTL81391]
-------------------------------------------------------------------------------------------------
I wa stried to ping any other Pc it shows me the Ping transmit
failed"transmit error code 11010"
I have netgear RTL8139 card.My sbc iz X86 based.
thank you
bye


Re: RTL 8139 by Paul

Paul
Thu Apr 24 09:07:59 PDT 2008

That's not the complete debug list, certainly. As suggested by Geoff, look
at the device/PC you're trying to ping and see if there are any firewall
issues. Does the Ethernet connection indicate that there is a LINK? Does
the system tray icon for the network adapter show good or does it indicate
that the network connection is broken? If you have the adapter set for
DHCP, you should be able to ping the DHCP server that is assigning your
address. Try that.

Paul T.

<ashsantu@gmail.com> wrote in message
news:25ab1e52-213b-4caf-9a0e-6db5b2f22c89@h1g2000prh.googlegroups.com...
> Hello
> I was tried run time debug message,
> Its shows me following.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Debug Serial Init
>
> SysInit: GDTBase=80fa70e8 IDTBase=80fc8860
> KData=80fd1800
> Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
> g_pPageDir = 80fd4000
> RTC - Status Reg B - 0x02
> X86Init done, OEMAddressTable = 80224fb8.
> OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
> OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
> OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
> DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
> at (Driver
> s\BuiltIn\AFD). Driver cannot be unloaded.
> DeviceFolder::LoadDevice!
> Enumerate Fou
> nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
> cannot be unloa
> ded.
> PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
> Lyg.p: Layout Manager successfully initialized to 1
> Explorer(V2.0) taskbar thread started.
> NDISPWR:: Found adapter [PCI\RTL81391]
> CTLPNL: cmdline=\Windows\connpnl.cpl,0
> --->>>CTLPNL: CPL='\Windows\connpnl.cpl' icon=0 tab=0
> NDISPWR:: BIND notification for adapter [PCI\RTL81391]
> cetsc.exe started. Cmdline : ''
> CTLPNL: cmdline=\Windows\connpnl.cpl,0
> --->>>CTLPNL: CPL='\Windows\connpnl.cpl' icon=0 tab=0
> NDISPWR:: BIND notification for adapter [PCI\RTL81391]
> -------------------------------------------------------------------------------------------------
> I wa stried to ping any other Pc it shows me the Ping transmit
> failed"transmit error code 11010"
> I have netgear RTL8139 card.My sbc iz X86 based.
> thank you
> bye
>



Re: RTL 8139 by ashsantu

ashsantu
Fri Apr 25 03:09:16 PDT 2008

Hello,
If i ping from "ping 192.168.10.81 " it shows request time out.
As per u r saying the driver is not configured correctly in
registery,
so pls tell me how i configured RTL 8139 driver in registery.
I am using the Plaform builder -Catalog item-device driver-
Networking-
LAN- Realtek8139
My RTL 8139 device id 10ec & vendor id 8139.
Pls tell me how i can see the debug message.
My nk.bin is booting from harddisk.
I was copied it permentatly.
If this driver is not working Then What is any other solution.?
I check the firewall setting. When i was try to ping wINCE TO ANY
OTHER pc.
mY wINCE pc IS BRIADCAST THE MESSAGE.oR MAY IT IS NOT SENDING ANY
PACKECT.
I WAS DONE Geoff suggestion also.Its not show me ARP packet.
Pls guid eme properly, i was stuck this problem last 2 weeks.
Tell me the platform builder RTl 8139 driver is worked as NDIS driver
or not?
if not pls Tell me the suggestion how it works ?
I want RTL 8139 driver for communication purpose.
that i can use internet & all communication facility.




Re: RTL 8139 by ashsantu

ashsantu
Fri Apr 25 06:35:05 PDT 2008

Pls check following debug message pls give me the solution
SysInit: GDTBase=8118d0e8 IDTBase=811deec0
KData=811fd800
Windows CE Kernel for i486 Built on Jun 24 2004 at
18:23:42
g_pPageDir = 81200000
InitKitlNIC: Searching for PCI Ethernet NIC
(dwIrq = 0,
dwI
oBase = 0, dwDfltType = 0) ...
InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11,
IOBase=0x1000).
RTL8139InitDMABuffer():: Start[0x811E2B40]-[0x811E2B40] -
Size[0x10000]
[0x0]
Tx[0x811E2B40] - Rx[0x811E4340] - RxLength[0x8000] -
RxLengthBit[0x1000]tRx[0x2117FF] [0x77400700] RCR
[0x181A] TCTR [0xA99ED
RTL8139:: built on [Apr 25 2008]
[14:47:12]
RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
RTL8139Init:: MAC = 00-08-A1-45-A6-77
RTL8139Init():: TxBuff[0x811E2B40] - RxBuff[0x811E4340] -
LastRx[0x811EC33F][0x10] CONFIG1
[0x8D]
RTL8139Init:: MAC = 00-18-4D-6F-24-3FTL8139HWSetMCRegs():: Set all to
0x00
RTL8139 ethdbg library: perform auto negotiate.
M
+RTL8139EnableInts().. [0xE5] MULI
RTL8139:: RTL8139HWSetMCRegs():: Set all to
0x00L8139EnableInts()..D [0x10]
VBridge:: built on [Apr 25 2008] time [14:47:14]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA11F2CE0] to [0xA11F6CE0].
Rx buffer [0xA11F6D00] to [0xA11FAD00].
VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
ERROR: OALKitlInit: KitlInit failed
RTC - Status Reg B - 0x02
X86Init done, OEMAddressTable = 80229378.
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
VBridge:: VB_INITIALIZED returns [1]
VBridge:: RESET_BUFFER received.
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Driver
s\BuiltIn\AFD). Driver cannot be unloaded.
DeviceFolder::LoadDevice!
Enumerate Fou
nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
cannot be unloa
ded.
PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
Lyg.p: Layout Manager successfully initialized to 1
Explorer(V2.0) taskbar thread started.
NDISPWR:: Found adapter [VMINI1]
NDISPWR:: Found adapter [PCI\RTL81391]

Re: RTL 8139 by Paul

Paul
Fri Apr 25 10:27:19 PDT 2008

So, you're NOT using the RTL adapter as an ordinary Ethernet adapter, but as
a KITL-over-Ethernet connection to your Platform Builder machine? It
appears that this is the case. If so, you *CAN'T* also use the adapter
driver; that won't work because you'll have both the kernel and the driver
trying to talk to the hardware. You can a) use VMini and leave the KITL
stuff or, b) change the BSP so that it's not using KITL-over-Ethernet and
use the real RTL driver. How, exactly, you do b), is BSP-specific, so I'll
have to leave that to you. If you want to do a), remove the RTL driver from
the OS and make sure that you've followed the instructions in Ethernet
Debugging Services in the help to turn on VMini.

Paul T.

<ashsantu@gmail.com> wrote in message
news:13059dc4-9fbc-49a0-ad08-175d74447de9@u36g2000prf.googlegroups.com...
> Pls check following debug message pls give me the solution
> SysInit: GDTBase=8118d0e8 IDTBase=811deec0
> KData=811fd800
> Windows CE Kernel for i486 Built on Jun 24 2004 at
> 18:23:42
> g_pPageDir = 81200000
> InitKitlNIC: Searching for PCI Ethernet NIC
> (dwIrq = 0,
> dwI
> oBase = 0, dwDfltType = 0) ...
> InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11,
> IOBase=0x1000).
> RTL8139InitDMABuffer():: Start[0x811E2B40]-[0x811E2B40] -
> Size[0x10000]
> [0x0]
> Tx[0x811E2B40] - Rx[0x811E4340] - RxLength[0x8000] -
> RxLengthBit[0x1000]tRx[0x2117FF] [0x77400700] RCR
> [0x181A] TCTR [0xA99ED
> RTL8139:: built on [Apr 25 2008]
> [14:47:12]
> RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
> RTL8139Init:: MAC = 00-08-A1-45-A6-77
> RTL8139Init():: TxBuff[0x811E2B40] - RxBuff[0x811E4340] -
> LastRx[0x811EC33F][0x10] CONFIG1
> [0x8D]
> RTL8139Init:: MAC = 00-18-4D-6F-24-3FTL8139HWSetMCRegs():: Set all to
> 0x00
> RTL8139 ethdbg library: perform auto negotiate.
> M
> +RTL8139EnableInts().. [0xE5] MULI
> RTL8139:: RTL8139HWSetMCRegs():: Set all to
> 0x00L8139EnableInts()..D [0x10]
> VBridge:: built on [Apr 25 2008] time [14:47:14]
> VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
> Tx buffer [0xA11F2CE0] to [0xA11F6CE0].
> Rx buffer [0xA11F6D00] to [0xA11FAD00].
> VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
> ERROR: OALKitlInit: KitlInit failed
> RTC - Status Reg B - 0x02
> X86Init done, OEMAddressTable = 80229378.
> OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
> OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
> OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
> VBridge:: VB_INITIALIZED returns [1]
> VBridge:: RESET_BUFFER received.
> DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
> at (Driver
> s\BuiltIn\AFD). Driver cannot be unloaded.
> DeviceFolder::LoadDevice!
> Enumerate Fou
> nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
> cannot be unloa
> ded.
> PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
> Lyg.p: Layout Manager successfully initialized to 1
> Explorer(V2.0) taskbar thread started.
> NDISPWR:: Found adapter [VMINI1]
> NDISPWR:: Found adapter [PCI\RTL81391]



Re: RTL 8139 by ashsantu

ashsantu
Tue Apr 29 05:58:15 PDT 2008

On Apr 25, 10:27 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
> So, you're NOTusingthe RTL adapter as an ordinary Ethernet adapter, but as
> a KITL-over-Ethernet connection to your Platform Builder machine? It
> appears that this is the case. If so, you *CAN'T* also use the adapter
> driver; that won't work because you'll have both the kernel and the driver
> trying to talk to the hardware. You can a) use VMini and leave the KITL
> stuff or, b) change the BSP so that it's notusingKITL-over-Ethernet and
> use the real RTL driver. How, exactly, you do b), is BSP-specific, so I'll
> have to leave that to you. If you want to do a), remove the RTL driver from
> the OS and make sure that you've followed the instructions in Ethernet
> Debugging Services in the help to turn on VMini.
>
> PaulT.
>
> <ashsa...@gmail.com> wrote in message
>
> news:13059dc4-9fbc-49a0-ad08-175d74447de9@u36g2000prf.googlegroups.com...
>
> > Pls check following debug message pls give me the solution
> > SysInit: GDTBase=8118d0e8 IDTBase=811deec0
> > KData=811fd800
> >WindowsCEKernel for i486 Built on Jun 24 2004 at
> > 18:23:42
> > g_pPageDir = 81200000
> > InitKitlNIC: Searching for PCI Ethernet NIC
> > (dwIrq = 0,
> > dwI
> > oBase = 0, dwDfltType = 0) ...
> > InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11,
> > IOBase=0x1000).
> > RTL8139InitDMABuffer():: Start[0x811E2B40]-[0x811E2B40] -
> > Size[0x10000]
> > [0x0]
> > Tx[0x811E2B40] - Rx[0x811E4340] - RxLength[0x8000] -
> > RxLengthBit[0x1000]tRx[0x2117FF] [0x77400700] RCR
> > [0x181A] TCTR [0xA99ED
> >RTL8139:: built on [Apr 25 2008]
> > [14:47:12]
> > RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
> > RTL8139Init:: MAC = 00-08-A1-45-A6-77
> > RTL8139Init():: TxBuff[0x811E2B40] - RxBuff[0x811E4340] -
> > LastRx[0x811EC33F][0x10] CONFIG1
> > [0x8D]
> > RTL8139Init:: MAC = 00-18-4D-6F-24-3FTL8139HWSetMCRegs():: Set all to
> > 0x00
> >RTL8139ethdbg library: perform auto negotiate.
> > M
> > +RTL8139EnableInts().. [0xE5] MULI
> >RTL8139:: RTL8139HWSetMCRegs():: Set all to
> > 0x00L8139EnableInts()..D [0x10]
> > VBridge:: built on [Apr 25 2008] time [14:47:14]
> > VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
> > Tx buffer [0xA11F2CE0] to [0xA11F6CE0].
> > Rx buffer [0xA11F6D00] to [0xA11FAD00].
> > VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
> > ERROR: OALKitlInit: KitlInit failed
> > RTC - Status Reg B - 0x02
> > X86Init done, OEMAddressTable = 80229378.
> > OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
> > OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
> > OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
> > VBridge:: VB_INITIALIZED returns [1]
> > VBridge:: RESET_BUFFER received.
> > DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
> > at (Driver
> > s\BuiltIn\AFD). Driver cannot be unloaded.
> > DeviceFolder::LoadDevice!
> > Enumerate Fou
> > nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
> > cannot be unloa
> > ded.
> > PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
> > Lyg.p: Layout Manager successfully initialized to 1
> > Explorer(V2.0) taskbar thread started.
> > NDISPWR:: Found adapter [VMINI1]
> > NDISPWR:: Found adapter [PCI\RTL81391]

Hello sir,

Error : RealTek Driver (rtl8139) is not acting as a simple adapter for
my wince Image

My Hardware : NETGEAR rtl8139D

My Tool : Platform Builder winCE5.0

Below is my target PC platform configuration for RealTek
Added to the platform

1. CEPC:X86 = Device Drivers - Networking-Local Area Networking (LAN)
devices - RealTekRTL8139

2.Custom Device[Display based devices] -Communication Services and
Networking - Local Area Network (LAN) -
Wired Local Area Network(802.3,802.5)

3. Custom Device[Display based devices]-Communication Services and
Networking - Networking features - NDIS &Networking
utilities(ipconfig,pimg,route)

RTL 8139 was detected in the image and i configured it to
static ip address 192.168.10.199

but when i tried to ping other device on the network
it gave me the following error:

Transmit error :11010


Following were the debug messages seen on Hyperterminal on COM port

SysInit: GDTBase=8165d0e8 IDTBase=816aeec0 KData=816cd800
Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
g_pPageDir = 816d0000
InitKitlNIC: Searching for PCI Ethernet NIC
(dwIrq = 0, dwI
oBase = 0, dwDfltType = 0) ...
InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11, IOBase=0x1000).
RTL8139InitDMABuffer():: Start[0x816B2B40]-[0x816B2B40] -
Size[0x10000]
Tx[0x816B2B40] - Rx[0x816B4340] - RxLength[0x8000] -
RxLengthBit[0x1000]
RTL8139:: built on [Apr 24 2008] [15:42:24]
RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
RTL8139Init():: TxBuff[0x816B2B40] - RxBuff[0x816B4340] -
LastRx[0x816BC33F]
RTL8139Init:: MAC = 00-18-4D-6F-24-3F
RTL8139 ethdbg library: perform auto negotiate.
RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
x86KitlCreateName: Using Device Name 'CEPC9279'
OALKitlCreateName: Using Device Name 'CEPC9279'
KITL: *** Device Name CEPC9279 ***

VBridge:: built on [Apr 24 2008] time [15:42:27]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA16C2CE0] to [0xA16C6CE0].
Rx buffer [0xA16C6D00] to [0xA16CAD00].
VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
ERROR: OALKitlInit: KitlInit failed
RTC - Status Reg B - 0x02
X86Init done, OEMAddressTable = 80229368.
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Driver
s\BuiltIn\AFD). Driver cannot be unloaded.
DeviceFolder::LoadDevice!
Enumerate Fou
nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
cannot be unloa
ded.
PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
Lyg.p: Layout Manager successfully initialized to 1
Explorer(V2.0) taskbar thread started.
NDISPWR:: Found adapter [PCI\RTL81391]
NDISPWR:: BIND notification for adapter [PCI\RTL81391]

Re: RTL 8139 by Paul

Paul
Tue Apr 29 08:42:53 PDT 2008

I remember the contents of the thread. There's no reason to repeat them.
Read my last message, below, and do the right thing for you, whatever that
is.

Paul T.

<ashsantu@gmail.com> wrote in message
news:513e8b81-7cf6-449f-9322-8e7fc99eb5f0@z24g2000prf.googlegroups.com...
> On Apr 25, 10:27 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
> no instrument no spam DOT com> wrote:
>> So, you're NOTusingthe RTL adapter as an ordinary Ethernet adapter, but
>> as
>> a KITL-over-Ethernet connection to your Platform Builder machine? It
>> appears that this is the case. If so, you *CAN'T* also use the adapter
>> driver; that won't work because you'll have both the kernel and the
>> driver
>> trying to talk to the hardware. You can a) use VMini and leave the KITL
>> stuff or, b) change the BSP so that it's notusingKITL-over-Ethernet and
>> use the real RTL driver. How, exactly, you do b), is BSP-specific, so
>> I'll
>> have to leave that to you. If you want to do a), remove the RTL driver
>> from
>> the OS and make sure that you've followed the instructions in Ethernet
>> Debugging Services in the help to turn on VMini.
>>
>> PaulT.
>>
>> <ashsa...@gmail.com> wrote in message
>>
>> news:13059dc4-9fbc-49a0-ad08-175d74447de9@u36g2000prf.googlegroups.com...
>>
>> > Pls check following debug message pls give me the solution
>> > SysInit: GDTBase=8118d0e8 IDTBase=811deec0
>> > KData=811fd800
>> >WindowsCEKernel for i486 Built on Jun 24 2004 at
>> > 18:23:42
>> > g_pPageDir = 81200000
>> > InitKitlNIC: Searching for PCI Ethernet NIC
>> > (dwIrq = 0,
>> > dwI
>> > oBase = 0, dwDfltType = 0) ...
>> > InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11,
>> > IOBase=0x1000).
>> > RTL8139InitDMABuffer():: Start[0x811E2B40]-[0x811E2B40] -
>> > Size[0x10000]
>> > [0x0]
>> > Tx[0x811E2B40] - Rx[0x811E4340] - RxLength[0x8000] -
>> > RxLengthBit[0x1000]tRx[0x2117FF] [0x77400700] RCR
>> > [0x181A] TCTR [0xA99ED
>> >RTL8139:: built on [Apr 25 2008]
>> > [14:47:12]
>> > RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
>> > RTL8139Init:: MAC = 00-08-A1-45-A6-77
>> > RTL8139Init():: TxBuff[0x811E2B40] - RxBuff[0x811E4340] -
>> > LastRx[0x811EC33F][0x10] CONFIG1
>> > [0x8D]
>> > RTL8139Init:: MAC = 00-18-4D-6F-24-3FTL8139HWSetMCRegs():: Set all to
>> > 0x00
>> >RTL8139ethdbg library: perform auto negotiate.
>> > M
>> > +RTL8139EnableInts().. [0xE5] MULI
>> >RTL8139:: RTL8139HWSetMCRegs():: Set all to
>> > 0x00L8139EnableInts()..D [0x10]
>> > VBridge:: built on [Apr 25 2008] time [14:47:14]
>> > VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
>> > Tx buffer [0xA11F2CE0] to [0xA11F6CE0].
>> > Rx buffer [0xA11F6D00] to [0xA11FAD00].
>> > VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
>> > ERROR: OALKitlInit: KitlInit failed
>> > RTC - Status Reg B - 0x02
>> > X86Init done, OEMAddressTable = 80229378.
>> > OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
>> > OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
>> > OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
>> > VBridge:: VB_INITIALIZED returns [1]
>> > VBridge:: RESET_BUFFER received.
>> > DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
>> > at (Driver
>> > s\BuiltIn\AFD). Driver cannot be unloaded.
>> > DeviceFolder::LoadDevice!
>> > Enumerate Fou
>> > nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
>> > cannot be unloa
>> > ded.
>> > PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
>> > Lyg.p: Layout Manager successfully initialized to 1
>> > Explorer(V2.0) taskbar thread started.
>> > NDISPWR:: Found adapter [VMINI1]
>> > NDISPWR:: Found adapter [PCI\RTL81391]
>
> Hello sir,
>
> Error : RealTek Driver (rtl8139) is not acting as a simple adapter for
> my wince Image
>
> My Hardware : NETGEAR rtl8139D
>
> My Tool : Platform Builder winCE5.0
>
> Below is my target PC platform configuration for RealTek
> Added to the platform
>
> 1. CEPC:X86 = Device Drivers - Networking-Local Area Networking (LAN)
> devices - RealTekRTL8139
>
> 2.Custom Device[Display based devices] -Communication Services and
> Networking - Local Area Network (LAN) -
> Wired Local Area Network(802.3,802.5)
>
> 3. Custom Device[Display based devices]-Communication Services and
> Networking - Networking features - NDIS &Networking
> utilities(ipconfig,pimg,route)
>
> RTL 8139 was detected in the image and i configured it to
> static ip address 192.168.10.199
>
> but when i tried to ping other device on the network
> it gave me the following error:
>
> Transmit error :11010
>
>
> Following were the debug messages seen on Hyperterminal on COM port
>
> SysInit: GDTBase=8165d0e8 IDTBase=816aeec0 KData=816cd800
> Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
> g_pPageDir = 816d0000
> InitKitlNIC: Searching for PCI Ethernet NIC
> (dwIrq = 0, dwI
> oBase = 0, dwDfltType = 0) ...
> InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11, IOBase=0x1000).
> RTL8139InitDMABuffer():: Start[0x816B2B40]-[0x816B2B40] -
> Size[0x10000]
> Tx[0x816B2B40] - Rx[0x816B4340] - RxLength[0x8000] -
> RxLengthBit[0x1000]
> RTL8139:: built on [Apr 24 2008] [15:42:24]
> RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
> RTL8139Init():: TxBuff[0x816B2B40] - RxBuff[0x816B4340] -
> LastRx[0x816BC33F]
> RTL8139Init:: MAC = 00-18-4D-6F-24-3F
> RTL8139 ethdbg library: perform auto negotiate.
> RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
> x86KitlCreateName: Using Device Name 'CEPC9279'
> OALKitlCreateName: Using Device Name 'CEPC9279'
> KITL: *** Device Name CEPC9279 ***
>
> VBridge:: built on [Apr 24 2008] time [15:42:27]
> VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
> Tx buffer [0xA16C2CE0] to [0xA16C6CE0].
> Rx buffer [0xA16C6D00] to [0xA16CAD00].
> VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
> ERROR: OALKitlInit: KitlInit failed
> RTC - Status Reg B - 0x02
> X86Init done, OEMAddressTable = 80229368.
> OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
> OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
> OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
> DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
> at (Driver
> s\BuiltIn\AFD). Driver cannot be unloaded.
> DeviceFolder::LoadDevice!
> Enumerate Fou
> nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
> cannot be unloa
> ded.
> PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
> Lyg.p: Layout Manager successfully initialized to 1
> Explorer(V2.0) taskbar thread started.
> NDISPWR:: Found adapter [PCI\RTL81391]
> NDISPWR:: BIND notification for adapter [PCI\RTL81391]



Re: RTL 8139 by ashsantu

ashsantu
Wed Apr 30 04:28:44 PDT 2008

On Apr 29, 8:42 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
> I remember the contents of the thread. There's no reason to repeat them.
> Read my last message, below, and do the right thing for you, whatever that
> is.
>
> PaulT.
>
> <ashsa...@gmail.com> wrote in message
>
> news:513e8b81-7cf6-449f-9322-8e7fc99eb5f0@z24g2000prf.googlegroups.com...
>
> > On Apr 25, 10:27 pm, "PaulG. Tobey [eMVP]" <p space tobey no spam AT
> > no instrument no spam DOT com> wrote:
> >> So, you're NOTusingthe RTL adapter as an ordinary Ethernet adapter, but
> >> as
> >> a KITL-over-Ethernet connection to your Platform Builder machine? It
> >> appears that this is the case. If so, you *CAN'T* also use the adapter
> >> driver; that won't work because you'll have both the kernel and the
> >> driver
> >> trying to talk to the hardware. You can a) use VMini and leave the KITL
> >> stuff or, b) change the BSP so that it's notusingKITL-over-Ethernet and
> >> use the real RTL driver. How, exactly, you do b), is BSP-specific, so
> >> I'll
> >> have to leave that to you. If you want to do a), remove the RTL driver
> >> from
> >> the OS and make sure that you've followed the instructions in Ethernet
> >> Debugging Services in the help to turn on VMini.
>
> >> PaulT.
>
> >> <ashsa...@gmail.com> wrote in message
>
> >>news:13059dc4-9fbc-49a0-ad08-175d74447de9@u36g2000prf.googlegroups.com...
>
> >> > Pls check following debug message pls give me the solution
> >> > SysInit: GDTBase=8118d0e8 IDTBase=811deec0
> >> > KData=811fd800
> >> >WindowsCEKernel for i486 Built on Jun 24 2004 at
> >> > 18:23:42
> >> > g_pPageDir = 81200000
> >> > InitKitlNIC: Searching for PCI Ethernet NIC
> >> > (dwIrq = 0,
> >> > dwI
> >> > oBase = 0, dwDfltType = 0) ...
> >> > InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11,
> >> > IOBase=0x1000).
> >> > RTL8139InitDMABuffer():: Start[0x811E2B40]-[0x811E2B40] -
> >> > Size[0x10000]
> >> > [0x0]
> >> > Tx[0x811E2B40] - Rx[0x811E4340] - RxLength[0x8000] -
> >> > RxLengthBit[0x1000]tRx[0x2117FF] [0x77400700] RCR
> >> > [0x181A] TCTR [0xA99ED
> >> >RTL8139:: built on [Apr 25 2008]
> >> > [14:47:12]
> >> > RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
> >> > RTL8139Init:: MAC = 00-08-A1-45-A6-77
> >> > RTL8139Init():: TxBuff[0x811E2B40] - RxBuff[0x811E4340] -
> >> > LastRx[0x811EC33F][0x10] CONFIG1
> >> > [0x8D]
> >> > RTL8139Init:: MAC = 00-18-4D-6F-24-3FTL8139HWSetMCRegs():: Set all to
> >> > 0x00
> >> >RTL8139ethdbg library: perform auto negotiate.
> >> > M
> >> > +RTL8139EnableInts().. [0xE5] MULI
> >> >RTL8139:: RTL8139HWSetMCRegs():: Set all to
> >> > 0x00L8139EnableInts()..D [0x10]
> >> > VBridge:: built on [Apr 25 2008] time [14:47:14]
> >> > VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
> >> > Tx buffer [0xA11F2CE0] to [0xA11F6CE0].
> >> > Rx buffer [0xA11F6D00] to [0xA11FAD00].
> >> > VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
> >> > ERROR: OALKitlInit: KitlInit failed
> >> > RTC - Status Reg B - 0x02
> >> > X86Init done, OEMAddressTable = 80229378.
> >> > OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
> >> > OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
> >> > OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
> >> > VBridge:: VB_INITIALIZED returns [1]
> >> > VBridge:: RESET_BUFFER received.
> >> > DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
> >> > at (Driver
> >> > s\BuiltIn\AFD). Driver cannot be unloaded.
> >> > DeviceFolder::LoadDevice!
> >> > Enumerate Fou
> >> > nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
> >> > cannot be unloa
> >> > ded.
> >> > PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
> >> > Lyg.p: Layout Manager successfully initialized to 1
> >> > Explorer(V2.0) taskbar thread started.
> >> > NDISPWR:: Found adapter [VMINI1]
> >> > NDISPWR:: Found adapter [PCI\RTL81391]
>
> > Hello sir,
>
> > Error : RealTek Driver (rtl8139) is not acting as a simple adapter for
> > my wince Image
>
> > My Hardware : NETGEAR rtl8139D
>
> > My Tool : Platform Builder winCE5.0
>
> > Below is my target PC platform configuration for RealTek
> > Added to the platform
>
> > 1. CEPC:X86 = Device Drivers - Networking-Local Area Networking (LAN)
> > devices - RealTekRTL8139
>
> > 2.Custom Device[Display based devices] -Communication Services and
> > Networking - Local Area Network (LAN) -
> > Wired Local Area Network(802.3,802.5)
>
> > 3. Custom Device[Display based devices]-Communication Services and
> > Networking - Networking features - NDIS &Networking
> > utilities(ipconfig,pimg,route)
>
> > RTL 8139 was detected in the image and i configured it to
> > static ip address 192.168.10.199
>
> > but when i tried to ping other device on the network
> > it gave me the following error:
>
> > Transmit error :11010
>
> > Following were the debug messages seen on Hyperterminal on COM port
>
> > SysInit: GDTBase=8165d0e8 IDTBase=816aeec0 KData=816cd800
> >WindowsCEKernel for i486 Built on Jun 24 2004 at 18:23:42
> > g_pPageDir = 816d0000
> > InitKitlNIC: Searching for PCI Ethernet NIC
> > (dwIrq = 0, dwI
> > oBase = 0, dwDfltType = 0) ...
> > InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11, IOBase=0x1000).
> > RTL8139InitDMABuffer():: Start[0x816B2B40]-[0x816B2B40] -
> > Size[0x10000]
> > Tx[0x816B2B40] - Rx[0x816B4340] - RxLength[0x8000] -
> > RxLengthBit[0x1000]
> >RTL8139:: built on [Apr 24 2008] [15:42:24]
> > RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
> > RTL8139Init():: TxBuff[0x816B2B40] - RxBuff[0x816B4340] -
> > LastRx[0x816BC33F]
> > RTL8139Init:: MAC = 00-18-4D-6F-24-3F
> >RTL8139ethdbg library: perform auto negotiate.
> >RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
> > x86KitlCreateName:UsingDevice Name 'CEPC9279'
> > OALKitlCreateName:UsingDevice Name 'CEPC9279'
> > KITL: *** Device Name CEPC9279 ***
>
> > VBridge:: built on [Apr 24 2008] time [15:42:27]
> > VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
> > Tx buffer [0xA16C2CE0] to [0xA16C6CE0].
> > Rx buffer [0xA16C6D00] to [0xA16CAD00].
> > VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
> > ERROR: OALKitlInit: KitlInit failed
> > RTC - Status Reg B - 0x02
> > X86Init done, OEMAddressTable = 80229368.
> > OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
> > OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
> > OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
> > DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
> > at (Driver
> > s\BuiltIn\AFD). Driver cannot be unloaded.
> > DeviceFolder::LoadDevice!
> > Enumerate Fou
> > nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
> > cannot be unloa
> > ded.
> > PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
> > Lyg.p: Layout Manager successfully initialized to 1
> > Explorer(V2.0) taskbar thread started.
> > NDISPWR:: Found adapter [PCI\RTL81391]
> > NDISPWR:: BIND notification for adapter [PCI\RTL81391]

Hello Sir,
We have sent this message again because we were worried about
the debug messages mentioned below (mainly
about the failure in the resource request ).Can you pls throw some
light on this

DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Driver s\BuiltIn\AFD). Driver cannot be unloaded.

DeviceFolder::LoadDevice! Enumerate Found deprecated load
instructions at (Drivers\BuiltIn\PPP). Driver
cannot be unloaded.
PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed

Thanks

Re: RTL 8139 by Paul

Paul
Wed Apr 30 09:44:37 PDT 2008

Then follow my previous message recommendations, tell us which of them you
used, turning off KITL over Ethernet and using the RTL8139 driver, or
removing the driver and use VMini, and I'll look at them. Till then, you
have a huge error in your OS configuration and I'm not going to fool around
with reading debug messages sent by an OS that I *know* is bad.

Paul T.

<ashsantu@gmail.com> wrote in message
news:b5353f20-344d-4fe0-afd5-fb9fec1eb4fd@b5g2000pri.googlegroups.com...
> On Apr 29, 8:42 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
> no instrument no spam DOT com> wrote:
>> I remember the contents of the thread. There's no reason to repeat them.
>> Read my last message, below, and do the right thing for you, whatever
>> that
>> is.
>>
>> PaulT.
>>
>> <ashsa...@gmail.com> wrote in message
>>
>> news:513e8b81-7cf6-449f-9322-8e7fc99eb5f0@z24g2000prf.googlegroups.com...
>>
>> > On Apr 25, 10:27 pm, "PaulG. Tobey [eMVP]" <p space tobey no spam AT
>> > no instrument no spam DOT com> wrote:
>> >> So, you're NOTusingthe RTL adapter as an ordinary Ethernet adapter,
>> >> but
>> >> as
>> >> a KITL-over-Ethernet connection to your Platform Builder machine? It
>> >> appears that this is the case. If so, you *CAN'T* also use the
>> >> adapter
>> >> driver; that won't work because you'll have both the kernel and the
>> >> driver
>> >> trying to talk to the hardware. You can a) use VMini and leave the
>> >> KITL
>> >> stuff or, b) change the BSP so that it's notusingKITL-over-Ethernet
>> >> and
>> >> use the real RTL driver. How, exactly, you do b), is BSP-specific, so
>> >> I'll
>> >> have to leave that to you. If you want to do a), remove the RTL
>> >> driver
>> >> from
>> >> the OS and make sure that you've followed the instructions in Ethernet
>> >> Debugging Services in the help to turn on VMini.
>>
>> >> PaulT.
>>
>> >> <ashsa...@gmail.com> wrote in message
>>
>> >>news:13059dc4-9fbc-49a0-ad08-175d74447de9@u36g2000prf.googlegroups.com...
>>
>> >> > Pls check following debug message pls give me the solution
>> >> > SysInit: GDTBase=8118d0e8 IDTBase=811deec0
>> >> > KData=811fd800
>> >> >WindowsCEKernel for i486 Built on Jun 24 2004 at
>> >> > 18:23:42
>> >> > g_pPageDir = 81200000
>> >> > InitKitlNIC: Searching for PCI Ethernet NIC
>> >> > (dwIrq = 0,
>> >> > dwI
>> >> > oBase = 0, dwDfltType = 0) ...
>> >> > InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11,
>> >> > IOBase=0x1000).
>> >> > RTL8139InitDMABuffer():: Start[0x811E2B40]-[0x811E2B40] -
>> >> > Size[0x10000]
>> >> > [0x0]
>> >> > Tx[0x811E2B40] - Rx[0x811E4340] - RxLength[0x8000] -
>> >> > RxLengthBit[0x1000]tRx[0x2117FF] [0x77400700] RCR
>> >> > [0x181A] TCTR [0xA99ED
>> >> >RTL8139:: built on [Apr 25 2008]
>> >> > [14:47:12]
>> >> > RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
>> >> > RTL8139Init:: MAC = 00-08-A1-45-A6-77
>> >> > RTL8139Init():: TxBuff[0x811E2B40] - RxBuff[0x811E4340] -
>> >> > LastRx[0x811EC33F][0x10] CONFIG1
>> >> > [0x8D]
>> >> > RTL8139Init:: MAC = 00-18-4D-6F-24-3FTL8139HWSetMCRegs():: Set all
>> >> > to
>> >> > 0x00
>> >> >RTL8139ethdbg library: perform auto negotiate.
>> >> > M
>> >> > +RTL8139EnableInts().. [0xE5] MULI
>> >> >RTL8139:: RTL8139HWSetMCRegs():: Set all to
>> >> > 0x00L8139EnableInts()..D [0x10]
>> >> > VBridge:: built on [Apr 25 2008] time [14:47:14]
>> >> > VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
>> >> > Tx buffer [0xA11F2CE0] to [0xA11F6CE0].
>> >> > Rx buffer [0xA11F6D00] to [0xA11FAD00].
>> >> > VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
>> >> > ERROR: OALKitlInit: KitlInit failed
>> >> > RTC - Status Reg B - 0x02
>> >> > X86Init done, OEMAddressTable = 80229378.
>> >> > OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
>> >> > OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
>> >> > OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
>> >> > VBridge:: VB_INITIALIZED returns [1]
>> >> > VBridge:: RESET_BUFFER received.
>> >> > DeviceFolder::LoadDevice!Enumerate Found deprecated load
>> >> > instructions
>> >> > at (Driver
>> >> > s\BuiltIn\AFD). Driver cannot be unloaded.
>> >> > DeviceFolder::LoadDevice!
>> >> > Enumerate Fou
>> >> > nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
>> >> > cannot be unloa
>> >> > ded.
>> >> > PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
>> >> > Lyg.p: Layout Manager successfully initialized to 1
>> >> > Explorer(V2.0) taskbar thread started.
>> >> > NDISPWR:: Found adapter [VMINI1]
>> >> > NDISPWR:: Found adapter [PCI\RTL81391]
>>
>> > Hello sir,
>>
>> > Error : RealTek Driver (rtl8139) is not acting as a simple adapter for
>> > my wince Image
>>
>> > My Hardware : NETGEAR rtl8139D
>>
>> > My Tool : Platform Builder winCE5.0
>>
>> > Below is my target PC platform configuration for RealTek
>> > Added to the platform
>>
>> > 1. CEPC:X86 = Device Drivers - Networking-Local Area Networking (LAN)
>> > devices - RealTekRTL8139
>>
>> > 2.Custom Device[Display based devices] -Communication Services and
>> > Networking - Local Area Network (LAN) -
>> > Wired Local Area Network(802.3,802.5)
>>
>> > 3. Custom Device[Display based devices]-Communication Services and
>> > Networking - Networking features - NDIS &Networking
>> > utilities(ipconfig,pimg,route)
>>
>> > RTL 8139 was detected in the image and i configured it to
>> > static ip address 192.168.10.199
>>
>> > but when i tried to ping other device on the network
>> > it gave me the following error:
>>
>> > Transmit error :11010
>>
>> > Following were the debug messages seen on Hyperterminal on COM port
>>
>> > SysInit: GDTBase=8165d0e8 IDTBase=816aeec0 KData=816cd800
>> >WindowsCEKernel for i486 Built on Jun 24 2004 at 18:23:42
>> > g_pPageDir = 816d0000
>> > InitKitlNIC: Searching for PCI Ethernet NIC
>> > (dwIrq = 0, dwI
>> > oBase = 0, dwDfltType = 0) ...
>> > InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11, IOBase=0x1000).
>> > RTL8139InitDMABuffer():: Start[0x816B2B40]-[0x816B2B40] -
>> > Size[0x10000]
>> > Tx[0x816B2B40] - Rx[0x816B4340] - RxLength[0x8000] -
>> > RxLengthBit[0x1000]
>> >RTL8139:: built on [Apr 24 2008] [15:42:24]
>> > RTL8139Init():: BaseIO[0x1000] : MemOffset[0x1000]
>> > RTL8139Init():: TxBuff[0x816B2B40] - RxBuff[0x816B4340] -
>> > LastRx[0x816BC33F]
>> > RTL8139Init:: MAC = 00-18-4D-6F-24-3F
>> >RTL8139ethdbg library: perform auto negotiate.
>> >RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
>> > x86KitlCreateName:UsingDevice Name 'CEPC9279'
>> > OALKitlCreateName:UsingDevice Name 'CEPC9279'
>> > KITL: *** Device Name CEPC9279 ***
>>
>> > VBridge:: built on [Apr 24 2008] time [15:42:27]
>> > VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
>> > Tx buffer [0xA16C2CE0] to [0xA16C6CE0].
>> > Rx buffer [0xA16C6D00] to [0xA16CAD00].
>> > VBridge:: NK add MAC: [0-18-4D-6F-24-3F]
>> > ERROR: OALKitlInit: KitlInit failed
>> > RTC - Status Reg B - 0x02
>> > X86Init done, OEMAddressTable = 80229368.
>> > OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
>> > OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
>> > OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
>> > DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
>> > at (Driver
>> > s\BuiltIn\AFD). Driver cannot be unloaded.
>> > DeviceFolder::LoadDevice!
>> > Enumerate Fou
>> > nd deprecated load instructions at (Drivers\BuiltIn\PPP). Driver
>> > cannot be unloa
>> > ded.
>> > PCIbus!PCIEnum: WARNING: Resource request for device 0:0:0 failed
>> > Lyg.p: Layout Manager successfully initialized to 1
>> > Explorer(V2.0) taskbar thread started.
>> > NDISPWR:: Found adapter [PCI\RTL81391]
>