• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 40 subscribers
  • Views 542 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Shared Transport and WL1271 (i.e. WiLink without GPS)

Chris Read
Genius 3345 points
Other Parts Discussed in Thread: WL1271, OMAP3530

I am trying to get our WL1271 LSR module working with Android ICS on the OMAP3530.  On the ICS porting page the Bluetooth support seems to require using the TI_ST  shared transport driver.  However our WL1271 module doesn't support GPS or FM.  I have had some success talking to our LSR module, including intermittently loading the firmware (TIInit_7.2.31.bts), but there seems to be much work to do, so I have some quick questions to help direct my activity...

  1. Will using the TI_ST shared transport drivers work with WiLink chips that don't have GPS, such as the WL1271?
  2. Does not using the TI_ST drivers require a different firmware load for Bluetooth (i.e. a different TIInit_x.x.x.bts file) than when you use TI_ST?
  3. Will the CONFIG_BT_WILINK (as opposed to the CONFIG_BT_WL1271) driver work with the WL1271 even though it doesn't have GPS?

Thanks in advance,

Chris

  • 0
    Prodigy 70 points

    1. Yes, TI_ST driver was designed and developed to work with ANY WL family of chipsets which expose UART interface for either BT, FM or GPS.
    2. No, Using dedicated UART s/w solutions like hciattach + HCI-UART (HCI-LL) drivers or Using ti-st & btwilink driver will make
    use of same firmware (named TIInit_X.X.X.bts), TI-ST makes use of kernel firmware class, hciattach does it from user-space.
    3. Yes, It will.

    few other added advantages :-
    * TI-ST driver provides or combines few things together, i.e It will to begin with toggle the BT_EN line
    (populated by adding right platform entries). By using hciattach + HCI-LL solution, you'll have to have your own
    wl127x-rfkill sort of gpio toggling driver to do this.
    * It will also download firmware (which is done by hciattach), It takes in 1 baud-rate argument and makes sure both
    chip and host are set to it, unlike hciattach which requires a specific firmware for specific baud-rates.
    * It will also handle HCI_LL messages, which is also done by using hciattach + HCI-LL driver (Not with hciattach + HCI-H4 driver).
    * Has been in more products than hciattach + HCI-LL solution !!