Re: ADM851X USB-LAN-Adapter driver

On Dec 4, 7:10 am, Mike.Brunb...@xxxxxxxxx wrote:
On Nov 29, 8:26 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:



It looks to me like your adapter might not be working correctly. It would
be worthwhile to try another one of the same type, if you haven't already.

If the hardware is eliminated and you are running on the same board that the
Windows CE 4.2 driver worked with, then there's something wrong with your
driver. I don't have any insight as to what, specifically, would be wrong.
Are those last couple of messages generated by you or the USB host
controller driver? I'd start with breakpoints where the transfers are
supposed to occur and see which one(s) fail and why. Your USB sniffer will
probably help here, too.

Paul T.

"Percy" <prabl...@xxxxxxxxx> wrote in message

news:7cee7933-2bd3-4a05-8670-ca8914161e38@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi Paul,

Thanks for reply.
These are the debug messages which we get on Hyper terminal after
connecting adapter.

LM_ResetAdapter: EP1Ctrl=0x4
LM_ResetAdapter: Reserved(0x1D)=0x0
LM_ResetAdapter: USBStatus=0x0
LM_ResetAdapter: USBStatus=0x0
LM_ResetAdapter: TxStatus-2=0x40
LM_ResetAdapter: RxStatus=0x0
LM_ResetAdapter: RxLostPktHigh=0x0
LM_ResetAdapter: RxLostPktLow=0x0
LM_ResetAdapter: IntPHYCtrl=0x2
LM_ResetAdapter: GPIO[5:4]=0x0
LM_ResetAdapter: GPIO[1:0]=0x27
LM_ResetAdapter: GPIO[3:2]=0x27
LM_ResetAdapter: MII test_mode=0x2
NDISPWR:: BIND notification for adapter [LANNDS1]
UM_CheckLinkStatus: LinkStatus=5
LRCCE: rx incomplete !, RxFree=18, RxPkt=0
LQRP: LM_ReceiveCompleteCE fail !
MIRP: LQRP Failed !, RxFree=18, RxPkt=0
Issue Tx Bulk Transfer fail !
Send Fail !, TxDescLeft=39

It will stop here at this stage, Please let me know what I need to
change, I have increased USB host controller memory.

Thanks,
Percy

On Nov 28, 9:43 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
Turn on all debugging messages, particularly for USB, and see what the
last
thing that shows up is. Set a breakpoint there in the kernel debugger
and
trace...

Paul T.

"Percy" <prabl...@xxxxxxxxx> wrote in message

news:4da2689b-1da1-4e91-8425-3e81e36ed2cd@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi ALL,

I'm working on ADM851XUSB-LAN-Adapterdriver, PXA255, WinCE 5.0.
I'm porting this driver from 4.2 to 5.0 with same Hardware.
Device will detect Adapter, but it will hang some where, and we can't
browse.
where may be the fault, please help me with suggestions.

Thanks
Percy- Hide quoted text -

- Show quoted text -

I totally agree with Paul.
I have faced this problem earlier and in your case as per the messages
it clearly seams
to be some problem with the hardware.
Try with another hardware sample.

Mike

Hi Mike,

USB-LAN-Adapter is working fine on PC, Win XP. Can you help me out
with how to take this issue forward.

Thanks,
Percy


.

Relevant Pages

  • Re: MODULES vs FILES in bib file
    ... no instrument no spam DOT com> wrote: ... why not calculate the hash on the image as a whole? ... performance of the driver will have any impact. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: ADM851X USB-LAN-Adapter driver
    ... timing differences in when power is applied, etc. on Windows CE vs. desktop ... source (and ask for a CE5-compatible driver, for goodness sake!), turn on ... no instrument no spam DOT com> wrote: ...
    (microsoft.public.windowsce.platbuilder)
  • Re: MODULES vs FILES in bib file
    ... why not calculate the hash on the image as a whole? ... no instrument no spam DOT com> wrote: ... performance of the driver will have any impact. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: ADM851X USB-LAN-Adapter driver
    ... no instrument no spam DOT com> wrote: ... Windows CE 4.2 driver worked with, then there's something wrong with your ... LQRP: LM_ReceiveCompleteCE fail! ... I'm porting this driver from 4.2 to 5.0 with same Hardware. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: smart card reading
    ... spam AT no instrument no spam DOT com> wrote: ... You'd then consult the documentation for the card to figure out ... >how to communicate with the driver. ...
    (microsoft.public.dotnet.framework.compactframework)