|
Steve Iribarne(deleted)
10/14/2013 2:52 PM
post105902
|
Hello.
I am currently running QNX SP6.5 sp1.
I have my wifi loading fine and if I mannually configure the wifi interface it works. (ie. run wpa_cli ssid "setmyid"
psk="mypasswd" key_mgmt WPA-PSK) I can get the network to come up and everythings works peachy.
I am having issues with restarting it once I've saved the file. Our persistent data lives on a NAND flash so when I
create the build config I create a link to the wpa_supplicant that lives on /emmc/wpa_supplicant.conf.
From the prompt I can see the file, cat the file etc.. so I know it's a valid link.
However when I run my script to startup the wifi, it never authenticate. It keeps trying and telling me that it has a
timeout.
tiw_sta0: Trying to associate with 20:aa:4b:a9:43:74 (SSID='NeatoEngineeringTestWIFI' freq=2462 MHz)
HOSTAPTIW wilink_associate: enter, mode = 0
tiw_sta0: Associated with 20:aa:4b:a9:43:74
tiw_sta0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
tiw_sta0: CTRL-EVENT-DISCONNECTED bssid=20:aa:4b:a9:43:74 reason=15
tiw_sta0: Authentication with 00:00:00:00:00:00 timed out.
tiw_sta0: skip - blacklisted (count=1 limit=0)
I know the pre-shared key is correct, because if I do it manually it works.
I have two io-pkt-v4-hc's running. The first one lives in the default location /dev/
The second one I load like:
io-pkt-v4-hc -ptcpip prefix=/alt -dti127x-am335x sdio=1,dmatx=2,dmarx=3,irq=794,irq_gpio=26,gpio=38,alt_soc
And then next I load the supplicant like:
SOCK=/alt /usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0 -c/etc/wpa_supplicant.conf
it reads the config file and gives the above error.
Any ideas?
Thanks.
-stv
|
|
|
|
|
|
Hugh Brown
10/15/2013 10:39 AM
post105915
|
Do you have any delay between starting the driver and running the
wpa_supplicant? The driver takes a while to come up as it has to download
the firmware to the chip, so you have to have some delay in between
starting the driver and the wpa_supplicant.
On 2013-10-14 2:52 PM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>Hello.
>
>I am currently running QNX SP6.5 sp1.
>
>I have my wifi loading fine and if I mannually configure the wifi
>interface it works. (ie. run wpa_cli ssid "setmyid" psk="mypasswd"
>key_mgmt WPA-PSK) I can get the network to come up and everythings works
>peachy.
>
>I am having issues with restarting it once I've saved the file. Our
>persistent data lives on a NAND flash so when I create the build config I
>create a link to the wpa_supplicant that lives on
>/emmc/wpa_supplicant.conf.
>
>From the prompt I can see the file, cat the file etc.. so I know it's a
>valid link.
>
>However when I run my script to startup the wifi, it never authenticate.
>It keeps trying and telling me that it has a timeout.
>
>tiw_sta0: Trying to associate with 20:aa:4b:a9:43:74
>(SSID='NeatoEngineeringTestWIFI' freq=2462 MHz)
>HOSTAPTIW wilink_associate: enter, mode = 0
>tiw_sta0: Associated with 20:aa:4b:a9:43:74
>tiw_sta0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
>tiw_sta0: CTRL-EVENT-DISCONNECTED bssid=20:aa:4b:a9:43:74 reason=15
>tiw_sta0: Authentication with 00:00:00:00:00:00 timed out.
>tiw_sta0: skip - blacklisted (count=1 limit=0)
>
>I know the pre-shared key is correct, because if I do it manually it
>works.
>
>I have two io-pkt-v4-hc's running. The first one lives in the default
>location /dev/
>The second one I load like:
>
>io-pkt-v4-hc -ptcpip prefix=/alt -dti127x-am335x
>sdio=1,dmatx=2,dmarx=3,irq=794,irq_gpio=26,gpio=38,alt_soc
>
>And then next I load the supplicant like:
>SOCK=/alt /usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0
>-c/etc/wpa_supplicant.conf
>
>it reads the config file and gives the above error.
>
>Any ideas?
>
>Thanks.
>-stv
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post105902
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
Steve Iribarne(deleted)
10/15/2013 11:14 AM
post105917
|
> Do you have any delay between starting the driver and running the
> wpa_supplicant? The driver takes a while to come up as it has to download
> the firmware to the chip, so you have to have some delay in between
> starting the driver and the wpa_supplicant.
>
I do have a 4 second delay. I will try to add a longer one.
I just re-read my post. Sometimes I think I don't write english.
So I did more investigation yesterday. Because I have a case in which it works (run wpa_cli and then set everything by
hand) and a case in which it doesn't work(when I've saved what I've done by hand to /etc/supplicant.conf).
Here is my supplicant.conf file.
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
network={
ssid="TestWIFI"
psk="stvtest123"
key_mgmt=WPA-PSK
}
I load wpa_supplicant like:
SOCK=/alt /usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0 -c/etc/wpa_supplicant.conf -dd -K > /tmp/supplicant.out 2>&1 &
the SOCK=/alt is due to the fact that I load io-pkt-v4-hc twice and I need both drivers loaded. So the wifi sockets live on /alt/dev/socket.
In the case where it works, I see the following:
tiw_sta0: Setting authentication timeout: 10 sec 0 usec
tiw_sta0: IEEE 802.1X RX: version=2 type=3 length=117
tiw_sta0: EAPOL-Key type=2
tiw_sta0: key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
tiw_sta0: key_length=16 key_data_length=22
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 06
key_nonce - hexdump(len=32): 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc c0 ac 22 9c cb e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=121): 02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 06 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc c0 ac 22 9c cb e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 53 6d 17 35 4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
HOSTAPTIW wilink_get_ssid: enter
HOSTAPTIW wilink_get_bssid: enter
tiw_sta0: State: ASSOCIATED ->
4WAY_HANDSHAKE
tiw_sta0: WPA: RX message 1 of 4-Way Handshake from 20:aa:4b:a9:43:74 (ver=2)
RSN: msg 1/4 key data - hexdump(len=22): dd 14 00 0f ac 04 53 6d 17 35 4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
WPA: PMKID in EAPOL-Key - hexdump(len=22): dd 14 00 0f ac 04 53 6d 17 35 4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
RSN: PMKID from Authenticator - hexdump(len=16): 53 6d 17 35 4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
tiw_sta0: RSN: no matching PMKID found
Get randomness: len=32 entropy=189
WPA: Renewed SNonce - hexdump(len=32): 17 39 81 1c cc 0d 34 9b dd 88 4a e7 b7 c4 85 59 69 81 06 6f bf c3 ec 66 85 6c 5c
25 bf eb f1 65
WPA: PTK derivation - A1=08:00:28:32:e4:59 A2=20:aa:4b:a9:43:74
WPA: Nonce1 - hexdump(len=32): 17 39 81 1c cc 0d 34 9b dd 88 4a e7 b7 c4 85 59 69 81 06 6f bf c3 ec 66 85 6c 5c 25 bf eb
f1 65
WPA: Nonce2 - hexdump(len=32): 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc c0 ac 22 9c cb e6 fb 38 70 1e bc 77 e9 c6 7f 27
a4 58
WPA: PMK - hexdump(len=32): bf 56 a6 d7 5d 22 a7 94 33 b8 30 5a 3c 44 14 e1 e5 b8 34 dd b7 93 a0 fe 12 c0 18 77 23 3b 03
c2
WPA: PTK - hexdump(len=48): 74 8a 07 5a 7b 4c fb 36 aa 4b ab 2a 0b ff d5 d6 f2 a8 de b2 00 4d d3 75 aa b3 c3 c1 a0 16 05
f8 a2 87 5e 9b ad c3 1e 18 31 21 5a 8d 93 d3 d5 d0
WPA: WPA IE for msg 2/4 - hexdump(len=22): 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
WPA: Replay Counter - hexdump(len=8): 00 00 00 00 00 00 00 06
tiw_sta0: WPA: Sending EAPOL-Key 2/4
WPA: KCK - hexdump(len=16): 74 8a 07 5a 7b 4c fb 36 aa 4b ab 2a 0b ff d5 d6
WPA: Derived Key MIC - hexdump(len=16): db 26 32 74 9e...
View Full Message
|
|
|
|
|
|
Hugh Brown
10/15/2013 12:16 PM
post105921
|
Try adding the following to your config file:
eapol_version=1
On 2013-10-15 11:14 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>> Do you have any delay between starting the driver and running the
>> wpa_supplicant? The driver takes a while to come up as it has to
>>download
>> the firmware to the chip, so you have to have some delay in between
>> starting the driver and the wpa_supplicant.
>>
>
>I do have a 4 second delay. I will try to add a longer one.
>
>I just re-read my post. Sometimes I think I don't write english.
>
>So I did more investigation yesterday. Because I have a case in which it
>works (run wpa_cli and then set everything by hand) and a case in which
>it doesn't work(when I've saved what I've done by hand to
>/etc/supplicant.conf).
>
>Here is my supplicant.conf file.
>
>ctrl_interface=/var/run/wpa_supplicant
>ctrl_interface_group=0
>update_config=1
>
>network={
> ssid="TestWIFI"
> psk="stvtest123"
> key_mgmt=WPA-PSK
>}
>
>
>I load wpa_supplicant like:
>
>SOCK=/alt /usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0
>-c/etc/wpa_supplicant.conf -dd -K > /tmp/supplicant.out 2>&1 &
>
>the SOCK=/alt is due to the fact that I load io-pkt-v4-hc twice and I
>need both drivers loaded. So the wifi sockets live on /alt/dev/socket.
>
>In the case where it works, I see the following:
>
>tiw_sta0: Setting authentication timeout: 10 sec 0 usec
>tiw_sta0: IEEE 802.1X RX: version=2 type=3 length=117
>tiw_sta0: EAPOL-Key type=2
>tiw_sta0: key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
>tiw_sta0: key_length=16 key_data_length=22
> replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 06
> key_nonce - hexdump(len=32): 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc
>c0 ac 22 9c cb e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58
> key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>00
> key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
> key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
> key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>00
>WPA: RX EAPOL-Key - hexdump(len=121): 02 03 00 75 02 00 8a 00 10 00 00 00
>00 00 00 00 06 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc c0 ac 22 9c cb
>e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58 00 00 00 00 00 00 00 00 00 00 00
>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 53 6d 17
>35 4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
>HOSTAPTIW wilink_get_ssid: enter
>HOSTAPTIW wilink_get_bssid: enter
>tiw_sta0: State: ASSOCIATED -> 4WAY_HANDSHAKE
>tiw_sta0: WPA: RX message 1 of 4-Way Handshake from 20:aa:4b:a9:43:74
>(ver=2)
>RSN: msg 1/4 key data - hexdump(len=22): dd 14 00 0f ac 04 53 6d 17 35 4a
>79 ee 48 97 c0 a6 3b 2d 7a c6 99
>WPA: PMKID in EAPOL-Key - hexdump(len=22): dd 14 00 0f ac 04 53 6d 17 35
>4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
>RSN: PMKID from Authenticator - hexdump(len=16): 53 6d 17 35 4a 79 ee 48
>97 c0 a6 3b 2d 7a c6 99
>tiw_sta0: RSN: no matching PMKID found
>Get randomness: len=32 entropy=189
>WPA: Renewed SNonce - hexdump(len=32): 17 39 81 1c cc 0d 34 9b dd 88 4a
>e7 b7 c4 85 59 69 81 06 6f bf c3 ec 66 85 6c 5c 25 bf eb f1 65
>WPA: PTK derivation - A1=08:00:28:32:e4:59 A2=20:aa:4b:a9:43:74
>WPA: Nonce1 - hexdump(len=32): 17 39 81 1c cc 0d 34 9b dd 88 4a e7 b7 c4
>85 59 69 81 06 6f bf c3 ec 66 85 6c 5c 25 bf eb f1 65
>WPA: Nonce2 - hexdump(len=32): 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc
>c0 ac 22 9c cb e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58
>WPA: PMK - hexdump(len=32): bf 56 a6 d7 5d 22 a7 94 33 b8 30 5a 3c 44 14
>e1 e5 b8 34 dd b7 93 a0 fe 12 c0 18 77 23 3b 03...
View Full Message
|
|
|
|
|
|
Steve Iribarne(deleted)
10/15/2013 12:48 PM
post105925
|
Same thing. I think eapol_version=1 is on by default.
> Try adding the following to your config file:
>
> eapol_version=1
>
>
>
>
> On 2013-10-15 11:14 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>
> >> Do you have any delay between starting the driver and running the
> >> wpa_supplicant? The driver takes a while to come up as it has to
> >>download
> >> the firmware to the chip, so you have to have some delay in between
> >> starting the driver and the wpa_supplicant.
> >>
> >
> >I do have a 4 second delay. I will try to add a longer one.
> >
> >I just re-read my post. Sometimes I think I don't write english.
> >
> >So I did more investigation yesterday. Because I have a case in which it
> >works (run wpa_cli and then set everything by hand) and a case in which
> >it doesn't work(when I've saved what I've done by hand to
> >/etc/supplicant.conf).
> >
> >Here is my supplicant.conf file.
> >
> >ctrl_interface=/var/run/wpa_supplicant
> >ctrl_interface_group=0
> >update_config=1
> >
> >network={
> > ssid="TestWIFI"
> > psk="stvtest123"
> > key_mgmt=WPA-PSK
> >}
> >
> >
> >I load wpa_supplicant like:
> >
> >SOCK=/alt /usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0
> >-c/etc/wpa_supplicant.conf -dd -K > /tmp/supplicant.out 2>&1 &
> >
> >the SOCK=/alt is due to the fact that I load io-pkt-v4-hc twice and I
> >need both drivers loaded. So the wifi sockets live on /alt/dev/socket.
> >
> >In the case where it works, I see the following:
> >
> >tiw_sta0: Setting authentication timeout: 10 sec 0 usec
> >tiw_sta0: IEEE 802.1X RX: version=2 type=3 length=117
> >tiw_sta0: EAPOL-Key type=2
> >tiw_sta0: key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
> >tiw_sta0: key_length=16 key_data_length=22
> > replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 06
> > key_nonce - hexdump(len=32): 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc
> >c0 ac 22 9c cb e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58
> > key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >00
> > key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
> > key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
> > key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >00
> >WPA: RX EAPOL-Key - hexdump(len=121): 02 03 00 75 02 00 8a 00 10 00 00 00
> >00 00 00 00 06 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc c0 ac 22 9c cb
> >e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58 00 00 00 00 00 00 00 00 00 00 00
> >00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 53 6d 17
> >35 4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
> >HOSTAPTIW wilink_get_ssid: enter
> >HOSTAPTIW wilink_get_bssid: enter
> >tiw_sta0: State: ASSOCIATED -> 4WAY_HANDSHAKE
> >tiw_sta0: WPA: RX message 1 of 4-Way Handshake from 20:aa:4b:a9:43:74
> >(ver=2)
> >RSN: msg 1/4 key data - hexdump(len=22): dd 14 00 0f ac 04 53 6d 17 35 4a
> >79 ee 48 97 c0 a6 3b 2d 7a c6 99
> >WPA: PMKID in EAPOL-Key - hexdump(len=22): dd 14 00 0f ac 04 53 6d 17 35
> >4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
> >RSN: PMKID from Authenticator - hexdump(len=16): 53 6d 17 35 4a 79 ee 48
> >97 c0 a6 3b 2d 7a c6 99
> >tiw_sta0: RSN: no matching PMKID found
> >Get randomness: len=32 entropy=189
> >WPA: Renewed SNonce - hexdump(len=32): 17 39 81 1c cc 0d 34 9b dd 88 4a
> >e7 b7 c4 85 59 69 81 06 6f bf c3 ec 66 85 6c 5c 25 bf eb f1 65
>...
View Full Message
|
|
|
|
|
|
Hugh Brown
10/15/2013 2:06 PM
post105927
|
Are you sure that this has nothing to do with the file being in NAND
flash? Try putting the configuration file in /dev/shmem and see if it
makes any difference.
The fact that it works when you run it manually means that the
configuration file is OK.
On 2013-10-15 12:48 PM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>Same thing. I think eapol_version=1 is on by default.
>
>> Try adding the following to your config file:
>>
>> eapol_version=1
>>
>>
>>
>>
>> On 2013-10-15 11:14 AM, "Steve Iribarne" <community-noreply@qnx.com>
>>wrote:
>>
>> >> Do you have any delay between starting the driver and running the
>> >> wpa_supplicant? The driver takes a while to come up as it has to
>> >>download
>> >> the firmware to the chip, so you have to have some delay in between
>> >> starting the driver and the wpa_supplicant.
>> >>
>> >
>> >I do have a 4 second delay. I will try to add a longer one.
>> >
>> >I just re-read my post. Sometimes I think I don't write english.
>> >
>> >So I did more investigation yesterday. Because I have a case in which
>>it
>> >works (run wpa_cli and then set everything by hand) and a case in which
>> >it doesn't work(when I've saved what I've done by hand to
>> >/etc/supplicant.conf).
>> >
>> >Here is my supplicant.conf file.
>> >
>> >ctrl_interface=/var/run/wpa_supplicant
>> >ctrl_interface_group=0
>> >update_config=1
>> >
>> >network={
>> > ssid="TestWIFI"
>> > psk="stvtest123"
>> > key_mgmt=WPA-PSK
>> >}
>> >
>> >
>> >I load wpa_supplicant like:
>> >
>> >SOCK=/alt /usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0
>> >-c/etc/wpa_supplicant.conf -dd -K > /tmp/supplicant.out 2>&1 &
>> >
>> >the SOCK=/alt is due to the fact that I load io-pkt-v4-hc twice and I
>> >need both drivers loaded. So the wifi sockets live on /alt/dev/socket.
>> >
>> >In the case where it works, I see the following:
>> >
>> >tiw_sta0: Setting authentication timeout: 10 sec 0 usec
>> >tiw_sta0: IEEE 802.1X RX: version=2 type=3 length=117
>> >tiw_sta0: EAPOL-Key type=2
>> >tiw_sta0: key_info 0x8a (ver=2 keyidx=0 rsvd=0 Pairwise Ack)
>> >tiw_sta0: key_length=16 key_data_length=22
>> > replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 06
>> > key_nonce - hexdump(len=32): 03 91 4e 01 76 95 c9 de f4 77 15 4b a8
>>bc
>> >c0 ac 22 9c cb e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58
>> > key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>00
>> >00
>> > key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
>> > key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
>> > key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>00
>> >00
>> >WPA: RX EAPOL-Key - hexdump(len=121): 02 03 00 75 02 00 8a 00 10 00 00
>>00
>> >00 00 00 00 06 03 91 4e 01 76 95 c9 de f4 77 15 4b a8 bc c0 ac 22 9c cb
>> >e6 fb 38 70 1e bc 77 e9 c6 7f 27 a4 58 00 00 00 00 00 00 00 00 00 00 00
>> >00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> >00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 53 6d 17
>> >35 4a 79 ee 48 97 c0 a6 3b 2d 7a c6 99
>> >HOSTAPTIW wilink_get_ssid: enter
>> >HOSTAPTIW wilink_get_bssid: enter
>> >tiw_sta0: State: ASSOCIATED -> 4WAY_HANDSHAKE
>> >tiw_sta0: WPA: RX message...
View Full Message
|
|
|
|
|
|
Steve Iribarne(deleted)
10/16/2013 8:49 AM
post105952
|
Yeah. I just tired it again.
No luck.
You are correct in that I know the config is correct. So there has to be something else that's screwing it up.
I have this setup in a typical debug environment. Where I have an ethernet connection so I can debug. So what I was
also thinking was maybe it's something to do with the dual stack thing.
So I moved my script that starts up the wifi AND the wpa_supplicant to /tmp.
lrwxrwxrwx 1 root root 10 Oct 15 2013 tmp -> /dev/shmem
drwxr-xr-x 2 root root 10 Oct 15 2013 usr
drwxr-xr-x 2 root root 10 Oct 15 2013 var
Then I edit my wistart script from Momentics IDE
echo "Starting the WIFI"
random -t -p
devb-ram ram capacity=8192 > /dev/null 2>&1
sleep 3
mount /dev/hd1t77 /var/run
sleep 2
io-pkt-v4-hc -dti127x-am335x sdio=1,dmatx=2,dmarx=3,irq=794,irq_gpio=26,gpio=38,alt_soc
sleep 4
/usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0 -c/tmp/wpa_supplicant.conf > /tmp/supplicant.out 2>&1 &
and you know my config file.
update_config=1
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
network={
ssid="TestWIFI"
psk="stvtest123"
key_mgmt=WPA-PSK
}
Once I was done editing the files, then I "slay -f io-pkt-v4-hc" and validated that it was gone by using ifconfig.
then I ran the script (from the serial port) all from tmp.
cd tmp
./wistart
Still get the same thing...
I'm just completely baffled by this. I though this was going to be a piece of cake... but it's turning out to be the most difficult part of the puzzle. :)
I still get the message:
tiw_sta0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
tiw_sta0: WPA: Could not verify EAPOL-Key MIC - dropping packet
So that's the problem but I don't understand the protocol enough to understand what is wrong with the EAPOL-Key.
thanks again for your help. I really appreciate it.
-stv
> Are you sure that this has nothing to do with the
file being in NAND
> flash? Try putting the configuration file in /dev/shmem and see if it
> makes any difference.
> The fact that it works when you run it manually means that the
> configuration file is OK.
>
>
>
> On 2013-10-15 12:48 PM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>
> >Same thing. I think eapol_version=1 is on by default.
> >
> >> Try adding the following to your config file:
> >>
> >> eapol_version=1
> >>
> >>
> >>
> >>
> >> On 2013-10-15 11:14 AM, "Steve Iribarne" <community-noreply@qnx.com>
> >>wrote:
> >>
> >> >> Do you have any delay between starting the driver and running the
> >> >> wpa_supplicant? The driver takes a while to come up as it has to
> >> >>download
> >> >> the firmware to the chip, so you have to have some delay in between
> >> >> starting the driver and the wpa_supplicant.
> >> >>
> >> >
> >> >I do have a 4 second delay. I will try to add a longer one.
> >> >
> >> >I just re-read my post. Sometimes I think I don't write english.
> >> >
> >> >So I did more investigation yesterday. Because I have a case in which
> >>it
> >> >works (run wpa_cli and then set everything by hand) and a case in which
> >> >it doesn't work(when I've saved what I've done by hand to
> >> >/etc/supplicant.conf).
> >> >
> >> >Here is my supplicant.conf file.
> >> >
> >> >ctrl_interface=/var/run/wpa_supplicant
> >> >ctrl_interface_group=0
> >> >update_config=1
> >> >
> >> >network={
> >> > ssid="TestWIFI"
> >>...
View Full Message
|
|
|
|
|
|
Hugh Brown
10/16/2013 12:04 PM
post105974
|
I have sent your query to TI to ask for their comments. As soon as I get a
reply, I'll let you know.
On 2013-10-16 8:49 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>Yeah. I just tired it again.
>No luck.
>
>You are correct in that I know the config is correct. So there has to be
>something else that's screwing it up.
>
>I have this setup in a typical debug environment. Where I have an
>ethernet connection so I can debug. So what I was also thinking was
>maybe it's something to do with the dual stack thing.
>
>So I moved my script that starts up the wifi AND the wpa_supplicant to
>/tmp.
>
>lrwxrwxrwx 1 root root 10 Oct 15 2013 tmp -> /dev/shmem
>drwxr-xr-x 2 root root 10 Oct 15 2013 usr
>drwxr-xr-x 2 root root 10 Oct 15 2013 var
>
>Then I edit my wistart script from Momentics IDE
>
>echo "Starting the WIFI"
>random -t -p
>devb-ram ram capacity=8192 > /dev/null 2>&1
>sleep 3
>mount /dev/hd1t77 /var/run
>sleep 2
>io-pkt-v4-hc -dti127x-am335x
>sdio=1,dmatx=2,dmarx=3,irq=794,irq_gpio=26,gpio=38,alt_soc
>sleep 4
>/usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0
>-c/tmp/wpa_supplicant.conf > /tmp/supplicant.out 2>&1 &
>
>and you know my config file.
>
>update_config=1
>ctrl_interface=/var/run/wpa_supplicant
>ctrl_interface_group=0
>network={
> ssid="TestWIFI"
> psk="stvtest123"
> key_mgmt=WPA-PSK
>}
>
>
>Once I was done editing the files, then I "slay -f io-pkt-v4-hc" and
>validated that it was gone by using ifconfig.
>
>then I ran the script (from the serial port) all from tmp.
>
>cd tmp
>./wistart
>
>Still get the same thing...
>
>I'm just completely baffled by this. I though this was going to be a
>piece of cake... but it's turning out to be the most difficult part of
>the puzzle. :)
>
>I still get the message:
>
>tiw_sta0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
>tiw_sta0: WPA: Could not verify EAPOL-Key MIC - dropping packet
>
>So that's the problem but I don't understand the protocol enough to
>understand what is wrong with the EAPOL-Key.
>
>thanks again for your help. I really appreciate it.
>
>-stv
>
>
>> Are you sure that this has nothing to do with the file being in NAND
>> flash? Try putting the configuration file in /dev/shmem and see if it
>> makes any difference.
>> The fact that it works when you run it manually means that the
>> configuration file is OK.
>>
>>
>>
>> On 2013-10-15 12:48 PM, "Steve Iribarne" <community-noreply@qnx.com>
>>wrote:
>>
>> >Same thing. I think eapol_version=1 is on by default.
>> >
>> >> Try adding the following to your config file:
>> >>
>> >> eapol_version=1
>> >>
>> >>
>> >>
>> >>
>> >> On 2013-10-15 11:14 AM, "Steve Iribarne" <community-noreply@qnx.com>
>> >>wrote:
>> >>
>> >> >> Do you have any delay between starting the driver and running the
>> >> >> wpa_supplicant? The driver takes a while to come up as it has to
>> >> >>download
>> >> >> the firmware to the chip, so you have to have some delay in
>>between
>> >> >> starting the driver and the wpa_supplicant.
>> >> >>
>> >> >
>> >> >I do have a 4 second delay. I will try to add a longer one.
>> >> >
>> >> >I just re-read my post. Sometimes I think I don't write english.
>> >> >
>>...
View Full Message
|
|
|
|
|
|
Steve Iribarne(deleted)
10/16/2013 12:18 PM
post105976
|
Thanks a ton!
> I have sent your query to TI to ask for their comments. As soon as I get a
> reply, I'll let you know.
>
>
>
>
> On 2013-10-16 8:49 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>
> >Yeah. I just tired it again.
> >No luck.
> >
> >You are correct in that I know the config is correct. So there has to be
> >something else that's screwing it up.
> >
> >I have this setup in a typical debug environment. Where I have an
> >ethernet connection so I can debug. So what I was also thinking was
> >maybe it's something to do with the dual stack thing.
> >
> >So I moved my script that starts up the wifi AND the wpa_supplicant to
> >/tmp.
> >
> >lrwxrwxrwx 1 root root 10 Oct 15 2013 tmp -> /dev/shmem
> >drwxr-xr-x 2 root root 10 Oct 15 2013 usr
> >drwxr-xr-x 2 root root 10 Oct 15 2013 var
> >
> >Then I edit my wistart script from Momentics IDE
> >
> >echo "Starting the WIFI"
> >random -t -p
> >devb-ram ram capacity=8192 > /dev/null 2>&1
> >sleep 3
> >mount /dev/hd1t77 /var/run
> >sleep 2
> >io-pkt-v4-hc -dti127x-am335x
> >sdio=1,dmatx=2,dmarx=3,irq=794,irq_gpio=26,gpio=38,alt_soc
> >sleep 4
> >/usr/sbin/wpa_supplicant_ti -Dwilink -itiw_sta0
> >-c/tmp/wpa_supplicant.conf > /tmp/supplicant.out 2>&1 &
> >
> >and you know my config file.
> >
> >update_config=1
> >ctrl_interface=/var/run/wpa_supplicant
> >ctrl_interface_group=0
> >network={
> > ssid="TestWIFI"
> > psk="stvtest123"
> > key_mgmt=WPA-PSK
> >}
> >
> >
> >Once I was done editing the files, then I "slay -f io-pkt-v4-hc" and
> >validated that it was gone by using ifconfig.
> >
> >then I ran the script (from the serial port) all from tmp.
> >
> >cd tmp
> >./wistart
> >
> >Still get the same thing...
> >
> >I'm just completely baffled by this. I though this was going to be a
> >piece of cake... but it's turning out to be the most difficult part of
> >the puzzle. :)
> >
> >I still get the message:
> >
> >tiw_sta0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
> >tiw_sta0: WPA: Could not verify EAPOL-Key MIC - dropping packet
> >
> >So that's the problem but I don't understand the protocol enough to
> >understand what is wrong with the EAPOL-Key.
> >
> >thanks again for your help. I really appreciate it.
> >
> >-stv
> >
> >
> >> Are you sure that this has nothing to do with the file being in NAND
> >> flash? Try putting the configuration file in /dev/shmem and see if it
> >> makes any difference.
> >> The fact that it works when you run it manually means that the
> >> configuration file is OK.
> >>
> >>
> >>
> >> On 2013-10-15 12:48 PM, "Steve Iribarne" <community-noreply@qnx.com>
> >>wrote:
> >>
> >> >Same thing. I think eapol_version=1 is on by default.
> >> >
> >> >> Try adding the following to your config file:
> >> >>
> >> >> eapol_version=1
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On 2013-10-15 11:14 AM, "Steve Iribarne" <community-noreply@qnx.com>
> >> >>wrote:
> >> >>
> >> >> >> Do you have any delay between starting the driver and running the
> >> >> >> wpa_supplicant? The driver...
View Full Message
|
|
|
|
|
|
Steve Iribarne(deleted)
10/16/2013 3:25 PM
post105986
|
Hey.. something very interesting just happened. So the same application that is loading and controlling the
wpa_supplicant (using the API's) has a memory issue. So what I did was enabled the memory checker tool. And when I did
the commands by hand, I get the same error.
I'm now wondering if this is a timing issue and the thread is not getting enough time to run. I'll let you know.
|
|
|
|
|
|
Steve Iribarne(deleted)
10/23/2013 7:19 AM
post106160
|
Hugh,
Have you heard anything? If not, I may have to go to Plan B soon. Keep my own config file.
Thanks for any update you can give.
|
|
|
|
|
|
Hugh Brown
10/23/2013 8:32 AM
post106162
|
I have sent a wake-up email to TI, so will let you know as soon as I get
an answer.
On 2013-10-23 7:19 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>Hugh,
>
>Have you heard anything? If not, I may have to go to Plan B soon. Keep
>my own config file.
>
>Thanks for any update you can give.
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post106160
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
Hugh Brown
10/24/2013 11:05 AM
post106217
|
Please can you send the sloginfo output when the problem occurs as well as
the firmware version. That is what TI is asking for.
Thanks, Hugh.
On 10/23/2013, 7:19 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>Hugh,
>
>Have you heard anything? If not, I may have to go to Plan B soon. Keep
>my own config file.
>
>Thanks for any update you can give.
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post106160
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
Steve Iribarne(deleted)
10/24/2013 4:09 PM
post106231
|
Hello Hugh.
I've attached a file with the sloginfo output.
The FW version is inside the slog info log.
Thanks .
-stv
> Please can you send the sloginfo output when the problem occurs as well as
> the firmware version. That is what TI is asking for.
>
> Thanks, Hugh.
>
>
>
> On 10/23/2013, 7:19 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>
> >Hugh,
> >
> >Have you heard anything? If not, I may have to go to Plan B soon. Keep
> >my own config file.
> >
> >Thanks for any update you can give.
> >
> >
> >
> >_______________________________________________
> >
> >General
> >http://community.qnx.com/sf/go/post106160
> >To cancel your subscription to this discussion, please e-mail
> >general-community-unsubscribe@community.qnx.com
>
|
|
|
|
|
|
Hugh Brown
10/28/2013 7:29 AM
post106300
|
The TI guys have told me that you aren¹t using the latest version of the
driver, so can you please try the latest version and see if it resolves
your problem?
On 10/24/2013, 4:09 PM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>Hello Hugh.
>
>I've attached a file with the sloginfo output.
>
>The FW version is inside the slog info log.
>
>Thanks .
>
>-stv
>
>> Please can you send the sloginfo output when the problem occurs as well
>>as
>> the firmware version. That is what TI is asking for.
>>
>> Thanks, Hugh.
>>
>>
>>
>> On 10/23/2013, 7:19 AM, "Steve Iribarne" <community-noreply@qnx.com>
>>wrote:
>>
>> >Hugh,
>> >
>> >Have you heard anything? If not, I may have to go to Plan B soon.
>>Keep
>> >my own config file.
>> >
>> >Thanks for any update you can give.
>> >
>> >
>> >
>> >_______________________________________________
>> >
>> >General
>> >http://community.qnx.com/sf/go/post106160
>> >To cancel your subscription to this discussion, please e-mail
>> >general-community-unsubscribe@community.qnx.com
>>
>
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post106231
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
Steve Iribarne(deleted)
10/28/2013 7:32 AM
post106301
|
> The TI guys have told me that you aren¹t using the latest version of the
> driver, so can you please try the latest version and see if it resolves
> your problem?
>
>
Sure. I'm using the one that came with our BSP distro. Where do I get the latest one from TI's website? I'll try
there, but if you have a better place plz point me to it.
Thanks for your efforts.
|
|
|
|
|
|
Hugh Brown
10/28/2013 7:35 AM
post106302
|
The driver can be downloaded from our web site and is included with the
specific BSP that you are using.
On 10/28/2013, 7:32 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>> The TI guys have told me that you aren¹t using the latest version of the
>> driver, so can you please try the latest version and see if it resolves
>> your problem?
>>
>>
>
>Sure. I'm using the one that came with our BSP distro. Where do I get
>the latest one from TI's website? I'll try there, but if you have a
>better place plz point me to it.
>
>Thanks for your efforts.
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post106301
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
Steve Iribarne(deleted)
10/28/2013 7:39 AM
post106303
|
> The driver can be downloaded from our web site and is included with the
> specific BSP that you are using.
>
But I am using the one that was distributed with 6.5.0 SP1. Is there a later version? Must be..
>
>
>
>
> On 10/28/2013, 7:32 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>
> >> The TI guys have told me that you aren¹t using the latest version of the
> >> driver, so can you please try the latest version and see if it resolves
> >> your problem?
> >>
> >>
> >
> >Sure. I'm using the one that came with our BSP distro. Where do I get
> >the latest one from TI's website? I'll try there, but if you have a
> >better place plz point me to it.
> >
> >Thanks for your efforts.
> >
> >
> >
> >_______________________________________________
> >
> >General
> >http://community.qnx.com/sf/go/post106301
> >To cancel your subscription to this discussion, please e-mail
> >general-community-unsubscribe@community.qnx.com
>
|
|
|
|
|
|
Hugh Brown
10/28/2013 7:43 AM
post106304
|
There was a new driver that we received from TI in May this year. It is
included in one of our BSPs - I’m not sure which one, but I can find out.
--
On 10/28/2013, 7:39 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>> The driver can be downloaded from our web site and is included with the
>> specific BSP that you are using.
>>
>
>But I am using the one that was distributed with 6.5.0 SP1. Is there a
>later version? Must be..
>
>
>>
>>
>>
>>
>> On 10/28/2013, 7:32 AM, "Steve Iribarne" <community-noreply@qnx.com>
>>wrote:
>>
>> >> The TI guys have told me that you aren¹t using the latest version of
>>the
>> >> driver, so can you please try the latest version and see if it
>>resolves
>> >> your problem?
>> >>
>> >>
>> >
>> >Sure. I'm using the one that came with our BSP distro. Where do I get
>> >the latest one from TI's website? I'll try there, but if you have a
>> >better place plz point me to it.
>> >
>> >Thanks for your efforts.
>> >
>> >
>> >
>> >_______________________________________________
>> >
>> >General
>> >http://community.qnx.com/sf/go/post106301
>> >To cancel your subscription to this discussion, please e-mail
>> >general-community-unsubscribe@community.qnx.com
>>
>
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post106303
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
Steve Iribarne(deleted)
10/28/2013 7:50 AM
post106305
|
> There was a new driver that we received from TI in May this year. It is
> included in one of our BSPs - I’m not sure which one, but I can find out.
>
Yeah that'd be great. Because I can't find it. I've searched both your site and TI's site.
> --
>
>
>
> On 10/28/2013, 7:39 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>
> >> The driver can be downloaded from our web site and is included with the
> >> specific BSP that you are using.
> >>
> >
> >But I am using the one that was distributed with 6.5.0 SP1. Is there a
> >later version? Must be..
> >
> >
> >>
> >>
> >>
> >>
> >> On 10/28/2013, 7:32 AM, "Steve Iribarne" <community-noreply@qnx.com>
> >>wrote:
> >>
> >> >> The TI guys have told me that you aren¹t using the latest version of
> >>the
> >> >> driver, so can you please try the latest version and see if it
> >>resolves
> >> >> your problem?
> >> >>
> >> >>
> >> >
> >> >Sure. I'm using the one that came with our BSP distro. Where do I get
> >> >the latest one from TI's website? I'll try there, but if you have a
> >> >better place plz point me to it.
> >> >
> >> >Thanks for your efforts.
> >> >
> >> >
> >> >
> >> >_______________________________________________
> >> >
> >> >General
> >> >http://community.qnx.com/sf/go/post106301
> >> >To cancel your subscription to this discussion, please e-mail
> >> >general-community-unsubscribe@community.qnx.com
> >>
> >
> >
> >
> >
> >
> >
> >_______________________________________________
> >
> >General
> >http://community.qnx.com/sf/go/post106303
> >To cancel your subscription to this discussion, please e-mail
> >general-community-unsubscribe@community.qnx.com
>
|
|
|
|
|
|
Hugh Brown
10/28/2013 10:14 AM
post106313
|
I have attached the latest patch file of the driver.
On 10/28/2013, 7:50 AM, "Steve Iribarne" <community-noreply@qnx.com> wrote:
>> There was a new driver that we received from TI in May this year. It is
>> included in one of our BSPs - I’m not sure which one, but I can find
>>out.
>>
>
>Yeah that'd be great. Because I can't find it. I've searched both your
>site and TI's site.
>
>
>> --
>>
>>
>>
>> On 10/28/2013, 7:39 AM, "Steve Iribarne" <community-noreply@qnx.com>
>>wrote:
>>
>> >> The driver can be downloaded from our web site and is included with
>>the
>> >> specific BSP that you are using.
>> >>
>> >
>> >But I am using the one that was distributed with 6.5.0 SP1. Is there a
>> >later version? Must be..
>> >
>> >
>> >>
>> >>
>> >>
>> >>
>> >> On 10/28/2013, 7:32 AM, "Steve Iribarne" <community-noreply@qnx.com>
>> >>wrote:
>> >>
>> >> >> The TI guys have told me that you aren¹t using the latest version
>>of
>> >>the
>> >> >> driver, so can you please try the latest version and see if it
>> >>resolves
>> >> >> your problem?
>> >> >>
>> >> >>
>> >> >
>> >> >Sure. I'm using the one that came with our BSP distro. Where do I
>>get
>> >> >the latest one from TI's website? I'll try there, but if you have a
>> >> >better place plz point me to it.
>> >> >
>> >> >Thanks for your efforts.
>> >> >
>> >> >
>> >> >
>> >> >_______________________________________________
>> >> >
>> >> >General
>> >> >http://community.qnx.com/sf/go/post106301
>> >> >To cancel your subscription to this discussion, please e-mail
>> >> >general-community-unsubscribe@community.qnx.com
>> >>
>> >
>> >
>> >
>> >
>> >
>> >
>> >_______________________________________________
>> >
>> >General
>> >http://community.qnx.com/sf/go/post106303
>> >To cancel your subscription to this discussion, please e-mail
>> >general-community-unsubscribe@community.qnx.com
>>
>
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post106305
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
Steve Iribarne(deleted)
10/28/2013 12:16 PM
post106321
|
Nope.. driver crashes with this.
Process 102425 (io-pkt-v4-hc) terminated SIGBUS code=3 fltno=5 ip=78020afc(/proc/boot/devnp-ti1273-am335xevm.so@
hPlatform_Wlan_Hardware_Init+0x134) mapaddr=00020afc. ref=2800806c
sloginfo
Jan 01 00:06:40 5 14 0 initializing IPsec... done
Jan 01 00:06:40 5 14 0 IPsec: Initialized Security Association Processing.
Jan 01 00:06:40 3 10 1 sdio option 1 specified
Jan 01 00:06:40 3 10 1 dmatx value set to 0x2
Jan 01 00:06:40 3 10 1 dmarx value set to 0x3
Jan 01 00:06:40 3 10 1 irq value set to 0x31a
Jan 01 00:06:40 3 10 1 gpio value set to 38
Jan 01 00:06:41 3 10 1 hPlatform_Wlan_Hardware_Init
We can stop worrying about it. I have written my own config file handling. Thanks again for all your help.
-stv
|
|
|
|
|
|
Armin Steinhoff
|
[Question] PCIexpress supported by QNX 4.25 ?
|
|
Armin Steinhoff
11/11/2013 11:39 AM
post106665
|
[Question] PCIexpress supported by QNX 4.25 ?
Hi,
supports QNX 4.25 PCIe interfaces ?
Regards
--Armin
|
|
|
|
|
|
Hugh Brown
|
Re: [Question] PCIexpress supported by QNX 4.25 ?
|
|
Hugh Brown
11/11/2013 12:19 PM
post106666
|
Re: [Question] PCIexpress supported by QNX 4.25 ?
The _CA_PCIŠ function calls are the same for both PCI and PCIe. The only
thing that you won¹t be able to do with these function calls is to access
the extended PCIe configuration space, unless the BIOS supports it.
On 2013/11/11, 11:39 AM, "Armin Steinhoff" <community-noreply@qnx.com>
wrote:
>
>Hi,
>
>supports QNX 4.25 PCIe interfaces ?
>
>Regards
>
>--Armin
>
>
>
>
>
>
>
>_______________________________________________
>
>General
>http://community.qnx.com/sf/go/post106665
>To cancel your subscription to this discussion, please e-mail
>general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
Armin Steinhoff
|
Re: [Question] PCIexpress supported by QNX 4.25 ?
|
|
Armin Steinhoff
11/12/2013 5:06 AM
post106683
|
Re: [Question] PCIexpress supported by QNX 4.25 ?
Hugh,
many thanks ..
I'm testing currently my port of the DPDK from Intel.
When I send with "testpmd" a burst of packets, my I210 adapter drops a
lot of packets.
Do you have an idea why an ethernet adapter is dropping packets when
packets are transmitted ?
--Armin
Hugh Brown wrote:
> The _CA_PCIÅ function calls are the same for both PCI and PCIe. The only
> thing that you won¹t be able to do with these function calls is to access
> the extended PCIe configuration space, unless the BIOS supports it.
>
>
>
> On 2013/11/11, 11:39 AM, "Armin Steinhoff" <community-noreply@qnx.com>
> wrote:
>
>> Hi,
>>
>> supports QNX 4.25 PCIe interfaces ?
>>
>> Regards
>>
>> --Armin
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post106665
>> To cancel your subscription to this discussion, please e-mail
>> general-community-unsubscribe@community.qnx.com
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post106666
> To cancel your subscription to this discussion, please e-mail general-community-unsubscribe@community.qnx.com
|
|
|
|
|
|
