linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Vanessa Maegima <vanessa.maegima@nxp.com>,
	"festevam@gmail.com" <festevam@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"van.ayumi@gmail.com" <van.ayumi@gmail.com>,
	"embed3d@gmail.com" <embed3d@gmail.com>
Subject: Re: AP6335 with mainline kernel
Date: Fri, 19 Jan 2018 10:02:52 +0100	[thread overview]
Message-ID: <5A61B43C.4000305@broadcom.com> (raw)
In-Reply-To: <1516276016.8817.1.camel@nxp.com>

On 1/18/2018 12:47 PM, Vanessa Maegima wrote:
> Hi Arend,
>
> On Ter, 2018-01-16 at 21:21 +0100, Arend van Spriel wrote:
>> On 1/15/2018 9:08 PM, Fabio Estevam wrote:
>>>
>>> Hi Arend,
>>>
>>> On Tue, Dec 5, 2017 at 12:58 PM, Vanessa Maegima
>>> <vanessa.maegima@nxp.com> wrote:
>>>
>>>>
>>>> Hi Arend,
>>>>
>>>> Sorry for this!
>>>>
>>>> I updated the folder on https://emea01.safelinks.protection.outlo
>>>> ok.com/?url=https%3A%2F%2Fdrive.google.com%2Fdrive%2Ffolders%2F1f
>>>> osahjL&data=02%7C01%7Cvanessa.maegima%40nxp.com%7Cf07cd1a6ffb34c0
>>>> 961f608d55d1eb901%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C63
>>>> 6517308901643244&sdata=6JAqSN%2BVPJ%2FCF7cbnBjm8geMKWydWkG9JcUhGB
>>>> Pj644%3D&reserved=0
>>>> N1KI5NKS59_aPZdHLpENPFHtK
>>>>
>>>> Thanks!
>>> Any ideas, please?
>> Well, the dumps confirm a crash early in the firmware boot. However,
>> I
>> could not obtain more information from it. To capture the failure I
>> need
>> to rework some firmware functionality which is not trivial and I can
>> not
>> claim time for it right now.
>>
>> Regards,
>> Arend
>>
>
> Thanks for all your investigation here!
>
> I just want to report one more thing that I noticed from my tests.
>
> I have tried to use an html file that I downloaded using wget as the
> nvram file (https://github.com/OpenELEC/wlan-firmware/blob/master/firmw
> are/brcm/nvram_ap6335.txt) and the wifi seems to work. I have not
> noticed the wrong format file until testing it.

Interesting. In brcmfmac the file is parsed before sending it to the 
firmware so I am wondering what is effectively send to the device.

Can you dump the nvram that is sent to the device. Just add hexdump call 
of nvram in brcmf_fw_request_nvram_done() in firmware.c just before 
fwctx->done() is called.

Regards,
Arend

  reply	other threads:[~2018-01-19  9:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 19:33 AP6335 with mainline kernel Vanessa Ayumi Maegima
2017-09-21  7:26 ` Arend van Spriel
2017-09-21 15:30   ` Vanessa Ayumi Maegima
2017-10-17 12:07     ` Vanessa Maegima
2017-11-10 12:43     ` Vanessa Maegima
2017-11-10 19:58       ` Arend van Spriel
2017-11-17 11:08         ` Vanessa Maegima
2017-11-17 12:55           ` Arend van Spriel
2017-11-17 15:24             ` Vanessa Maegima
2017-11-20 11:03               ` Arend van Spriel
2017-11-20 11:12                 ` Arend van Spriel
2017-11-22 10:48                   ` Vanessa Maegima
2017-11-22 10:58                     ` Arend van Spriel
2017-11-23 15:24                       ` Vanessa Maegima
2017-11-30 12:31                         ` Arend van Spriel
2017-12-04 19:00                           ` Vanessa Maegima
2017-12-05  9:06                             ` Arend Van Spriel
2017-12-05 14:58                               ` Vanessa Maegima
2018-01-15 20:08                                 ` Fabio Estevam
2018-01-16 20:21                                   ` Arend van Spriel
2018-01-18 11:47                                     ` Vanessa Maegima
2018-01-19  9:02                                       ` Arend van Spriel [this message]
2018-03-21 15:38                                         ` Vanessa Maegima
2018-03-23  9:28                                           ` Arend van Spriel
2018-03-23 13:15                                             ` Vanessa Maegima
2018-03-26 12:25                                               ` Vanessa Maegima
2018-03-26 13:34                                                 ` Vanessa Maegima
2018-11-14 11:40                                                   ` Arend van Spriel
2018-11-15 17:04                                                     ` Vanessa Ayumi Maegima
     [not found]                                                       ` <CAHWfWzm8Zwjc2tBQWVqpaa-cMYyEPWmUKYN7rspyb9W9spx2iQ@mail.gmail.com>
2018-11-17 19:10                                                         ` Fabio Estevam
2018-11-28 15:59                                                           ` Fabio Estevam
     [not found]                                                             ` <CAF7Mx6p1DpRieCKy_1qOE5YT4_76UO8vhLMBFUD2B0FrQ9BJGw@mail.gmail.com>
2018-11-28 16:23                                                               ` Fabio Estevam
2018-11-28 18:08                                                                 ` Fabio Estevam
2018-11-28 20:13                                                                   ` Arend van Spriel
2018-11-29  0:12                                                                     ` Fabio Estevam

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=5A61B43C.4000305@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=embed3d@gmail.com \
    --cc=festevam@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=van.ayumi@gmail.com \
    --cc=vanessa.maegima@nxp.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).