6 Replies Latest reply on Sep 5, 2017 3:21 PM by nick.bourdon_1521531

    Type 1CK integration on a BD-SL-i.MX6

    nick.bourdon_1521531

      Hello, I'm using a Murata Type 1CK (BCM4339) with a Boundary BD-SL (i.MX6Q) dev board. The very similar Nitrogen6X supposedly supports the 1CK by default, but it is configured to use SDIO2 which does not exist on the BD-SL, so I am basing my changes on that board's configuration but using SDIO3.

       

      I've made a number of changes so far including:

      -updating the device tree to configure SDIO3 to be the wifi host and configured a GPIO to act as my WL_EN

      -enabled BCMDHD int he device config

      -copied the correct NVRAM and firmware files to the expected locations

       

      I have not yet tried to support Bluetooth. I assume this won't affect wifi operation.

       

      I am still unable to get wifi working, my log is below. It is clearly upset about the P2P Supplicant, but I don't know how to address this issue, if there is anything else wrong that could be causing this problem, or if P2P operation is even critical to normal wifi operation. I've tried working backward from a few of these error messages without any luck thus far. Any advice would be very much appreciated. Thanks.

       

      Dongle Host Driver, version 1.141.88 (r)

      Compiled from

      wl_android_wifi_on in

      sdio_reset_comm():

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

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

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

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

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

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

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

      dhdsdio_download_code_file: firmware path: /system/vendor/firmware/fw_bcmdhd.bin

      dhdsdio_download_nvram: nvram path: /system/etc/wifi/bcmdhd.cal

      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=a0:cc:2b:61:94:28

      Firmware version = wl0: Feb 17 2016 18:29:33 version 6.37.32.RC23.34.42 (r608406)

      dhd_wlfc_init(): successfully enabled bdcv2 tlv signaling, 79

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

      wl_create_event_handler(): thread:wl_event_handler:6d8 started

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

      init: Starting service 'p2p_supplicant'...

      CFG80211-ERROR) wl_event_handler : was terminated

      wl_destroy_event_handler(): thread:wl_event_handler:6d8 terminated OK

      wl_android_wifi_off in

      dhd_wlfc_deinit():3277, maintain HOST RXRERODER flag in tvl

      dhd_wlfc_deinit():3291 successfully disabled bdcv2 tlv signaling, 64

      init: Service 'p2p_supplicant' (pid 1755) exited with status 255

        • 1. Re: Type 1CK integration on a BD-SL-i.MX6
          nick.bourdon_1521531

          Also, here is my logcat:

           

          01-01 00:07:47.263 500-972/system_process D/wifi: set interface wlan0 flags (UP)

          01-01 00:07:47.264 500-972/system_process I/WifiHAL: Initializing wifi

          01-01 00:07:47.264 500-972/system_process I/WifiHAL: Creating socket

          01-01 00:07:47.266 500-972/system_process I/WifiHAL: Initialized Wifi HAL Successfully; vendor cmd = 103

          01-01 00:07:47.266 500-972/system_process D/wifi: Did set static halHandle = 0x84a960e0

          01-01 00:07:47.266 500-972/system_process D/wifi: halHandle = 0x84a960e0, mVM = 0xa4c320c0, mCls = 0x122e

          01-01 00:07:47.267 500-972/system_process D/wifi: array field set

          01-01 00:07:47.268 500-1779/system_process I/WifiNative-HAL: Waiting for HAL events mWifiHalHandle=-2069274400

          01-01 00:07:47.272 500-1779/system_process D/wifi: waitForHalEvents called, vm = 0xa4c320c0, obj = 0x122e, env = 0x7ca2cc40

          01-01 00:07:47.352 1780-1780/? I/wpa_supplicant: Successfully initialized wpa_supplicant

          01-01 00:07:47.355 1780-1780/? E/wpa_supplicant: Could not read interface p2p0 flags: No such device

          01-01 00:07:47.355 1780-1780/? I/wpa_supplicant: nl80211: Driver does not support authentication/association or connect commands

          01-01 00:07:47.355 1780-1780/? I/wpa_supplicant: nl80211: deinit ifname=p2p0 disabled_11b_rates=0

          01-01 00:07:47.356 1780-1780/? E/wpa_supplicant: Could not read interface p2p0 flags: No such device

          01-01 00:07:47.356 1780-1780/? E/wpa_supplicant: p2p0: Failed to initialize driver interface

          01-01 00:07:47.368 500-972/system_process E/WifiStateMachine: Failed to start supplicant!

          01-01 00:07:47.370 500-500/system_process E/WifiController: WifiControllerWifi turn on failed

          • 2. Re: Type 1CK integration on a BD-SL-i.MX6
            mifo

            Moving to the Murata support forum, adding ghouse and skerr_1713761 from Murata.

            • 3. Re: Type 1CK integration on a BD-SL-i.MX6
              ghouse

              Only NXP iMX6 boards are supported. If you can check this on NXP's iMX6 platform with 1CK, that will be helpful to look at this.

               

              However, have you looked at the Quickstart guide http://wireless.murata.com/datasheet?/RFM/data/murata_quick_start_guide_linux.pdf

               

              Look at section 4 on how to apply the patches and make sure you are pointing to correct firmware version for 1CK.  Look at Table 6 in the document on files that you are supposed to use.

              1 of 1 people found this helpful
              • 4. Re: Type 1CK integration on a BD-SL-i.MX6
                nick.bourdon_1521531

                I apologize for the delay, I was out of the office last week. Thank you for your response.

                 

                The trouble is that since I am porting this to a (minimally) different board, binaries and patches don't always apply, especially in the case of a .dtb. Is there any way to get the source for these and perhaps a rationale behind the changes so I can apply them in my source?

                • 5. Re: Type 1CK integration on a BD-SL-i.MX6
                  ghouse

                  nick.bourdon_1521531, the driver is open source. you need to refer to the Linux user manual for more detailed description. Linux user manual on My Murata. The Linux Quick start guide which I was point out has description on the changes applied in the patch files. If you go through these documents you will find lot of information.  

                  1 of 1 people found this helpful
                  • 6. Re: Type 1CK integration on a BD-SL-i.MX6
                    nick.bourdon_1521531

                    I've been over all the manuals; they are what got me to where I am now. I'll post back if I find a solution.