|
a l(deleted)
|
asix usb ethernet dongle problem
|
|
a l(deleted)
01/21/2014 6:05 PM
post108074
|
asix usb ethernet dongle problem
Hi all,
I'm trying to connect to o (armle) target.
the target starts a script from usb on boot.
I can load the devn-asix driver , and that fires up the usb adaptor (lights on)
This is what i try :
io-pkt-v4-hc -d /fs/U0/devn-asix.so lan=2
ifconfig en2 192.168.6.2
i can ping 192.168.6.2 , but can't ping to the other end of the ethernet..
in syslog :
Jan 01 00:00:27 5 14 0 tcpip starting
Jan 01 00:00:28 3 14 0 Unable to attach to pci server: No such file or directory
Jan 01 00:00:28 3 14 0 Using pseudo random generator. See "random" option
Jan 01 00:00:28 5 14 0 initializing IPsec... done
Jan 01 00:00:28 5 14 0 IPsec: Initialized Security Association Processing.
Jan 01 00:00:30 5 14 0 en2
Jan 01 00:00:30 2 14 0 ax_initialize: unable to enqueue rcv buffer 13
Any help is welcome..
|
|
|
|
|
|
Hugh Brown
|
Re: asix usb ethernet dongle problem
|
|
Hugh Brown
01/22/2014 8:02 AM
post108082
|
Re: asix usb ethernet dongle problem
If you are starting io-pkt in a script and then running ifconfig
immediately after, that could be your problem. You should have a delay
after starting the driver and running ifconfig to allow the driver to
initialize the hardware.
On 2014/1/21, 6:05 PM, "a l" <community-noreply@qnx.com> wrote:
>Hi all,
>
>I'm trying to connect to o (armle) target.
>the target starts a script from usb on boot.
>I can load the devn-asix driver , and that fires up the usb adaptor
>(lights on)
>
>This is what i try :
>io-pkt-v4-hc -d /fs/U0/devn-asix.so lan=2
>ifconfig en2 192.168.6.2
>
>i can ping 192.168.6.2 , but can't ping to the other end of the ethernet..
>
>in syslog :
>Jan 01 00:00:27 5 14 0 tcpip starting
>Jan 01 00:00:28 3 14 0 Unable to attach to pci server: No such
>file or directory
>Jan 01 00:00:28 3 14 0 Using pseudo random generator. See
>"random" option
>Jan 01 00:00:28 5 14 0 initializing IPsec... done
>Jan 01 00:00:28 5 14 0 IPsec: Initialized Security Association
>Processing.
>Jan 01 00:00:30 5 14 0 en2
>Jan 01 00:00:30 2 14 0 ax_initialize: unable to enqueue rcv
>buffer 13
>
>Any help is welcome..
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post108074
>To cancel your subscription to this discussion, please e-mail
>general-networking-unsubscribe@community.qnx.com
|
|
|
|
|
|
a l(deleted)
|
Re: asix usb ethernet dongle problem
|
|
a l(deleted)
01/22/2014 9:01 AM
post108083
|
Re: asix usb ethernet dongle problem
Thanks...
I did put a sleep between it...
After running ifconfig it also lists the interface with the configured ip address.
Also disabling packet filtering did not help.
After network setup i can ping to the configured target ip address..but nothing to host..
> If you are starting io-pkt in a script and then running ifconfig
> immediately after, that could be your problem. You should have a delay
> after starting the driver and running ifconfig to allow the driver to
> initialize the hardware.
|
|
|
|
|
|
Hugh Brown
|
Re: asix usb ethernet dongle problem
|
|
Hugh Brown
01/22/2014 9:04 AM
post108084
|
Re: asix usb ethernet dongle problem
Please can you post the output from ³usb -v² so that I can see which
version of the Asix chip you have.
On 2014/1/22, 9:01 AM, "a l" <community-noreply@qnx.com> wrote:
>Thanks...
>
>I did put a sleep between it...
>
>After running ifconfig it also lists the interface with the configured ip
>address.
>Also disabling packet filtering did not help.
>
>After network setup i can ping to the configured target ip address..but
>nothing to host..
>
>
>
>
>> If you are starting io-pkt in a script and then running ifconfig
>> immediately after, that could be your problem. You should have a delay
>> after starting the driver and running ifconfig to allow the driver to
>> initialize the hardware.
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post108083
>To cancel your subscription to this discussion, please e-mail
>general-networking-unsubscribe@community.qnx.com
|
|
|
|
|
|
a l(deleted)
|
Re: asix usb ethernet dongle problem
|
|
a l(deleted)
01/22/2014 9:37 AM
post108087
|
Re: asix usb ethernet dongle problem
USB 0 (dm816x) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk(SG), Isoch(Stream), High speed
Device Address : 1
Upstream Host Controller : 0
Upstream Device Address : 0
Upstream Port : 0
Upstream Port Speed : High
Vendor : 0x04b8
Product : 0x090a
Device Release : r0.90
Class : 0x09 (Hub)
Subclass : 0x00
Protocol : 0x01
Max PacketSize0 : 64
Hub Number Ports : 2
Hub Characteristics : 0x0020 (Ganged power, Global over-current)
Hub Power On->Good : 0 ms
Hub Power Requirements : 100 mA
Configurations : 1
Configuration : 1
Attributes : 0xe0 (Self-powered, Remote-wakeup)
Max Power : 100 mA
Device Address : 2
Upstream Host Controller : 0
Upstream Device Address : 1
Upstream Port : 2
Upstream Port Speed : High
Vendor : 0x2101 (Action Star)
Product : 0x8500 (USB2.0 Hub)
Device Release : r1.06
Class : 0x09 (Hub)
Subclass : 0x00
Protocol : 0x02
Max PacketSize0 : 64
Hub Number Ports : 5
Hub Characteristics : 0x00e4 (Ganged power, Compound, Global over-current)
Hub Power On->Good : 100 ms
Hub Power Requirements : 100 mA
Configurations : 1
Configuration : 1
Attributes : 0xe0 (Self-powered, Remote-wakeup)
Max Power : 100 mA
Device Address : 3
Upstream Host Controller : 0
Upstream Device Address : 2
Upstream Port : 1
Upstream Port Speed : High
Vendor : 0x2101 (Action Star)
Product : 0x8501 (USB HID)
Device Release : r6.05
Class : 0x00 (Independent per interface)
Max PacketSize0 : 64
Configurations : 1
Configuration : 1
Attributes : 0xa0 (Bus-powered, Remote-wakeup)
Max Power : 20 mA
Device Address : 4
Upstream Host Controller : 0
Upstream Device Address : 2
Upstream Port : 2
Upstream Port Speed : High
Vendor : 0x1307 (USBest Technology)
Product : 0x0163 (USB Mass Storage Device)
Device Release : r1.00
Class : 0x00 (Independent per interface)
Max PacketSize0 : 64
Configurations : 1
Configuration : 1
Attributes : 0x80 (Bus-powered)
Max Power : 80 mA
Device Address : 5
Upstream Host Controller : 0
Upstream Device Address : 2
Upstream Port : 3
Upstream Port Speed : High
Vendor : 0x2001 (D-Link Corporation)
Product : 0x3c05 (DUB-E100)
Device Release : r0.01
Class : 0xff (Vendor-specific)
Subclass : 0xff
Protocol : 0x00
Max PacketSize0 : 64
Configurations : 1
Configuration : 1 (0)
Attributes : 0x80 (Bus-powered)
Max Power : 250 mA
USB 1 (dm816x) v1.10, v1.01 DDK, v1.01 HCD
Control, Interrupt, Bulk, Isoch(Stream), High speed
|
|
|
|
|
|
Hugh Brown
|
Re: asix usb ethernet dongle problem
|
|
Hugh Brown
01/22/2014 9:44 AM
post108088
|
Re: asix usb ethernet dongle problem
We have ported the Asix driver to a native io-pkt driver, so will you
please run the attached driver and see if it works for you.
On 2014/1/22, 9:37 AM, "a l" <community-noreply@qnx.com> wrote:
>USB 0 (dm816x) v1.10, v1.01 DDK, v1.01 HCD
> Control, Interrupt, Bulk(SG), Isoch(Stream), High speed
>
>Device Address : 1
>Upstream Host Controller : 0
>Upstream Device Address : 0
>Upstream Port : 0
>Upstream Port Speed : High
>Vendor : 0x04b8
>Product : 0x090a
>Device Release : r0.90
>Class : 0x09 (Hub)
>Subclass : 0x00
>Protocol : 0x01
>Max PacketSize0 : 64
>Hub Number Ports : 2
>Hub Characteristics : 0x0020 (Ganged power, Global over-current)
>Hub Power On->Good : 0 ms
>Hub Power Requirements : 100 mA
>Configurations : 1
> Configuration : 1
> Attributes : 0xe0 (Self-powered, Remote-wakeup)
> Max Power : 100 mA
>
>Device Address : 2
>Upstream Host Controller : 0
>Upstream Device Address : 1
>Upstream Port : 2
>Upstream Port Speed : High
>Vendor : 0x2101 (Action Star)
>Product : 0x8500 (USB2.0 Hub)
>Device Release : r1.06
>Class : 0x09 (Hub)
>Subclass : 0x00
>Protocol : 0x02
>Max PacketSize0 : 64
>Hub Number Ports : 5
>Hub Characteristics : 0x00e4 (Ganged power, Compound, Global
>over-current)
>Hub Power On->Good : 100 ms
>Hub Power Requirements : 100 mA
>Configurations : 1
> Configuration : 1
> Attributes : 0xe0 (Self-powered, Remote-wakeup)
> Max Power : 100 mA
>
>Device Address : 3
>Upstream Host Controller : 0
>Upstream Device Address : 2
>Upstream Port : 1
>Upstream Port Speed : High
>Vendor : 0x2101 (Action Star)
>Product : 0x8501 (USB HID)
>Device Release : r6.05
>Class : 0x00 (Independent per interface)
>Max PacketSize0 : 64
>Configurations : 1
> Configuration : 1
> Attributes : 0xa0 (Bus-powered, Remote-wakeup)
> Max Power : 20 mA
>
>Device Address : 4
>Upstream Host Controller : 0
>Upstream Device Address : 2
>Upstream Port : 2
>Upstream Port Speed : High
>Vendor : 0x1307 (USBest Technology)
>Product : 0x0163 (USB Mass Storage Device)
>Device Release : r1.00
>Class : 0x00 (Independent per interface)
>Max PacketSize0 : 64
>Configurations : 1
> Configuration : 1
> Attributes : 0x80 (Bus-powered)
> Max Power : 80 mA
>
>Device Address : 5
>Upstream Host Controller : 0
>Upstream Device Address : 2
>Upstream Port : 3
>Upstream Port Speed : High
>Vendor : 0x2001 (D-Link Corporation)
>Product : 0x3c05 (DUB-E100)
>Device Release : r0.01
>Class : 0xff (Vendor-specific)
>Subclass : 0xff
>Protocol : 0x00
>Max PacketSize0 : 64
>Configurations : 1
> Configuration : 1 (0)
> Attributes : 0x80 (Bus-powered)
> Max Power : 250...
View Full Message
|
|
|
|
|
|
a l(deleted)
|
Re: asix usb ethernet dongle problem
|
|
a l(deleted)
01/22/2014 10:26 AM
post108090
|
Re: asix usb ethernet dongle problem
Thanks for your help , really appreciated !!
With the new driver.. (mount -Tio-pkt /fs/U0/devnp-asix.so)
- The dongle start..led turn on (same as old driver)
- No /dev/io-net is created
syslog:
Jan 01 00:00:22 5 10 0 ax_detect: attached [bus 0, dev 5]
Jan 01 00:00:22 5 14 0 ax0
Jan 01 00:00:25 5 10 0 ax_detect: attached AX interfaces 0
Jan 01 00:00:25 5 10 0 ax_detect: found 1 device
Jan 01 00:00:56 2 10 0 error 2
Jan 01 00:00:56 2 10 0 ax_initialize: unable to enqueue rcv buffer 13
|
|
|
|
|
|
Hugh Brown
|
Re: asix usb ethernet dongle problem
|
|
Hugh Brown
01/22/2014 10:36 AM
post108091
|
Re: asix usb ethernet dongle problem
Yes, io-pkt drivers don¹t create a /dev/io-net.
Has this dongle worked before? The fact that both drivers indicate the
same problem, seems to indicate a hardware problem.
On 2014/1/22, 10:26 AM, "a l" <community-noreply@qnx.com> wrote:
>Thanks for your help , really appreciated !!
>
>With the new driver.. (mount -Tio-pkt /fs/U0/devnp-asix.so)
>- The dongle start..led turn on (same as old driver)
>- No /dev/io-net is created
>
>syslog:
>Jan 01 00:00:22 5 10 0 ax_detect: attached [bus 0, dev 5]
>Jan 01 00:00:22 5 14 0 ax0
>Jan 01 00:00:25 5 10 0 ax_detect: attached AX interfaces 0
>Jan 01 00:00:25 5 10 0 ax_detect: found 1 device
>Jan 01 00:00:56 2 10 0 error 2
>Jan 01 00:00:56 2 10 0 ax_initialize: unable to enqueue rcv
>buffer 13
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post108090
>To cancel your subscription to this discussion, please e-mail
>general-networking-unsubscribe@community.qnx.com
|
|
|
|
|
|
a l(deleted)
|
Re: asix usb ethernet dongle problem
|
|
a l(deleted)
01/22/2014 12:32 PM
post108094
|
Re: asix usb ethernet dongle problem
The dongle currently works on the vm-ware x86 image..and on a other target (also arm-le)
I tried driver from that target , same result.
Difference is that the other target is prepared for this dongle (driver loaded via enum..ect).
Can there be something on the target that causes this error..?
it's giving me a lot of trouble..
Also can't load devc-serusb (can't create /dev/serusb error)..so no comm at the moment..other that the boot script from
usb.
Thanks
|
|
|
|
|
|
Hugh Brown
|
Re: asix usb ethernet dongle problem
|
|
Hugh Brown
01/22/2014 12:37 PM
post108095
|
Re: asix usb ethernet dongle problem
It sounds to me as though you have a USB problem with that target, rather
than a network driver problem. We have a lot of those DLink dongles here
that we use all the time, so I know that the driver works.
I cannot help you with USB problems, so maybe you should post this
question on another conference.
On 2014/1/22, 12:32 PM, "a l" <community-noreply@qnx.com> wrote:
>The dongle currently works on the vm-ware x86 image..and on a other
>target (also arm-le)
>
>I tried driver from that target , same result.
>Difference is that the other target is prepared for this dongle (driver
>loaded via enum..ect).
>
>Can there be something on the target that causes this error..?
>it's giving me a lot of trouble..
>Also can't load devc-serusb (can't create /dev/serusb error)..so no comm
>at the moment..other that the boot script from usb.
>
>Thanks
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post108094
>To cancel your subscription to this discussion, please e-mail
>general-networking-unsubscribe@community.qnx.com
|
|
|
|
|
|
a l(deleted)
|
Re: asix usb ethernet dongle problem
|
|
a l(deleted)
01/23/2014 4:30 AM
post108115
|
Re: asix usb ethernet dongle problem
Turned out the target had some custom enum system..
That system prevented my manually loaded driver from working..
I changed the vid&pid in the system img (hexedit) so it loads my dongle driver with the custom enum system..and it works
like a charm.
Thanks for your help !!
|
|
|
|
|
|
