Hi Arend, On Sex, 2018-01-19 at 10:02 +0100, Arend van Spriel wrote: > 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@xxxxxxx> wrote: > > > > > > > > > > > > > > > > > > > Hi Arend, > > > > > > > > > > Sorry for this! > > > > > > > > > > I updated the folder on https://emea01.safelinks.protection.o > > > > > utlook.com/?url=https%3A%2F%2Femea01.safelinks.protection.out > > > > > lo&data=02%7C01%7Cvanessa.maegima%40nxp.com%7C39040229475441d > > > > > 7b5aa08d55f1b6cd3%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1% > > > > > 7C636519493755298348&sdata=Zws4AElm4La96Q4pjK152nH2lP6v4mPJJN > > > > > xSGz7TLBA%3D&reserved=0 > > > > > ok.com/?url=https%3A%2F%2Fdrive.google.com%2Fdrive%2Ffolders% > > > > > 2F1f > > > > > osahjL&data=02%7C01%7Cvanessa.maegima%40nxp.com%7Cf07cd1a6ffb > > > > > 34c0 > > > > > 961f608d55d1eb901%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0% > > > > > 7C63 > > > > > 6517308901643244&sdata=6JAqSN%2BVPJ%2FCF7cbnBjm8geMKWydWkG9Jc > > > > > UhGB > > > > > 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://emea01.safelinks.protection.outlook.com/?url=ht > > tps%3A%2F%2Fgithub.com%2FOpenELEC%2Fwlan- > > firmware%2Fblob%2Fmaster%2Ffirmw&data=02%7C01%7Cvanessa.maegima%40n > > xp.com%7C39040229475441d7b5aa08d55f1b6cd3%7C686ea1d3bc2b4c6fa92cd99 > > c5c301635%7C0%7C1%7C636519493755298348&sdata=EZFVV3qbStjH9Eqe6uVVXJ > > f7LmQlMLIURXHaQIMIpms%3D&reserved=0 > > 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 Sorry for my delayed response, but I could not get the hexdump from the nvram. I have tried several hexdump functions I found on kernel and on the brcmfmac driver but none of them printed any output. Is there any CONFIG I need to enable to get those working? Thanks! Best, Vanessa
