9 Replies Latest reply on Mar 28, 2017 7:26 AM by mifo

    Murata 1DX EVK with Sabre quad board WiFi nvram issue

    usman_1902851

      I am having some issues bringing the WiFi up using the Murata 1DX EVK with the Sabre Board Android 5.1.1 BSP. Bluetooth is working. WiFi is not.

      Contents of my /etc/firmware/bcm directory:

      BCM43430A1.1DX.hcd

      bcmdhd.1DX.SDIO.cal

      fw_bcmdhd.bin

       

      The hcd file makes the Bluetooth work. The wifi nvram is not getting loaded properly though (I have attached dmesg log)

       

      sdio_reset_comm():

      sdio_read_cis: 2 callbacks suppressed

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

      F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x1 pkg:0x3

      DHD: dongle ram size is set to 524288(orig 524288) at 0x0

      _dhdsdio_download_firmware: dongle nvram file download failed

      dhd_net_bus_devreset: dhd_bus_devreset: -35

      dhd_open : wl_android_wifi_on failed (-35)

       

      Does anyone know what might cause this?

        • 2. Re: Murata 1DX EVK with Sabre quad board WiFi nvram issue
          ghouse

          usman_1902851 Can you share the picture of your setup? Are you using the imagefiles downloaded from the NXP site as is?

          • 3. Re: Murata 1DX EVK with Sabre quad board WiFi nvram issue
            usman_1902851

            ghouse, my apologies for the late reply. Yes, I am using the default images from the NXP website. I followed the guide provided on the Murata website which asked to download kernel images and extract firmware files for the BCM chip. The setup is just a quad sabre board with the 1DX EVK. The sabre board has been reworked in accordance with the Murata guide. 3.jpgIMG_20170221_100129.jpg

            • 4. Re: Murata 1DX EVK with Sabre quad board WiFi nvram issue
              ghouse

              usman_1902851 Did you follow the steps for replacing the files since the device you are using is 1DX. The images by default are built for Type ZP.  The steps are in section 6 and files are in Table 6. Android user guide

              • 5. Re: Murata 1DX EVK with Sabre quad board WiFi nvram issue
                usman_1902851

                Yes, the files were replaced with the ones for Type 1DX. The bluetooth is functional because of this, but the nvram file is not getting loaded.

                 

                 

                 

                root@sabresd_6dq:/etc/firmware/bcm # ls

                 

                BCM43430A1.1DX.hcd

                bcmdhd.cal

                fw_bcmdhd.bin

                 

                 

                • 6. Re: Murata 1DX EVK with Sabre quad board WiFi nvram issue
                  skerr_1713761

                  What version of Android is being used? I think NXP team may have changed file naming convention.  On the first release (NXP Android 5.1.1 Lollipop GA BSP) supporting Murata Wi-Fi/BT EVK, the default naming for Type ZP module was:

                   

                  /etc/firmware/bcm/bcmdhd.cal

                  /etc/firmware/bcm/fw_bcmdhd.bin

                  /etc/firmware/bcm/fw_bcmdhd_apsta.bin

                  /etc/firmware/bcm/Type_ZP.hcd

                   

                  The failure is definitely due to path/filename issue. Unlike Linux, the Android software specifically names the HCD file (instead of reading Bluetooth core for an ID string). Thus the need for Type_ZP.hcd filename.

                   

                  Prior to file modifications, do you know what filenames were in the "/etc/firmware/bcm" folder?

                  1 of 1 people found this helpful
                  • 7. Re: Murata 1DX EVK with Sabre quad board WiFi nvram issue
                    usman_1902851

                    skerr_1713761

                    I reflashed the board with the 5.1.1 firmware to start fresh. Then I got the firmware files from the L3.14.52_1.1.0-ga_images_MX6UL Linux images and renamed them to match the old files. WiFi still behaves the same way, nvram is not loading successfully. Just to make sure I am using the correct files, I am attaching the MD5 hashes of all the files in the firmware folder and the backup folder as well.

                     

                    New files that were copied over from L3.14.52_1.1.0-ga_images_MX6UL.tar.gz:

                    root@sabresd_6dq:/etc/firmware/bcm # busybox md5sum ./*

                    00b4a75a3bc247f96eb07f12b28dd061  ./Type_ZP.hcd

                    ec9004a2832a9a417c5b730ca64a6603  ./bcmdhd.cal

                    0b222bc301f5df4365bfd90233e3421e  ./fw_bcmdhd.bin

                    0b222bc301f5df4365bfd90233e3421e  ./fw_bcmdhd_apsta.bin

                     

                    Old files that are now in backup folder:

                    root@sabresd_6dq:/etc/firmware/bcm # busybox md5sum ./Type_ZP_Backup/*                                              <

                    66154ac0796cd5aee6171e8878912788  ./Type_ZP_Backup/Type_ZP.hcd

                    f1d89ec0a22c12aef01e2ad45c91d9dd  ./Type_ZP_Backup/bcmdhd.cal

                    c3e83aa0b863ef2f4909d04977667dc3  ./Type_ZP_Backup/fw_bcmdhd.bin

                    42bbf2415c7990f2367556444f0a70da  ./Type_ZP_Backup/fw_bcmdhd_apsta.bin

                    root@sabresd_6dq:/etc/firmware/bcm #

                     

                    Dmesg output when wifi radio button is turned to ON in Android settings:

                    Dongle Host Driver, version 1.141.72 (r)

                    Compiled from

                    wl_android_wifi_on in

                    sdio_reset_comm():

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

                    mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

                    mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

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

                    F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x1 pkg:0x3

                    DHD: dongle ram size is set to 524288(orig 524288) at 0x0

                    _dhdsdio_download_firmware: dongle image file download failed

                    dhd_net_bus_devreset: dhd_bus_devreset: -35

                    dhd_open : wl_android_wifi_on failed (-35)

                    wl_android_wifi_off in

                    dhd_prot_ioctl : bus is down. we have nothing to do

                    dhd_net_bus_devreset: dhd_bus_devreset: -35

                    dhd_wlfc_deinit():3253, Already disabled!

                    dhd_detach(): thread:dhd_watchdog_thread:500 terminated OK

                    dhd_dpc_thread: Unexpected up_cnt 0

                    dhd_detach(): thread:dhd_dpc:501 terminated OK

                    CFG80211-ERROR) wl_event_handler : was terminated

                    wl_destroy_event_handler(): thread:wl_event_handler:4ff terminated OK

                    unregister wifi platform drivers

                    cfg80211: Calling CRDA to update world regulatory domain

                    dhd_module_init in

                    Power-up adapter 'DHD generic adapter'

                    dummy_sdmmc: probe of mmc1:0001:1 failed with error -110

                    dummy_sdmmc: probe of mmc1:0001:2 failed with error -110

                    wifi_platform_bus_enumerate device present 1

                    mmc1: card 0001 removed

                    sdio_read_cis: 2 callbacks suppressed

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

                    mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

                    mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

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

                    mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

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

                    mmc1: new high speed SDIO card at address 0001

                    F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x1 pkg:0x3

                    DHD: dongle ram size is set to 524288(orig 524288) at 0x0

                    wifi_platform_get_mac_addr

                    CFG80211-ERROR) wl_setup_wiphy : Registering Vendor80211)

                    wl_create_event_handler(): thread:wl_event_handler:517 started

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

                    dhd_attach(): thread:dhd_watchdog_thread:518 started

                    dhd_attach(): thread:dhd_dpc:519 started

                    dhd_deferred_work_init: work queue initialized

                     

                     

                    Dongle Host Driver, version 1.141.72 (r)

                    Compiled from

                    Register interface [wlan0]  MAC: 00:90:4c:11:22:33

                     

                     

                    dhd_prot_ioctl : bus is down. we have nothing to do

                     

                     

                     

                     

                    Dongle Host Driver, version 1.141.72 (r)

                    Compiled from

                    wl_android_wifi_on in

                    sdio_reset_comm():

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

                    mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

                    mmc1: queuing unknown CIS tuple 0x80 (3 bytes)

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

                    F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x1 pkg:0x3

                    DHD: dongle ram size is set to 524288(orig 524288) at 0x0

                    _dhdsdio_download_firmware: dongle image file download failed

                    dhd_net_bus_devreset: dhd_bus_devreset: -35

                    dhd_open : wl_android_wifi_on failed (-35)

                    wl_android_wifi_off in

                    dhd_prot_ioctl : bus is down. we have nothing to do

                    dhd_net_bus_devreset: dhd_bus_devreset: -35

                    PU: Power-on latency exceeded, new value 2363000 ns

                    • 8. Re: Murata 1DX EVK with Sabre quad board WiFi nvram issue
                      jersey.yang_2296731

                      _dhdsdio_download_firmware: dongle image file download failed

                       

                      this indicates your board downloading the firmware failed. if you use the built-in bcmdhd driver(intergrate the bcmdhd driver into the zImage),

                       

                      you must specify the nvram_path and firmware_path before you bring up the wlan0, no matter bring up

                       

                      the wlan0 automatically or manually.

                       

                       

                      echo /lib/firmware/bcm/1DX_BCM4343W/fw_bcmdhd_apsta.bin > /sys/module/bcmdhd/parameters/firmware_path
                      echo /lib/firmware/bcm/1DX_BCM4343W/bcmdhd.1DX.SDIO.cal > /sys/module/bcmdhd/parameters/nvram_path

                       

                      if you insmod the bcmdhd.ko manually, you also need to specify the path as insmod command's parameter

                       

                      like this:

                       

                      insmod /home/root/bcmdhd.ko firmware_path=/lib/firmware/bcm/fw_bcmdhd_apsta.bin nvram_path=/lib/firmware/bcm/bcmdhd.cal

                       

                      the cal and bin files path should be correct when loading the 1DX's firmware.