7 Replies Latest reply on Aug 12, 2016 3:22 PM by vens

    Failed to connect SN8000 (BCM43362) module with WPA2PSK, WPAPSK network

    dhvanil

      HI All,

       

      I am using a SN8000 module on i.MX6UL. I have used linux kernel version 3.14.52 and used "BRCM_FW_for_i.MX_04062016" firmware. The kernel driver is successfully loaded and wlan0 interface is created and up.

       

      Now I have used wl utility to join ssid. The SN8000 is successfully able to join open network. When I tried to connect SN8000 to secured network using wl join command, It is failed to join private network.

       

       

      wl command for WPA2PSK network logs:

      The wl command show successful but every time the access point mac address is changed . Actually it is not connected with access point

      root@imx6ulevk:~/VT_BOARD#  wl join Bimal key 3132333435363738 imode ibss amode wp

      root@imx6ulevk:~/VT_BOARD# wl_bss_connect_done succeeded with a2:d6:d2:95:d6:a9

      wl_bss_connect_done succeeded with a2:d6:d2:95:d6:a9

       

       

      pa2pskmx6ulevk:~/VT_BOARD# wl join Bimal key 3132333435363738 imode ibss amode wp

      root@imx6ulevk:~/VT_BOARD# wl_bss_connect_done succeeded with 32:17:ee:82:17:d5

      wl_bss_connect_done succeeded with 32:17:ee:82:17:d5

       

       

      pa2pskmx6ulevk:~/VT_BOARD# wl join Bimal key 3132333435363738 imode ibss amode wp

      root@imx6ulevk:~/VT_BOARD# wl_bss_connect_done succeeded with 62:19:31:9c:19:ce

      wl_bss_connect_done succeeded with 62:19:31:9c:19:ce

       

      root@imx6ulevk:~/VT_BOARD#

      pa2pskmx6ulevk:~/VT_BOARD# wl join Bimal key 3132333435363738 imode ibss amode wp

      root@imx6ulevk:~/VT_BOARD# wl_bss_connect_done succeeded with 76:74:b8:b6:74:94

      wl_bss_connect_done succeeded with 76:74:b8:b6:74:94

       

      wl command for Open network

      The wl command show successful but every  access point mac address is same. It is  connected with access point and able to ping google

      root@imx6ulevk:~/VT_BOARD# wl join Bimal

      root@imx6ulevk:~/VT_BOARD# CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH

      wl_bss_connect_done succeeded with 5c:51:88:7c:6d:61

       

       

      root@imx6ulevk:~/VT_BOARD# wl join Bimal

      root@imx6ulevk:~/VT_BOARD# CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH

      wl_bss_connect_done succeeded with 5c:51:88:7c:6d:61

       

      I have also tried to run wpa_supplicant utility on wlan0 interface. But it is giving an error while executing an utility.

       

      Can anybody provide help to resolve this issue.?

       

      -

      Dhvanil Patel

        • 2. Re: Failed to connect SN8000 (BCM43362) module with WPA2PSK, WPAPSK network
          dhvanil

          Hi,

           

          Thanks for adding linux application support team,

           

          I have also test it with wpa_supplicant and wpa_cli utility (Link Unable to join a network) . But when I enable the network on wpa_cli command prompt, I am getting following error message.

           

          1

          > OK

          <3>Trying to associate with SSID 'Belkin_Ay'

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          <3>Association request to the driver failed

          <3>CTRL-EVENT-SCAN-STARTED

          <3>CTRL-EVENT-SCAN-RESULTS

          <3>WPS-AP-AVAILABLE

          <3>Trying to associate with SSID 'Belkin_Ay'

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          <3>Association request to the driver failed

          <3>CTRL-EVENT-SCAN-STARTED

          <3>CTRL-EVENT-SCAN-RESULTS

          <3>WPS-AP-AVAILABLE

          <3>Trying to associate with SSID 'Belkin_Ay'

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          <3>Association request to the driver failed

          <3>CTRL-EVENT-SCAN-STARTED

          <3>CTRL-EVENT-SCAN-RESULTS

          <3>WPS-AP-AVAILABLE

          <3>Trying to associate with SSID 'Belkin_Ay'

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          <3>Association request to the driver failed

          > root@imx6ulevk:~/VT_BOARD# CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          CFG80211-ERROR) wl_cfg80211_connect : Connectting withff:ff:ff:ff:ff:ff channel (0) ssid "Belkin_Ay", len (9)

          CFG80211-ERROR) wl_cfg80211_connect : error (-14)

          • 3. Re: Failed to connect SN8000 (BCM43362) module with WPA2PSK, WPAPSK network
            dhvanil

            Hi Murata Support team,

             

            Waiting for your response.

            • 4. Re: Failed to connect SN8000 (BCM43362) module with WPA2PSK, WPAPSK network
              vens

              Hi dhvanil

               

              I don't have an SN8000 with me now. But here is logs from a ZP module. Could you use the commands from these logs to see whether it works for you?

               

               

              root@imx6ulevk:~/bcm_imx# ./scripts/insmod_dhd.sh

              FW=/lib/firmware/bcm/fw_bcmdhd.bin

              NVRAM=/lib/firmware/bcm/bcmdhd.cal

              dhd_module_init in

              Power-up adapter 'DHD generic adapter'

              wifi_platform_bus_enumerate device present 1

              mmc0: queuing unknown CIS tuple 0x80 (2 bytes)

              mmc0: queuing unknown CIS tuple 0x80 (7 bytes)

              mmc0: queuing unknown CIS tuple 0x80 (6 bytes)

              mmc0: queuing unknown CIS tuple 0x91 (3 bytes)

              mmc0: new high speed SDIO card at address 0001

              F1 signature OK, socitype:0x1 chip:0x4339 rev:0x1 pkg:0x0

              DHD: dongle ram size is set to 786432(orig 786432) at 0x180000

              wifi_platform_get_mac_addr

              CFG80211-ERROR) wl_setup_wiphy : Registering Vendor80211)

              wl_create_event_handler(): thread:wl_event_handler:35a started

              CFG80211-ERROR) wl_event_handler : tsk Enter, tsk = 0x88ee141c

              dhd_attach(): thread:dhd_watchdog_thread:35b started

              dhd_attach(): thread:dhd_dpc:35c started

              dhd_deferred_work_init: work queue initialized

              dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.

              dhd_bus_init: enable 0x06, ready 0x06 (waited 0us)

              wifi_platform_get_mac_addr

              Firmware up: op_mode=0x0005, MAC=98:f1:70:6a:a7:a7

              Firmware version = wl0: Jul 16 2015 22:46:14 version 6.37.39.16 (r550328)

              dhd_wlfc_init(): successfully enabled bdcv2 tlv signaling, 79

              dhd_wlfc_init(): wlfc_mode=0x0, ret=-23

               

               

              Dongle Host Driver, version 1.141.72 (r)

              Compiled from

              Register interface [wlan0]  MAC: 98:f1:70:6a:a7:a7

               

               

              root@imx6ulevk:~/bcm_imx#

              root@imx6ulevk:~/bcm_imx#

              root@imx6ulevk:~/bcm_imx#

              root@imx6ulevk:~/bcm_imx#

              ..

              ..

              root@imx6ulevk:~/bcm_imx#

              root@imx6ulevk:~/bcm_imx#

              ..

              + killall wpa_supplicant

              + sleep 1

              + wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D nl80211

              Successfully initialized wpa_supplicant

              rfkill: Cannot open RFKILL control device

              _dhd_wlfc_mac_entry_update():1649, entry(32)

              + set +x

              root@imx6ulevk:~/bcm_imx#

              root@imx6ulevk:~/bcm_imx# uname -a

              Linux imx6ulevk 3.14.52-135322-g5f6f0a5 #2 SMP PREEMPT Wed Mar 16 12:31:44 PDT 2016 armv7l GNU/Linux

              ..

              ..

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 disconnect

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 list_network

              network id / ssid / bssid / flags

              0       vs-33031c-5g    any     [DISABLED]

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 remove_network 0

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 add_network

              0

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 set_network 0 ssid '"vs-33031c-5g"'

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 set_network 0 proto WPA2

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 set_network 0 key_mgmt WPA-PSK

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 set_network 0 pairwise CCMP

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 set_network 0 psk '"12345678"'

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 save_config

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 enable_network 0

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 select_network 0

              OK

              + wpa_cli -p/var/run/wpa_supplicant -iwlan0 status

              wpa_state=SCANNING

              address=98:f1:70:6a:a7:a7

              uuid=2f763fd1-9ef3-5dad-9225-9e46a279e998

              ...

              + ifconfig wlan0 192.168.1.11

              ..

              ..

              root@imx6ulevk:~/bcm_imx# ping 192.168.1.1

              + ping 192.168.1.1

              PING 192.168.1.1 (192.168.1.1): 56 data bytes

              64 bytes from 192.168.1.1: seq=0 ttl=64 time=11.322 ms

              64 bytes from 192.168.1.1: seq=1 ttl=64 time=9.989 ms

              64 bytes from 192.168.1.1: seq=2 ttl=64 time=10.571 ms

              ^C

              --- 192.168.1.1 ping statistics ---

              3 packets transmitted, 3 packets received, 0% packet loss

              round-trip min/avg/max = 9.989/10.627/11.322 ms

              root@imx6ulevk:~/bcm_imx#

               

              Thanks,

              Venkat

              • 5. Re: Failed to connect SN8000 (BCM43362) module with WPA2PSK, WPAPSK network
                vens

                The commands works on SN8000 too. Attached are logs from SN800.

                • 6. Re: Failed to connect SN8000 (BCM43362) module with WPA2PSK, WPAPSK network
                  vens

                  dhvanil

                  I was able to reproduce this issue with 141.88 driver. As a temporary solution please disable DROAM_ENABLE in the Makefile. We shall continue to investigate this issue further.

                   

                  diff --git a/bcmdhd/Makefile b/bcmdhd/Makefile

                  index e15f5cc..8b8416b 100644

                  --- a/bcmdhd/Makefile

                  +++ b/bcmdhd/Makefile

                  @@ -40,7 +40,7 @@ DHDCFLAGS += -DCUSTOM_TDLS_RSSI_THRESHOLD_LOW=-70

                   

                  # Roaming

                  DHDCFLAGS += -DROAM_AP_ENV_DETECTION

                  -DHDCFLAGS += -DROAM_ENABLE -DROAM_CHANNEL_CACHE -DROAM_API

                  +DHDCFLAGS += -DROAM_CHANNEL_CACHE -DROAM_API

                  DHDCFLAGS += -DENABLE_FW_ROAM_SUSPEND

                  # Roaming trigger

                  DHDCFLAGS += -DCUSTOM_ROAM_TRIGGER_SETTING=-75

                  1 of 1 people found this helpful
                  • 7. Re: Failed to connect SN8000 (BCM43362) module with WPA2PSK, WPAPSK network
                    vens

                    Please get the firmware from 08/12/2016 @ https://community.cypress.com/docs/DOC-2661

                    With this updated firmware disable of ROAM_API is not required.

                    Thanks,

                    Venkat