archive mirror
 help / color / mirror / Atom feed
From: Logan Gunthorpe <>
To: Luciano Coelho <>
Subject: RE: wl1271 firmware
Date: Fri, 09 Jul 2010 18:19:44 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: 1278578525.8576.19.camel@chilepepper

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. (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
( 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.



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.

             reply	other threads:[~2010-07-10  0:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10  0:19 Logan Gunthorpe [this message]
2010-07-11  5:38 ` wl1271 firmware Levi, Shahar
2010-07-12  5:35   ` Logan Gunthorpe
2010-07-16 21:41   ` Pazzo Da Legare
2010-07-17 12:20     ` Levi, Shahar
     [not found]       ` <>
     [not found]         ` <>
2010-07-21 17:01           ` Pazzo Da Legare
2010-07-21 17:27             ` Pazzo Da Legare
2010-07-22  6:40               ` Luciano Coelho
2010-07-22 15:41                 ` Pazzo Da Legare
2010-07-22 16:34                   ` Luciano Coelho
2010-07-23 23:19                     ` Pazzo Da Legare
2010-07-31 13:23                       ` Kalle Valo
  -- strict thread matches above, loose matches on Subject: below --
2010-06-30 11:26 Pazzo Da Legare
2010-06-30 13:42 ` Levi, Shahar
2010-07-01  7:36   ` Pazzo Da Legare
2010-07-02  9:47   ` max
2010-07-02  9:54   ` mastupristi
2010-07-05  7:36   ` Pazzo Da Legare
2010-07-05 16:49     ` Pazzo Da Legare
2010-07-06 12:28       ` Levi, Shahar
2010-07-08  8:42         ` Luciano Coelho
2010-07-06 11:55     ` Levi, Shahar

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).