Hi all,
I'm looking for wl1271 firmwares. I found wl1271-fw.bin but I cannot
find wl1271-nvs.bin needed to use the wl1271's driver.
Could you please indicate where I can get it?
Thank in advance,
pz
Hi pz,
I am checking the way to access the FW and NVS file of wl1271.
Let me find more details on that and get back to you.
Regards,
Shahar
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Pazzo Da Legare
Sent: Wednesday, June 30, 2010 2:27 PM
To: [email protected]
Subject: wl1271 firmware
Hi all,
I'm looking for wl1271 firmwares. I found wl1271-fw.bin but I cannot
find wl1271-nvs.bin needed to use the wl1271's driver.
Could you please indicate where I can get it?
Thank in advance,
pz
On Thu, 2010-07-22 at 17:41 +0200, ext Pazzo Da Legare wrote:
> I enabled the DEBUG_LEVEL as you advice me but I have no additional
> information....
>
> [ 186.230000] wl1271_sdio mmc0:0001:2: firmware: requesting
> wl1271-fw.bin
> [ 186.420000] wl1271_sdio mmc0:0001:2: firmware: requesting
> wl1271-nvs.bin
> [ 186.860000] wl1271: firmware booted (Rev 6.1.0.0.310)
> [ 186.880000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 187.380000] wl1271: ERROR ELP wakeup timeout!
> [ 187.880000] wl1271: ERROR ELP wakeup timeout!
There's something wrong. There should have been a lot more traces with
the DEBUG_LEVEL I proposed. Please try again.
--
Cheers,
Luca.
> -----Original Message-----
> From: [email protected] [mailto:linux-wireless-
> [email protected]] On Behalf Of Logan Gunthorpe
> Sent: Saturday, July 10, 2010 3:20 AM
> To: Luciano Coelho
> Cc: [email protected]
> Subject: RE: wl1271 firmware
>
> Hi Everyone,
>
> I too am working with a WL1271 module and have just today got it
> connected to an Atmel ARM9 development kit (AT91SAM9G45-EKES). So far it
> appears to work but I have been gated by the firmware and NVS file issues.
>
> I have a firmware binary, but it seems to be a newer version
> (6.1.3.01.5) than what you are using. Does anyone have any idea if this
> version will work? It seems to be the only one available on TI's
> website. Additionally, our device manufacturer has been hesitant to
> provide any support because we are on an unsupported platform and opted
> to use the open source driver. Are there any other ways to obtain an
> older version of the firmware?
>
> The NVS file is another problem. TI's website has instructions to use a
> cryptic tool that appears to come with their driver package. There is no
> source for this tool and for obvious reasons would not work for us.
>
> Anyway, I'd like to help in anyway I can. I've taken a look at the
> twilan.ini file and I see the commonality with wl1271_ini.h. It would be
> relatively easy to write a tool that parses the INI file and generates
> the common part of the NVS file. However, I'd have no idea how to
> generate the device specific calibration or the few fields missing from
> the INI file.
>
> Thanks,
>
> Logan
>
Hi Logan,
I am pushing to get access to the correct FW and NVS files version in TI web. I believe the community wills nave access of those files this week.
Regarding the tool to generate the NVS file in the correct format, I will check that and reply.
Regards,
Shahar
Hi Everyone,
Luciano Coelho Wrote:
> You need to get the firmware (wl1271-fw.bin) directly from TI or from
> your device manufacturer. I don't have the permission to redistribute
> it. The latest version that we are using is Rev. 6.1.0.0.310 (you can
> check this by running strings on and grepping the binary file).
>
> The NVS file is another story. It contains device-specific calibration
> values and you should probably get those from the device manufacturer.
> There is a common part (which is the INI file in tiwlan's terms), which
> you need to use to create the binary (check wl1271_ini.h for the binary
> file structure). The more problematic part is the device-specific self
> generated calibration. You need to run a specific sequence of commands
> in order to get these values and then apply these values to the correct
> place in the binary file.
>
> Shahar, maybe you could contribute a tool to generate the NVS file in
> the correct format for wl1271? That would be very cool and would help
> lots of people. Please let me know if you have interest and we can
> discuss this in more details.
I too am working with a WL1271 module and have just today got it
connected to an Atmel ARM9 development kit (AT91SAM9G45-EKES). So far it
appears to work but I have been gated by the firmware and NVS file issues.
I have a firmware binary, but it seems to be a newer version
(6.1.3.01.5) than what you are using. Does anyone have any idea if this
version will work? It seems to be the only one available on TI's
website. Additionally, our device manufacturer has been hesitant to
provide any support because we are on an unsupported platform and opted
to use the open source driver. Are there any other ways to obtain an
older version of the firmware?
The NVS file is another problem. TI's website has instructions to use a
cryptic tool that appears to come with their driver package. There is no
source for this tool and for obvious reasons would not work for us.
Anyway, I'd like to help in anyway I can. I've taken a look at the
twilan.ini file and I see the commonality with wl1271_ini.h. It would be
relatively easy to write a tool that parses the INI file and generates
the common part of the NVS file. However, I'd have no idea how to
generate the device specific calibration or the few fields missing from
the INI file.
Thanks,
Logan
P.S. I was not subscribed to this list when the message I'm replying to
was sent. I apologize if I broke the thread. I am subscribed now.
Levi, Shahar <shahar_levi@...> writes:
> I am checking the way to access the FW and NVS file of wl1271.
> Let me find more details on that and get back to you.
Hi I'm also searching for that file
Please let me know when it will be available
thanks
Hi Pazzo,
On Wed, 2010-07-21 at 19:27 +0200, ext Pazzo Da Legare wrote:
> Dear All again,
>
> I've just test with compact-wireless-2010-07-20 but I've the same problem:
>
> root@hawkboard:~# ifconfig wlan0 192.168.0.1 up
> [ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
> [ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
> [ 69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> root@hawkboard:~# [ 70.020000] wl1271: ERROR ELP wakeup timeout!
> [ 70.520000] wl1271: ERROR ELP wakeup timeout!
>
>
> looking at dmesg:
>
> [ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
> [ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
> [ 69.500000] wl1271: firmware booted (Rev 6.1.0.0.310)
> [ 69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 70.020000] wl1271: ERROR ELP wakeup timeout!
> [ 70.520000] wl1271: ERROR ELP wakeup timeout!
>
> [ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
> [ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
> [ 69.500000] wl1271: firmware booted (Rev 6.1.0.0.310)
> [ 70.020000] wl1271: ERROR ELP wakeup timeout!
> [ 70.520000] wl1271: ERROR ELP wakeup timeout!
>
> Do you have any clue?
I'm not sure what this is, but usually an ERROR ELP wakeup timeout means
that the firmware has crashed.
Could you enable the following DEBUG flags in wl1271.h and send the logs
again? Maybe they provide more clues...
#define DEBUG_LEVEL (DEBUG_BOOT | DEBUG_ACX | DEBUG_CMD | DEBUG_PSM | \
DEBUG_IRQ | DEBUG_EVENT)
--
Cheers,
Luca.
> I start from tiwlan.ini file for tiwlan driver to produce an nvs file.
> Could you please indicate values to use for the following parameters
> of struct wl1271_nvs_file: general_params.srf1[],
> general_params.srf2[], general_params.srf3[],
> dyn_radio_params_2[].params.degraded_low_to_normal_thr,
> dyn_radio_params_2[].params.normal_to_degraded_high_thr,
> dyn_radio_params_5[i].params.degraded_low_to_normal_thr,
> dyn_radio_params_5[i].params.normal_to_degraded_high_thr
Hi,
The tiwlan driver ini&NVS files has a different stature then the mac80211 NVS. The parameters you mentioned are RF parameters.
I believe it will be the best to get the NVS that mach to the mac80211 (that I am pushing to get).
Regards,
Shahar
Shahar,
Excellent news.
Thank you very much.
Logan
Levi, Shahar wrote:
>> -----Original Message-----
>> From: [email protected] [mailto:linux-wireless-
>> [email protected]] On Behalf Of Logan Gunthorpe
>> Sent: Saturday, July 10, 2010 3:20 AM
>> To: Luciano Coelho
>> Cc: [email protected]
>> Subject: RE: wl1271 firmware
>>
>> Hi Everyone,
>>
>> I too am working with a WL1271 module and have just today got it
>> connected to an Atmel ARM9 development kit (AT91SAM9G45-EKES). So far it
>> appears to work but I have been gated by the firmware and NVS file issues.
>>
>> I have a firmware binary, but it seems to be a newer version
>> (6.1.3.01.5) than what you are using. Does anyone have any idea if this
>> version will work? It seems to be the only one available on TI's
>> website. Additionally, our device manufacturer has been hesitant to
>> provide any support because we are on an unsupported platform and opted
>> to use the open source driver. Are there any other ways to obtain an
>> older version of the firmware?
>>
>> The NVS file is another problem. TI's website has instructions to use a
>> cryptic tool that appears to come with their driver package. There is no
>> source for this tool and for obvious reasons would not work for us.
>>
>> Anyway, I'd like to help in anyway I can. I've taken a look at the
>> twilan.ini file and I see the commonality with wl1271_ini.h. It would be
>> relatively easy to write a tool that parses the INI file and generates
>> the common part of the NVS file. However, I'd have no idea how to
>> generate the device specific calibration or the few fields missing from
>> the INI file.
>>
>> Thanks,
>>
>> Logan
>>
>
> Hi Logan,
> I am pushing to get access to the correct FW and NVS files version in TI web. I believe the community wills nave access of those files this week.
> Regarding the tool to generate the NVS file in the correct format, I will check that and reply.
> Regards,
> Shahar
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Shahar,
Thank you for your help!
pz
2010/6/30 Levi, Shahar <[email protected]>:
> Hi pz,
> I am checking the way to access the FW and NVS file of wl1271.
> Let me find more details on that and get back to you.
> Regards,
> Shahar
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Pazzo Da Legare
> Sent: Wednesday, June 30, 2010 2:27 PM
> To: [email protected]
> Subject: wl1271 firmware
>
> Hi all,
>
> I'm looking for wl1271 firmwares. I found wl1271-fw.bin but I cannot
> find wl1271-nvs.bin needed to use the wl1271's driver.
> Could you please indicate where I can get it?
>
> Thank in advance,
>
> pz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
Levi, Shahar <shahar_levi@...> writes:
> Hi pz,
> I am checking the way to access the FW and NVS file of wl1271.
> Let me find more details on that and get back to you.
Hi all,
I have the same problem searching wl1271-nvs.bin.
I hope that it will be possible to find it.
Please I would like to have your feedback
best regards,
bye
Dear Shahar,
Thank you for your help and the news. Could you please indicate a link
when available?
Pz
2010/7/11, Levi, Shahar <[email protected]>:
>> -----Original Message-----
>> From: [email protected] [mailto:linux-wireless-
>> [email protected]] On Behalf Of Logan Gunthorpe
>> Sent: Saturday, July 10, 2010 3:20 AM
>> To: Luciano Coelho
>> Cc: [email protected]
>> Subject: RE: wl1271 firmware
>>
>> Hi Everyone,
>>
>> I too am working with a WL1271 module and have just today got it
>> connected to an Atmel ARM9 development kit (AT91SAM9G45-EKES). So far it
>> appears to work but I have been gated by the firmware and NVS file issues.
>>
>> I have a firmware binary, but it seems to be a newer version
>> (6.1.3.01.5) than what you are using. Does anyone have any idea if this
>> version will work? It seems to be the only one available on TI's
>> website. Additionally, our device manufacturer has been hesitant to
>> provide any support because we are on an unsupported platform and opted
>> to use the open source driver. Are there any other ways to obtain an
>> older version of the firmware?
>>
>> The NVS file is another problem. TI's website has instructions to use a
>> cryptic tool that appears to come with their driver package. There is no
>> source for this tool and for obvious reasons would not work for us.
>>
>> Anyway, I'd like to help in anyway I can. I've taken a look at the
>> twilan.ini file and I see the commonality with wl1271_ini.h. It would be
>> relatively easy to write a tool that parses the INI file and generates
>> the common part of the NVS file. However, I'd have no idea how to
>> generate the device specific calibration or the few fields missing from
>> the INI file.
>>
>> Thanks,
>>
>> Logan
>>
>
> Hi Logan,
> I am pushing to get access to the correct FW and NVS files version in TI
> web. I believe the community wills nave access of those files this week.
> Regarding the tool to generate the NVS file in the correct format, I will
> check that and reply.
> Regards,
> Shahar
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Inviato dal mio dispositivo mobile
Dear All,
Dear Shahar,
I tried your files but I had errors from the driver.
# ifconfig wlan0 up
[ 194.470000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
[ 194.620000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
[ 195.080000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
root@hawkboard:~# [ 195.590000] wl1271: ERROR ELP wakeup timeout!
I tried to scan but it doesn't work. Note that I'm using a driver
built from compact-wireless-2010-06-20 and I'm going to try to update.
Thank you for your help again,
pz
2010/7/20 Logan Gunthorpe <[email protected]>:
> Hi Sharar,
>
> Thanks a lot. I'm pleased to report that our module appears to be working
> with the firmware and NVS files you supplied.
>
> Logan
>
> Levi, Shahar wrote:
>>>
>>> -----Original Message-----
>>> From: Levi, Shahar
>>> Sent: Saturday, July 17, 2010 3:20 PM
>>> To: Pazzo Da Legare
>>> Cc: [email protected]; Logan Gunthorpe; Luciano Coelho
>>> Subject: RE: wl1271 firmware
>>> Hi Pazzo,
>>> I am still pushing the legal stuff to make it happened. I hope to close
>>> that in a few days.
>>> Regards,
>>> Shahar
>>
>> Hi Pazzo and Logan,
>> Until the file will publish in TI web I am enclosing the file for you in
>> the mail.
>> I will publish link to the community as soon it will be in the TI web.
>>
>> Regards,
>> Shahar
>>
>
Dear Luciano,
Dear All,
I enabled the DEBUG_LEVEL as you advice me but I have no additional
information....
[ 186.230000] wl1271_sdio mmc0:0001:2: firmware: requesting
wl1271-fw.bin
[ 186.420000] wl1271_sdio mmc0:0001:2: firmware: requesting
wl1271-nvs.bin
[ 186.860000] wl1271: firmware booted (Rev 6.1.0.0.310)
[ 186.880000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 187.380000] wl1271: ERROR ELP wakeup timeout!
[ 187.880000] wl1271: ERROR ELP wakeup timeout!
Pazzo
2010/7/22 Luciano Coelho <[email protected]>:
> Hi Pazzo,
>
>
> On Wed, 2010-07-21 at 19:27 +0200, ext Pazzo Da Legare wrote:
>> Dear All again,
>>
>> I've just test with compact-wireless-2010-07-20 but I've the same problem:
>>
>> root@hawkboard:~# ifconfig wlan0 192.168.0.1 up
>> [ ? 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
>> [ ? 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
>> [ ? 69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> root@hawkboard:~# [ ? 70.020000] wl1271: ERROR ELP wakeup timeout!
>> [ ? 70.520000] wl1271: ERROR ELP wakeup timeout!
>>
>>
>> looking at dmesg:
>>
>> [ ?68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
>> [ ? 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
>> [ ? 69.500000] wl1271: firmware booted (Rev 6.1.0.0.310)
>> [ ? 69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [ ? 70.020000] wl1271: ERROR ELP wakeup timeout!
>> [ ? 70.520000] wl1271: ERROR ELP wakeup timeout!
>>
>> [ ? 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
>> [ ? 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
>> [ ? 69.500000] wl1271: firmware booted (Rev 6.1.0.0.310)
>> [ ? 70.020000] wl1271: ERROR ELP wakeup timeout!
>> [ ? 70.520000] wl1271: ERROR ELP wakeup timeout!
>>
>> Do you have any clue?
>
> I'm not sure what this is, but usually an ERROR ELP wakeup timeout means
> that the firmware has crashed.
>
> Could you enable the following DEBUG flags in wl1271.h and send the logs
> again? Maybe they provide more clues...
>
> #define DEBUG_LEVEL (DEBUG_BOOT | DEBUG_ACX | DEBUG_CMD | DEBUG_PSM | \
> ? ? ? ? ? ? ? ? ? ? DEBUG_IRQ | DEBUG_EVENT)
>
>
> --
> Cheers,
> Luca.
>
>
Dear All again,
I've just test with compact-wireless-2010-07-20 but I've the same problem:
root@hawkboard:~# ifconfig wlan0 192.168.0.1 up
[ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
[ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
[ 69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
root@hawkboard:~# [ 70.020000] wl1271: ERROR ELP wakeup timeout!
[ 70.520000] wl1271: ERROR ELP wakeup timeout!
looking at dmesg:
[ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
[ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
[ 69.500000] wl1271: firmware booted (Rev 6.1.0.0.310)
[ 69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 70.020000] wl1271: ERROR ELP wakeup timeout!
[ 70.520000] wl1271: ERROR ELP wakeup timeout!
[ 68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
[ 69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
[ 69.500000] wl1271: firmware booted (Rev 6.1.0.0.310)
[ 70.020000] wl1271: ERROR ELP wakeup timeout!
[ 70.520000] wl1271: ERROR ELP wakeup timeout!
Do you have any clue?
pz
2010/7/21 Pazzo Da Legare <[email protected]>:
> Dear All,
> Dear Shahar,
>
> I tried your files but I had errors from the driver.
>
> # ifconfig wlan0 up
>
> [ ?194.470000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
> [ ?194.620000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
> [ ?195.080000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> root@hawkboard:~# [ ?195.590000] wl1271: ERROR ELP wakeup timeout!
>
> I tried to scan but it doesn't work. Note that I'm using a driver
> built from compact-wireless-2010-06-20 and I'm going to try to update.
>
> Thank you for your help again,
>
> pz
>
>
> 2010/7/20 Logan Gunthorpe <[email protected]>:
>> Hi Sharar,
>>
>> Thanks a lot. I'm pleased to report that our module appears to be working
>> with the firmware and NVS files you supplied.
>>
>> Logan
>>
>> Levi, Shahar wrote:
>>>>
>>>> -----Original Message-----
>>>> From: Levi, Shahar
>>>> Sent: Saturday, July 17, 2010 3:20 PM
>>>> To: Pazzo Da Legare
>>>> Cc: [email protected]; Logan Gunthorpe; Luciano Coelho
>>>> Subject: RE: wl1271 firmware
>>>> Hi Pazzo,
>>>> I am still pushing the legal stuff to make it happened. I hope to close
>>>> that in a few days.
>>>> Regards,
>>>> Shahar
>>>
>>> Hi Pazzo and Logan,
>>> Until the file will publish in TI web I am enclosing the file for you in
>>> the mail.
>>> I will publish link to the community as soon it will be in the TI web.
>>>
>>> Regards,
>>> Shahar
>>>
>>
>
Hi Shahar,
Did you have any news about nvs file? I wrote an email to driver's
mantaneir too,
Thank you in advance,
pz
2010/6/30 Levi, Shahar <[email protected]>:
> Hi pz,
> I am checking the way to access the FW and NVS file of wl1271.
> Let me find more details on that and get back to you.
> Regards,
> Shahar
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Pazzo Da Legare
> Sent: Wednesday, June 30, 2010 2:27 PM
> To: [email protected]
> Subject: wl1271 firmware
>
> Hi all,
>
> I'm looking for wl1271 firmwares. I found wl1271-fw.bin but I cannot
> find wl1271-nvs.bin needed to use the wl1271's driver.
> Could you please indicate where I can get it?
>
> Thank in advance,
>
> pz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
> -----Original Message-----
> From: Pazzo Da Legare [mailto:[email protected]]
> Sent: Saturday, July 17, 2010 12:41 AM
> To: Levi, Shahar; Logan Gunthorpe; Luciano Coelho; linux-
> [email protected]
> Subject: Re: wl1271 firmware
>
> Dear Shahar,
> Thank you for your help and the news. Could you please indicate a link
> when available?
> Pz
>
Hi Pazzo,
I am still pushing the legal stuff to make it happened. I hope to close that in a few days.
Regards,
Shahar
Dear Luciano,
Obviously you are right: I did a stupid error (I modified wrong
wl1271.h file, the one for and older compact-wireless...), sorry for
that.
I attached what I got. Note that I have a limited buffer for system
log so this is the last part only, I hope is enough.
http://pastebin.com/7nLJeXkb
Thank you again,
pz
2010/7/22 Luciano Coelho <[email protected]>:
> On Thu, 2010-07-22 at 17:41 +0200, ext Pazzo Da Legare wrote:
>> I enabled the DEBUG_LEVEL as you advice me but I have no additional
>> information....
>>
>> [ ?186.230000] wl1271_sdio mmc0:0001:2: firmware: requesting
>> wl1271-fw.bin
>> [ ?186.420000] wl1271_sdio mmc0:0001:2: firmware: requesting
>> wl1271-nvs.bin
>> [ ?186.860000] wl1271: firmware booted (Rev 6.1.0.0.310)
>> [ ?186.880000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [ ?187.380000] wl1271: ERROR ELP wakeup timeout!
>> [ ?187.880000] wl1271: ERROR ELP wakeup timeout!
>
> There's something wrong. ?There should have been a lot more traces with
> the DEBUG_LEVEL I proposed. ?Please try again.
>
>
> --
> Cheers,
> Luca.
>
>
> Did you have any news about nvs file? I wrote an email to driver's
> mantaneir too,
Hi,
Still pushing to get access to the files it TI. I hope I will have something e\o the week.
Regards,
Shahar
Dear Shahar,
I start from tiwlan.ini file for tiwlan driver to produce an nvs file.
Could you please indicate values to use for the following parameters
of struct wl1271_nvs_file: general_params.srf1[],
general_params.srf2[], general_params.srf3[],
dyn_radio_params_2[].params.degraded_low_to_normal_thr,
dyn_radio_params_2[].params.normal_to_degraded_high_thr,
dyn_radio_params_5[i].params.degraded_low_to_normal_thr,
dyn_radio_params_5[i].params.normal_to_degraded_high_thr
Thank you very much for your time,
Best Regards,
pz
2010/7/5 Pazzo Da Legare <[email protected]>:
> Hi Shahar,
>
> Did you have any news about nvs file? I wrote an email to driver's
> mantaneir too,
>
> Thank you in advance,
>
> pz
>
> 2010/6/30 Levi, Shahar <[email protected]>:
>> Hi pz,
>> I am checking the way to access the FW and NVS file of wl1271.
>> Let me find more details on that and get back to you.
>> Regards,
>> Shahar
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On Behalf Of Pazzo Da Legare
>> Sent: Wednesday, June 30, 2010 2:27 PM
>> To: [email protected]
>> Subject: wl1271 firmware
>>
>> Hi all,
>>
>> I'm looking for wl1271 firmwares. I found wl1271-fw.bin but I cannot
>> find wl1271-nvs.bin needed to use the wl1271's driver.
>> Could you please indicate where I can get it?
>>
>> Thank in advance,
>>
>> pz
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>>
>
Pazzo Da Legare <[email protected]> writes:
> I attached what I got. Note that I have a limited buffer for system
> log so this is the last part only, I hope is enough.
>
> http://pastebin.com/7nLJeXkb
wl1271 sdio needs a special SDIO command to wakeup the firmware
properly from ELP. I recommend to check that your platform is using
that.
--
Kalle Valo
Hi,
On Tue, 2010-07-06 at 14:28 +0200, ext Levi, Shahar wrote:
> > I start from tiwlan.ini file for tiwlan driver to produce an nvs file.
> > Could you please indicate values to use for the following parameters
> > of struct wl1271_nvs_file: general_params.srf1[],
> > general_params.srf2[], general_params.srf3[],
> > dyn_radio_params_2[].params.degraded_low_to_normal_thr,
> > dyn_radio_params_2[].params.normal_to_degraded_high_thr,
> > dyn_radio_params_5[i].params.degraded_low_to_normal_thr,
> > dyn_radio_params_5[i].params.normal_to_degraded_high_thr
>
> Hi,
> The tiwlan driver ini&NVS files has a different stature then the mac80211 NVS. The parameters you mentioned are RF parameters.
> I believe it will be the best to get the NVS that mach to the mac80211 (that I am pushing to get).
> Regards,
> Shahar
You need to get the firmware (wl1271-fw.bin) directly from TI or from
your device manufacturer. I don't have the permission to redistribute
it. The latest version that we are using is Rev. 6.1.0.0.310 (you can
check this by running strings on and grepping the binary file).
The NVS file is another story. It contains device-specific calibration
values and you should probably get those from the device manufacturer.
There is a common part (which is the INI file in tiwlan's terms), which
you need to use to create the binary (check wl1271_ini.h for the binary
file structure). The more problematic part is the device-specific self
generated calibration. You need to run a specific sequence of commands
in order to get these values and then apply these values to the correct
place in the binary file.
Shahar, maybe you could contribute a tool to generate the NVS file in
the correct format for wl1271? That would be very cool and would help
lots of people. Please let me know if you have interest and we can
discuss this in more details.
--
Cheers,
Luca.