From: Arend van Spriel <arend@broadcom.com> To: John Tobias <john.tobias.ph@gmail.com> Cc: "<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>, "<linux-arm-kernel@lists.infradead.org>" <linux-arm-kernel@lists.infradead.org>, Fabio Estevam <festevam@gmail.com>, Aisheng Dong <Aisheng.Dong@freescale.com>, Shawn Guo <shawn.guo@linaro.org>, <ryeh@broadcom.com>, <eccopark@broadcom.com>, <dimitrysh@google.com> Subject: Re: Broadcom 43340 module on iMX6DL Date: Thu, 23 Apr 2015 20:39:01 +0200 [thread overview] Message-ID: <55393C45.3060105@broadcom.com> (raw) In-Reply-To: <CACUGKYMXr3ASbB9fCk+GBnpfMC1kf_+NxDsOF_FODBKRAN9YvQ@mail.gmail.com> 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@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
WARNING: multiple messages have this Message-ID (diff)
From: arend@broadcom.com (Arend van Spriel) To: linux-arm-kernel@lists.infradead.org Subject: Broadcom 43340 module on iMX6DL Date: Thu, 23 Apr 2015 20:39:01 +0200 [thread overview] Message-ID: <55393C45.3060105@broadcom.com> (raw) In-Reply-To: <CACUGKYMXr3ASbB9fCk+GBnpfMC1kf_+NxDsOF_FODBKRAN9YvQ@mail.gmail.com> 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 at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-04-23 18:39 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-23 18:10 Broadcom 43340 module on iMX6DL John Tobias 2015-04-23 18:10 ` John Tobias 2015-04-23 18:19 ` Dmitry Shmidt 2015-04-23 18:19 ` Dmitry Shmidt 2015-04-23 18:39 ` Arend van Spriel [this message] 2015-04-23 18:39 ` Arend van Spriel 2015-04-23 18:44 ` John Tobias 2015-04-23 18:44 ` John Tobias 2015-04-23 19:00 ` Arend van Spriel 2015-04-23 19:00 ` Arend van Spriel 2015-04-24 0:50 ` John Tobias 2015-04-24 0:50 ` John Tobias 2015-04-27 3:21 ` Dong Aisheng 2015-04-27 3:21 ` Dong Aisheng 2015-04-24 0:57 ` John Stultz 2015-04-24 0:57 ` John Stultz 2015-04-24 0:59 ` John Tobias 2015-04-24 0:59 ` John Tobias 2015-04-24 1:04 ` John Tobias 2015-04-24 1:04 ` John Tobias 2015-04-24 8:20 ` Arend van Spriel 2015-04-24 8:20 ` Arend van Spriel 2015-04-24 17:49 ` John Tobias 2015-04-24 17:49 ` John Tobias 2015-04-24 18:14 ` Arend van Spriel 2015-04-24 18:14 ` Arend van Spriel 2015-04-24 18:24 ` John Tobias 2015-04-24 18:24 ` John Tobias 2015-04-24 19:03 ` Arend van Spriel 2015-04-24 19:03 ` Arend van Spriel 2015-04-25 13:36 ` Arend van Spriel 2015-04-25 13:36 ` Arend van Spriel 2015-04-27 3:27 ` Dong Aisheng 2015-04-27 3:27 ` Dong Aisheng 2015-04-27 3:33 ` Dong Aisheng 2015-04-27 3:33 ` Dong Aisheng 2015-04-27 7:17 ` John Tobias 2015-04-27 7:17 ` John Tobias 2015-04-24 8:38 ` Arend van Spriel 2015-04-24 8:38 ` Arend van Spriel
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=55393C45.3060105@broadcom.com \ --to=arend@broadcom.com \ --cc=Aisheng.Dong@freescale.com \ --cc=dimitrysh@google.com \ --cc=eccopark@broadcom.com \ --cc=festevam@gmail.com \ --cc=john.tobias.ph@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=ryeh@broadcom.com \ --cc=shawn.guo@linaro.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.