All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Bidkar <vikram.bidkar@sasken.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: [Yacto Project] Issue with Implementation of "Wi-Fi Access Point" on IMX7
Date: Mon, 10 Jul 2017 05:06:33 +0000	[thread overview]
Message-ID: <0BEBF42667D48548BAC1D4F202E2273F4E0766EA@exgmbxfz01.sasken.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2607 bytes --]

Dear All,

I am trying to implement "Wi-Fi Access Point" on the IMX7 evaluation board having Murata Wi-Fi chip(LBEH5HMZPC).

Below are my changes in .config file.

CONFIG_BCMDHD_FW_PATH="/lib/firmware/bcm/ZP_BCM4339/fw_bcmdhd_apsta.bin"
CONFIG_BCMDHD_NVRAM_PATH="/lib/firmware/bcm/ZP_BCM4339/bcmdhd.ZP.SDIO.cal"

CONFIG_HOSTAP=y
CONFIG_HOSTAP_FIRMWARE=y

but when I do "ifconfig wlan0 up" I am getting following error

root@imx7dsabresd:~# ifconfig wlan0 up

Dongle Host Driver, version 1.141.92 (r)
Compiled in drivers/net/wireless/bcmdhd
wl_android_wifi_on in
mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
mmc1: 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
dhd_bus_init: enable 0x06, ready 0x06 (waited 0us)
dhd_bus_rxctl: resumed on timeout, INT status=0x208000C0
dhd_bus_rxctl: rxcnt_timeout=1, rxlen=0
dhd_check_hang: Event HANG send up due to re=1 te=0 e=-110 s=2
dhd_open : wl_android_wifi_on failed (-14)

What could be the issue?
Note: Wi-Fi is working fine in client mode. It can able to scan and all.

possible issue may be

1) I think I have missed some patches as mentioned in the document (http://www.nxp.com/docs/en/application-note/AN5414.pdf)
Can I get the patches as mentioned in ("section :2 Prepare source code for applying Wi-Fi patches" from doc http://www.nxp.com/docs/en/application-note/AN5414.pdf )


Please help me to resolve the issue

Thanks and Regards,
Vikram

________________________________

SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Technologies Limited ( formerly known as "Sasken Communication Technologies Limited" ) unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
Read Disclaimer at http://www.sasken.com/mail-disclaimer/

________________________________

[-- Attachment #2: Type: text/html, Size: 6876 bytes --]

             reply	other threads:[~2017-07-10  5:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10  5:06 Vikram Bidkar [this message]
2017-07-11 13:39 ` [Yacto Project] Issue with Implementation of "Wi-Fi Access Point" on IMX7 Daiane Angolini

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=0BEBF42667D48548BAC1D4F202E2273F4E0766EA@exgmbxfz01.sasken.com \
    --to=vikram.bidkar@sasken.com \
    --cc=meta-freescale@yoctoproject.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: link
Be 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.