Kernel version 3.4 and earlier
To build the latest driver for your system see the script available here: WL12xx NLCP Build Instructions
After fetching the script be sure to change the version tag at the top of wl12xx_build.sh to the desired release version. At the time of this writing the latest version tag is "ol_R5.SP7.01".
After the driver is built and installed on the target system be sure to calibrate each module. Calibration ensures optimum RF performance as well and EMC compliance. If the module is not calibrated it will void all modular certifications. Be sure to use an INI file from the LSR website and follow the calibration instructions. The calibrator utility should have been downloaded and built with the driver script above. See here: WL12xx Calibration Steps
Kernel version 3.5 and later
The last official driver release for the WL12xx was based on kernel v3.2. There are no further releases planned for newer kernels. The WL12xx drivers are included in newer kernels but each kernel may have a different driver. This requires that the end user ensure the driver and firmware are correct for the WL12xx.
Here are some steps that LSR has put together for getting the WL12xx driver running in newer kernels. These steps were tested on kernel v3.12 for TI's AM335x.
Started with the LINUXEZSDK-AM335X here: http://www.ti.com/tool/LINUXEZSDK-SITARA
Diff here for the AM335X starter kit device tree file.
Four main changes go into this file:
- A new block for MMC2, which references a new pin mux table (wilink_pins) and a new regulator definition (vmmc_wl).
- The new pin mux table (wilink_pins) that configures the pinmux for the pins needed for the MMC2 bus.
- The new regulator definition (vmmc_wl). Most important thing here is to get the gpio setting correct, matching the WLAN_EN signal into the TiWi module.
- A new block for the wlcore. The gpio setting is important. It should be configured to the GPIO connected to the WLAN_IRQ. The platform-quirks setting may or may not be important. There is only a single bit used here, bit 0, which sets whether to use level or edge interrupts on the IRQ. The board-ref-clock setting is also important and needs to be set based on which TiWi is being used.
If the kernel is lacking device tree support for the driver this patch may help: https://lkml.org/lkml/2014/2/28/60
WL127x firmware that worked with this kernel version:
- SR: 188.8.131.52.139
- MR: 184.108.40.206.47
- PLT: 220.127.116.11.137
These are normally distributed as files named wl127x-fw-4-*.bin. These need to be renamed to wl127x-fw-5-*.bin and placed inside /lib/firmware/ti-connectivity/ for the driver to find and load them correctly. These firmware files were obtained from the ti-utils git repository (git://github.com/TI-OpenLink/ti-utils.git) using the tag ol_R5.SP7.01.
After the driver is working the same calibration steps listed for kernel v3.4 and earlier should be followed.
The module comes with a MAC address fused into the WL12xx chipset. This MAC is used by default for the Bluetooth core and can be used as the WLAN MAC address as well. The MAC address is set at calibration time for WLAN. To use the built in MAC address for WLAN be sure to pass a MAC address of 00:00:00:00:00:00 as a parameter to the autocalibrate function. To set a custom MAC address for WLAN just pass the desired value into the autocalibrate function. See here for details on the WLAN MAC address: WL12xx MAC Address
To change the MAC address for Bluetooth a VS command must be issued each time after the Bluetooth core is powered on. See here for details on the VS command: Bluetooth write BD Addr
- Is the TiWi-R2 obsolete?
No, the TiWi-R2 still in production, and there are no plans to discontinue it. Any new designs should use the TiWi-BLE or TiWi5 Modules. Both of these modules support additional features.
- Where can I get a datasheet for the WL1271?
The datasheet for the WL1271 is not public, and can only be obtained under NDA to customers through TI. Enough information is presented in the TiWi-R2 datasheet for most applications. Contact your local TI Sales Representative if you feel it is necessary to obtain the datasheet.
- Where can I get the command set/interface for WLAN and Bluetooth®?
There is no published command set for either radio. The only interface is through the drivers built into the OS. The commands would have to be extracted, or reverse engineered from there.
- What antennas can I use with the module?
The answer to this question depends on if you plan on using the modular certification of the module.
If you want to use the modular certification you need to use one of the antennas that the module was certified with. Consult the datasheet, or product webpage to determine which antennas the module was certified with. If none of the certified antennas meet your requirements, another antenna may be used, however the modular certification will NOT be valid. The new antenna will need to be tested for EMC compliance. Contact LSR’s EMC Test Services to learn more about this process and how we can help.
- Can I substitute antennas? For example can I use another dipole antenna instead of the exact model a module was certified with?
Yes, this is possible if: 1) The peak gain of the alternate antenna is less than or equal to the original antenna, and 2) The antennas are the same type.
There are some cases that are not black and white. It is the customer's responsibility to collect and retain the appropriate and accurate test data traceable to NIST standards for the alternate antenna. Please contact LSR to discuss any questions.
- How do I use the FM Radio on the TiWi-R2 Module?
The FM radio is tested by TI at the WL1271 level, but not tested at the Module level by LSR at the present time. Therefore LSR assumes no liability for its operation. If this is a requirement for an application, please feel free to contact LSR to discuss. Information on using the FM radio (again at a customers own risk) can be obtained from TI. For example see TI OMAP Wiki.
- What Bluetooth® Profiles are supported by the TiWi-R2?
The Linux driver supports A2DP, HFP, HSP, OPP and FTP profiles.
The Win CE driver supports SDP, SSP, OPP, FTP, DUN, PAN et AD2P.
- Was any SAR testing done on the TiWi-R2 Module?
Yes, the TiWi-R2 Module is certified as mobile device >20cm from the human body. Note that LSR has completed a class 1 permissive change allowing the TiWi-R2 to fall under these certifications.
- The performance of my TiWi-R2 Module is not matching the published specs in the datasheet. What is wrong?
The ini file in your OS/Driver likely does not have the correct parameters. It is important that you update this in your OS/Driver by following the instructions in the TiWi Family INI Radio Parameter User Guide available on the TiWi-R2 Module download page.
Didn't find the answer to your question here? Try:
ForumPost or view product support questions
EMail Technical SupportEmails will be assigned a Technical Support Request (TSR) number and assigned a LSR resource. We work diligently to respond to all email and forum posts as soon as possible.
EMail Technical SalesFor questions relating to RF Design Services, RF Module Sales and EMC Testing Services, email our Technical Sales Department.