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.

Questions regarding wl1831, WLAN and Bluetooth

Other Parts Discussed in Thread: WL1831, WL1831MOD

Hi All,

We are using wl1831 in one of our product. and i have some questions regarding it.

1. I am going through the datsheet and i have found that wl1832mod is Fully Calibrated: Production Calibration Not Required. What does this mean?
Don't we need to do calibration which we are used to do with wl12xx modules?

2. Another thing, i have found in datasheet is,

SmartConfigTM Connects In-Home Devices to
Wi-Fi in One Step

What is the meaning of it?

3.In the datasheet, it is written that For bluetooth and BLE, there is Royalty-Free Certified Stack From StoneStreet One.

From where we can get it?

We are using linux on freescale processor. Do this stack have any benefits over bluez stack? Which should we use?

or this stack is any plugin over bluez stack which will improve the perfomance?

4. What values should i pass for below parameters in device tree for wl1831mod?

board-ref-clock

board-tcxo-clock

platform-quirks

Thanks,

Jags

  • Hi Jags,

    1. You are correct. The per unit calibration stage that was used in wl12xx is not required for wl18xx.

    2. SmartConfig is a technology across our wifi devices and was first introduced on CC3000. It is described at http://processors.wiki.ti.com/index.php/CC3000_Smart_Config.  It will be in this months wl18xx driver release (http://processors.wiki.ti.com/index.php/WiLink8_Feature_Guide/Smart_Config)

    3.The "Royalty Free" StoneStreetOne stack is currently only available on AM335x for wl18xx. It is delivered as a binary package and so is compiled with the AM335x SDK toolchain. The advantage over Bluez is that it is a versioned binary that has already been certified and so the stacks QDID number can be used. If you use Bluez you have to run full test suite yourself as there is no way to show that your build is identical to one that has already been certified.

    4. Board tcxo-clock is a don't care in the driver

    ++    wlcore {
    ++        compatible = "wlcore";
    ++        gpio = <136>;   // The wl8 driver expects gpio to be an integer, so gpio5_8 is (5-1)*32+8=136
    ++            // irq property must not be set as driver derives irq number from gpio if no irq set
    ++         /* use edge irqs for suspend/resume */
    ++        platform-quirks = <1>;
    ++
    ++        /* if a 12xx card is there, configure the clock to
    ++           WL12XX_REFCLOCK_38_XTAL */
    ++        board-ref-clock = <4>;
    ++
    ++    };

    Iain