linux-kernel - Re: Broadcom 43340 module on iMX6DL

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <55393C45.3060105@broadcom.com>
Date:	Thu, 23 Apr 2015 20:39:01 +0200
From:	Arend van Spriel <arend@...adcom.com>
To:	John Tobias <john.tobias.ph@...il.com>
CC:	"<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>,
	"<linux-arm-kernel@...ts.infradead.org>" 
	<linux-arm-kernel@...ts.infradead.org>,
	Fabio Estevam <festevam@...il.com>,
	Aisheng Dong <Aisheng.Dong@...escale.com>,
	Shawn Guo <shawn.guo@...aro.org>, <ryeh@...adcom.com>,
	<eccopark@...adcom.com>, <dimitrysh@...gle.com>
Subject: Re: Broadcom 43340 module on iMX6DL

On 04/23/15 20:10, John Tobias wrote:
> Hello Guys,
>
> I am trying to use the bcmdhd wifi driver 43340 module on iMX6DL
> processor using kernel Freescale GA (3.10.53).
>
> I am having an issue with the sdio registration. I would like to know
> if anyone here had the same issue and how did you solve it?.
>
>
> Entry: wifi_add_dev
> Entry: wifi_add_dev
> Entry: wifi_probe
> wifi_probe: calling wifi_set_power on
> Entry: wifi_set_power
> wifi_set_power = 1
> wifi_set_carddetect = 1
> 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
>
> Dongle Host Driver, version 1.88.45 (r)
> Compiled in drivers/net/wireless/bcmdhd on Apr 23 2015 at 00:40:05
> F1 signature OK, socitype:0x1 chip:0xa94c rev:0x2 pkg:0x0
> DHD: dongle ram size is set to 524288(orig 524288) at 0x0
> wl_create_event_handler(): thread:wl_event_handler:3ba started
> CFG80211-ERROR) wl_event_handler : tsk Enter, tsk = 0x96741444
> dhd_attach(): thread:dhd_watchdog_thread:3bb started
> dhd_attach(): thread:dhd_dpc:3bc started
> dhd_attach(): thread:dhd_rxf:3bd started
> dhd_attach(): thread:dhd_sysioc:3be started
> wifi_get_mac_addr
> dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
>
>
> Times out here...
> dhd_module_init: sdio_register_driver timeout or error
>
> dhd_bus_init: enable 0x06, ready 0x02 (waited 3006383us)

This means it failed to enable function 2. My guess would be the 
firmware did not come up.

> dhd_bus_start failed bus is not ready
> dhdsdio_probe: dhd_bus_start failed
> dhd_detach(): thread:dhd_sysioc:3be terminated OK
> dhd_detach(): thread:dhd_watchdog_thread:3bb terminated OK
> dhd_dpc_thread: Unexpected up_cnt 0
> dhd_detach(): thread:dhd_dpc:3bc terminated OK
> dhd_detach(): thread:dhd_rxf:3bd terminated OK
> CFG80211-ERROR) wl_event_handler : was terminated
> wl_destroy_event_handler(): thread:wl_event_handler:3ba terminated OK
> dhd_osl_detach: MEMORY LEAK 156 bytes
> ## wifi_remove
> Entry: wifi_set_power
> wifi_set_power = 0
> navdy_wifi_power: 0
> wifi_set_carddetect = 0
> insmod: init_module '/system/lib/modules/bcmdhd.ko' failed (No such device)
> # mmc0: card 0001 removed
>
>
> Note: I ran the command below to load the driver:
> insmod /system/lib/modules/bcmdhd.ko
> firmware_path=/system/vendor/firmware/brcmfmac43340-sdio.bin
> nvram_path=/system/vendor/firmware/bcmdhd.cal

So this is an Android image, right? Can you do hexdump, ie.:

$ hexdump -C brcmfmac43340-sdio.bin | tail -30

Regards,
Arend

> Regards,
>
> John
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/