SSd2ZSBiZWVuIHRyeWluZyB0byBnZXQgdGhlIHdsMTI3MS1zZGlvIGRyaXZlciB0byB3b3JrLCBh
bmQgc28gZmFyIEkndmUKbWFuYWdlZCB0byBnZXQgdGhlIGRldmljZSB0byBzdGFydCB1cCwgYnV0
IGFtIHVuYWJsZSB0byBzZWUgYW55IGFjY2Vzcwpwb2ludHMuIEknbSB1c2luZyB0aGUgbGF0ZXN0
IGhlYWQgZnJvbSBMdWNpYW5vJ3Mgd2wxMnh4IHRyZWUsIGFuZCBmb3IKZmlybXdhcmUgSSdtIHVz
aW5nIHRoZSBmaWxlcyBjb21taXR0ZWQgdG8gbGludXgtZmlybXdhcmUgYnkgU2hhaGFyIExldmkK
KHdsMTI3MS1mdy5iaW4gdmVyc2lvbiA2LjEuMC4wLjM0MykuIEknbSB3b25kZXJpbmcgaWYgdGhl
cmUncyBtYXliZSBzb21lCm1pbm9yIGNvbXBvbmVudCBvciBzZXR0aW5nIHRoYXQgSSdtIG1pc3Np
bmcgKGxpa2UgcmFkaW8tZW5hYmxlLCBvcgpwZXJoYXBzIGxpbWl0IHRvIDgwMi4xMWEsIGV0Yyk/
CgpXaXRoIGFsbCBkZWJ1ZyBpbmZvcm1hdGlvbiB0dXJuZWQgb24gaW4gdGhlIGRyaXZlciwgSSBz
ZWUgcGxlbnR5IG9mCmNvbW11bmljYXRpb24gZ29pbmcgYmFjayBhbmQgZm9ydGggdy9vIGFueSAo
bm90aWNlYWJsZSkgZXJyb3JzLCBidXQgSQpkb24ndCBzZWUgYW55IHNpZ24gb2YgbWFnaWMgc3Ry
aW5ncyBzdWNoIGFzIGFueSBvZiB0aGUgRVNTSURzIEkgZXhwZWN0CnRvIHNlZSBpbiB0aGUgYXJl
YS4KCi0tCkpvc2ggV2F0dHMK
On Tue, 2010-11-23 at 19:51 +0200, Luciano Coelho wrote:
> Hi Josh,
>
> On Tue, 2010-11-23 at 10:34 -0500, ext Josh Watts wrote:
> > I've been trying to get the wl1271-sdio driver to work, and so far I've
> > managed to get the device to start up, but am unable to see any access
> > points. I'm using the latest head from Luciano's wl12xx tree, and for
> > firmware I'm using the files committed to linux-firmware by Shahar Levi
> > (wl1271-fw.bin version 6.1.0.0.343). I'm wondering if there's maybe some
> > minor component or setting that I'm missing (like radio-enable, or
> > perhaps limit to 802.11a, etc)?
>
> If you got that far, the scan "should" work. ;) My main guess is that
> your device is not calibrated properly (the NVS that Shahar provided is
> a "default" one and may work, but the results will vary wildly depending
> on your RF).
>
> Which device are you using? If you bought a end-user device, you may
> find the appropriate NVS lying somewhere in the filesystem. If you're
> working on a new device, you will need to get it calibrated.
> Unfortunately we don't have a publicly available application to do that
> yet (but there's one under work).
We are using the TiWi-R1 from LS Research. Connected to the U.Fl
connector is a custom antenna board with a ceramic chip on it. Is this
calibration specific to the TiWi-R1 itself, or to the entire system
including antenna?
If my particular implementation requires calibration, what kind of
expertise and equipment would we need to perform it? (I myself am no RF
engineer ;-) If not, it seems I should get in contact with someone at LS
Research to see about obtaining the proper NVS file?
> > With all debug information turned on in the driver, I see plenty of
> > communication going back and forth w/o any (noticeable) errors, but I
> > don't see any sign of magic strings such as any of the ESSIDs I expect
> > to see in the area.
>
> Please send the debug information to us and we may be able to figure
> something out from the logs. You probably don't need DEBUG_SDIO,
> because that one will dump a *lot* of stuff that will probably not help
> here...
See attached (wlan0.log.20101123_1317 201.4KiB) for the debug log (copy
of /var/log/messages) sans DEBUG_SDIO.
On Tue, 2010-11-23 at 18:41 +0100, Levi, Shahar wrote:
Hi,
> sdio function: 23.545043 chip id read correctly.
> FW boot well: 25.239135.
> the driver transmit probe req but the your mac address looks strange.
> Try set mac address by using:
> >ifconfig wlan0 hw ether 08:00:28:00:61:39
> >sleep 1
> >ifconfig wlan0 up
>
> Instead of 'ifup wlan0'.
Shahar, the attached log file was generated using your tip from above.
I'm afraid that as Luca pointed out, the NVS file from linux-firmware
may not work with my hardware setup.
--
Josh Watts
T24gVHVlLCAyMDEwLTExLTIzIGF0IDIxOjEzICswMjAwLCBJZG8gWWFyaXYgd3JvdGU6Cj4gT24g
VHVlLCBOb3YgMjMsIDIwMTAgYXQgMTA6MzQ6MTRBTSAtMDUwMCwgSm9zaCBXYXR0cyB3cm90ZToK
PiA+IEknbSB3b25kZXJpbmcgaWYgdGhlcmUncyBtYXliZSBzb21lCj4gPiBtaW5vciBjb21wb25l
bnQgb3Igc2V0dGluZyB0aGF0IEknbSBtaXNzaW5nIChsaWtlIHJhZGlvLWVuYWJsZSwgb3IKPiA+
IHBlcmhhcHMgbGltaXQgdG8gODAyLjExYSwgZXRjKT8KPiBIaSBKb3NoLAo+IAo+IFRoZXNlIGtp
bmQgb2YgcHJvYmxlbXMgY291bGQgYmUgY2F1c2VkIGJ5IHVzaW5nIGEgd3JvbmcgcmVmZXJlbmNl
IGNsb2NrCj4gdmFsdWUuIENvdWxkIHlvdSBwbGVhc2UgZG91YmxlIGNoZWNrIHRoYXQgdGhlIHJl
ZmVyZW5jZSBjbG9jawo+IChib2FyZF9yZWZfY2xvY2spIG1hdGNoZXMgdGhlIHJlZmVyZW5jZSBj
bG9jayBjb25uZWN0ZWQgdG8gdGhlIHdsMTI3MT8KPiAKPiBSZWdhcmRzLAo+IElkby4KCkRvZXMg
Ym9hcmRfcmVmX2Nsb2NrIHJlZmVyIHRvIHRoZSBTTE9XX0NMSyBzaWduYWwgZmVkIHRvIHRoZSBU
aVdpIGJvYXJkPwpUaGUgZGF0YXNoZWV0LCBhbmQgdGh1cyB0aGUgYm9hcmQgd2UgZGVzaWduZWQs
IHNob3dzIHRoaXMgc2lnbmFsIHNob3VsZApiZSAzMktIeiwgYnV0IHdoZW4gSSBsb29rIHRocm91
Z2ggdGhlIHdsMTJ4eCBkcml2ZXIgc291cmNlLCBJIGNhbiBvbmx5CmZpbmQgb3B0aW9ucyBmb3Ig
MTkuMiwgMjYsIDM4LjQsIDQwIGFuZCAzMy42LiBDdXJyZW50bHkgSSBoYXZlCmJvYXJkX3JlZl9j
bG9jayBzZXQgdG8gMSwgd2hpY2ggSSB0aGluayBpcyBzdXBwb3NlZCB0byBiZSBSRUZfRlJFUV8y
Nl8wPwooSSBib3Jyb3dlZCB0aGUgbGluZSBvZiBjb2RlIGZyb20gdGhlIGJvYXJkLXpvb20tcGVy
aXBoZXJhbHMuYykKCi0tIGJvYXJkLXpvb20tcGVyaXBoZXJhbHMuYyAtLQpzdHJ1Y3Qgd2wxMnh4
X3BsYXRmb3JtX2RhdGEgb21hcF96b29tX3dsYW5fZGF0YSBfX2luaXRkYXRhID0gewogICAgICAg
IC5pcnEgPSBPTUFQX0dQSU9fSVJRKE9NQVBfWk9PTV9XTEFOX0lSUV9HUElPKSwKICAgICAgICAv
KiBaT09NIHJlZiBjbG9jayBpcyAyNiBNSHogKi8KICAgICAgICAuYm9hcmRfcmVmX2Nsb2NrID0g
MSwKfTsKLS0gZW5kIGNsaXAgLS0KCi0tIHJlZy5oIC0tCiNkZWZpbmUgUkVGX0ZSRVFfMTlfMiAg
ICAgICAgICAgICAgICAgICAgICAgMAojZGVmaW5lIFJFRl9GUkVRXzI2XzAgICAgICAgICAgICAg
ICAgICAgICAgIDEKI2RlZmluZSBSRUZfRlJFUV8zOF80ICAgICAgICAgICAgICAgICAgICAgICAy
CiNkZWZpbmUgUkVGX0ZSRVFfNDBfMCAgICAgICAgICAgICAgICAgICAgICAgMwojZGVmaW5lIFJF
Rl9GUkVRXzMzXzYgICAgICAgICAgICAgICAgICAgICAgIDQKI2RlZmluZSBSRUZfRlJFUV9OVU0g
ICAgICAgICAgICAgICAgICAgICAgICA1Ci0tIGVuZCBjbGlwIC0tCgotLQpKb3NoIFdhdHRzCg==
T24gVHVlLCAyMDEwLTExLTIzIGF0IDE2OjMwIC0wNTAwLCBKb3NoIFdhdHRzIHdyb3RlOgo+IE9u
IFR1ZSwgMjAxMC0xMS0yMyBhdCAyMToxMyArMDIwMCwgSWRvIFlhcml2IHdyb3RlOgo+ID4gT24g
VHVlLCBOb3YgMjMsIDIwMTAgYXQgMTA6MzQ6MTRBTSAtMDUwMCwgSm9zaCBXYXR0cyB3cm90ZToK
PiA+ID4gSSdtIHdvbmRlcmluZyBpZiB0aGVyZSdzIG1heWJlIHNvbWUKPiA+ID4gbWlub3IgY29t
cG9uZW50IG9yIHNldHRpbmcgdGhhdCBJJ20gbWlzc2luZyAobGlrZSByYWRpby1lbmFibGUsIG9y
Cj4gPiA+IHBlcmhhcHMgbGltaXQgdG8gODAyLjExYSwgZXRjKT8KPiA+IEhpIEpvc2gsCj4gPiAK
PiA+IFRoZXNlIGtpbmQgb2YgcHJvYmxlbXMgY291bGQgYmUgY2F1c2VkIGJ5IHVzaW5nIGEgd3Jv
bmcgcmVmZXJlbmNlIGNsb2NrCj4gPiB2YWx1ZS4gQ291bGQgeW91IHBsZWFzZSBkb3VibGUgY2hl
Y2sgdGhhdCB0aGUgcmVmZXJlbmNlIGNsb2NrCj4gPiAoYm9hcmRfcmVmX2Nsb2NrKSBtYXRjaGVz
IHRoZSByZWZlcmVuY2UgY2xvY2sgY29ubmVjdGVkIHRvIHRoZSB3bDEyNzE/Cj4gPiAKPiA+IFJl
Z2FyZHMsCj4gPiBJZG8uCj4gCj4gRG9lcyBib2FyZF9yZWZfY2xvY2sgcmVmZXIgdG8gdGhlIFNM
T1dfQ0xLIHNpZ25hbCBmZWQgdG8gdGhlIFRpV2kgYm9hcmQ/CgpPb3BzLCBJIHNlZSBub3cgSSB3
YXMgY29uZnVzZWQgb24gdGhpcyBwb2ludC4gSXQgYXBwZWFycyBib2FyZF9yZWZfY2xvY2sKcmVm
ZXJzIHRvIHRoZSBTRElPIGNsb2NrIGxpbmUsIGNvcnJlY3Q/IEl0IGFwcGVhcnMgdGhhdCBteSBN
TUMvU0RJTwppbnRlcmZhY2UgaXMgYXV0by1jb25maWd1cmluZyBpdHNlbGYgdG8gMjVNSHouIElz
IHRoaXMgY2xvc2UgZW5vdWdoIHRvCjI2TUh6LCBvciBkbyB5b3UgdGhpbmsgSSBzaG91bGQgbG9v
ayBpbnRvIGFkanVzdGluZy9mb3JjaW5nIHRoZQppbnRlcmZhY2UgdG8gb3BlcmF0ZSBhdCBvbmUg
b2YgdGhlIHJhdGVzIGxpc3RlZCBpbiB3bDEyeHgvYm9vdC5jPwoKLS0KSm9zaCBXYXR0cwo=
Hi Josh,
On Tue, 2010-11-23 at 10:34 -0500, ext Josh Watts wrote:
> I've been trying to get the wl1271-sdio driver to work, and so far I've
> managed to get the device to start up, but am unable to see any access
> points. I'm using the latest head from Luciano's wl12xx tree, and for
> firmware I'm using the files committed to linux-firmware by Shahar Levi
> (wl1271-fw.bin version 6.1.0.0.343). I'm wondering if there's maybe some
> minor component or setting that I'm missing (like radio-enable, or
> perhaps limit to 802.11a, etc)?
If you got that far, the scan "should" work. ;) My main guess is that
your device is not calibrated properly (the NVS that Shahar provided is
a "default" one and may work, but the results will vary wildly depending
on your RF).
Which device are you using? If you bought a end-user device, you may
find the appropriate NVS lying somewhere in the filesystem. If you're
working on a new device, you will need to get it calibrated.
Unfortunately we don't have a publicly available application to do that
yet (but there's one under work).
> With all debug information turned on in the driver, I see plenty of
> communication going back and forth w/o any (noticeable) errors, but I
> don't see any sign of magic strings such as any of the ESSIDs I expect
> to see in the area.
Please send the debug information to us and we may be able to figure
something out from the logs. You probably don't need DEBUG_SDIO,
because that one will dump a *lot* of stuff that will probably not help
here...
--
Cheers,
Luca.
Sm9zaCwNCg0KPiA+ID4gVGhlc2Uga2luZCBvZiBwcm9ibGVtcyBjb3VsZCBiZSBjYXVzZWQgYnkg
dXNpbmcgYSB3cm9uZyByZWZlcmVuY2UgY2xvY2sNCj4gPiA+IHZhbHVlLiBDb3VsZCB5b3UgcGxl
YXNlIGRvdWJsZSBjaGVjayB0aGF0IHRoZSByZWZlcmVuY2UgY2xvY2sNCj4gPiA+IChib2FyZF9y
ZWZfY2xvY2spIG1hdGNoZXMgdGhlIHJlZmVyZW5jZSBjbG9jayBjb25uZWN0ZWQgdG8gdGhlIHds
MTI3MT8NCj4gPiA+DQo+ID4gPiBSZWdhcmRzLA0KPiA+ID4gSWRvLg0KPiA+DQo+ID4gRG9lcyBi
b2FyZF9yZWZfY2xvY2sgcmVmZXIgdG8gdGhlIFNMT1dfQ0xLIHNpZ25hbCBmZWQgdG8gdGhlIFRp
V2kgYm9hcmQ/DQo+IA0KPiBPb3BzLCBJIHNlZSBub3cgSSB3YXMgY29uZnVzZWQgb24gdGhpcyBw
b2ludC4gSXQgYXBwZWFycyBib2FyZF9yZWZfY2xvY2sNCj4gcmVmZXJzIHRvIHRoZSBTRElPIGNs
b2NrIGxpbmUsIGNvcnJlY3Q/IEl0IGFwcGVhcnMgdGhhdCBteSBNTUMvU0RJTw0KPiBpbnRlcmZh
Y2UgaXMgYXV0by1jb25maWd1cmluZyBpdHNlbGYgdG8gMjVNSHouIElzIHRoaXMgY2xvc2UgZW5v
dWdoIHRvDQo+IDI2TUh6LCBvciBkbyB5b3UgdGhpbmsgSSBzaG91bGQgbG9vayBpbnRvIGFkanVz
dGluZy9mb3JjaW5nIHRoZQ0KPiBpbnRlcmZhY2UgdG8gb3BlcmF0ZSBhdCBvbmUgb2YgdGhlIHJh
dGVzIGxpc3RlZCBpbiB3bDEyeHgvYm9vdC5jPw0KPiANCg0KMjVNSHogZm9yIHRoZSBTRElPIGNs
b2NrIGlzIGEgY29ycmVjdCB2YWx1ZS4NCkhvd2V2ZXIsIEkgYmVsaWV2ZSB0aGUgaXNzdWUgZGlz
Y3Vzc2VkIGlzIG1vcmUgcmVsYXRlZCB0byB0aGUgZmFzdCBjbG9jayAocmVmZXJlbmNlIGNsb2Nr
KSBzdXBwbGllZCB0byB0aGUgV0wxMjcxIGNoaXAgaXRzZWxmIGFuZCBub3QgdG8gdGhlIFNESU8g
YnVzLg0KVGhpcyBpcyBtb3N0IHByb2JhYmx5IGEgMjZNSHogY2xvY2sgYnV0IHlvdSdkIGJldHRl
ciB2ZXJpZnkgaG93IHlvdXIgaGFyZHdhcmUgaXMgd2lyZWQuDQoNClJlZ2FyZHMsDQpPei4NCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg==
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBsaW51eC13aXJlbGVzcy1vd25l
ckB2Z2VyLmtlcm5lbC5vcmcgW21haWx0bzpsaW51eC13aXJlbGVzcy0NCj4gb3duZXJAdmdlci5r
ZXJuZWwub3JnXSBPbiBCZWhhbGYgT2YgSm9zaCBXYXR0cw0KPiBTZW50OiBUdWVzZGF5LCBOb3Zl
bWJlciAyMywgMjAxMCA1OjM0IFBNDQo+IFRvOiBsaW51eC13aXJlbGVzc0B2Z2VyLmtlcm5lbC5v
cmcNCj4gU3ViamVjdDogTm8gc2NhbiByZXN1bHRzIGZyb20gd2wxMjcxLXNkaW8NCj4gDQo+IEkn
dmUgYmVlbiB0cnlpbmcgdG8gZ2V0IHRoZSB3bDEyNzEtc2RpbyBkcml2ZXIgdG8gd29yaywgYW5k
IHNvIGZhciBJJ3ZlDQo+IG1hbmFnZWQgdG8gZ2V0IHRoZSBkZXZpY2UgdG8gc3RhcnQgdXAsIGJ1
dCBhbSB1bmFibGUgdG8gc2VlIGFueSBhY2Nlc3MNCj4gcG9pbnRzLiBJJ20gdXNpbmcgdGhlIGxh
dGVzdCBoZWFkIGZyb20gTHVjaWFubydzIHdsMTJ4eCB0cmVlLCBhbmQgZm9yDQo+IGZpcm13YXJl
IEknbSB1c2luZyB0aGUgZmlsZXMgY29tbWl0dGVkIHRvIGxpbnV4LWZpcm13YXJlIGJ5IFNoYWhh
ciBMZXZpDQo+ICh3bDEyNzEtZncuYmluIHZlcnNpb24gNi4xLjAuMC4zNDMpLiBJJ20gd29uZGVy
aW5nIGlmIHRoZXJlJ3MgbWF5YmUNCj4gc29tZQ0KPiBtaW5vciBjb21wb25lbnQgb3Igc2V0dGlu
ZyB0aGF0IEknbSBtaXNzaW5nIChsaWtlIHJhZGlvLWVuYWJsZSwgb3INCj4gcGVyaGFwcyBsaW1p
dCB0byA4MDIuMTFhLCBldGMpPw0KPiANCj4gV2l0aCBhbGwgZGVidWcgaW5mb3JtYXRpb24gdHVy
bmVkIG9uIGluIHRoZSBkcml2ZXIsIEkgc2VlIHBsZW50eSBvZg0KPiBjb21tdW5pY2F0aW9uIGdv
aW5nIGJhY2sgYW5kIGZvcnRoIHcvbyBhbnkgKG5vdGljZWFibGUpIGVycm9ycywgYnV0IEkNCj4g
ZG9uJ3Qgc2VlIGFueSBzaWduIG9mIG1hZ2ljIHN0cmluZ3Mgc3VjaCBhcyBhbnkgb2YgdGhlIEVT
U0lEcyBJIGV4cGVjdA0KPiB0byBzZWUgaW4gdGhlIGFyZWEuDQo+IA0KPiAtLQ0KPiBKb3NoIFdh
dHRzDQpJIHdvdWxkIGJlIGRlbGlnaHRlZCB0byBsb29rIG9uIGRlYnVnIGxvZyBpbiBvcmRlciB0
byBoZWxwLiBTZW5kIG1lIGRpcmVjdGx5IGEgbG9nIGFuZCBJIHdpbGwgbG9vayBvbiB0aGF0Lg0K
Q2hlZXJzLA0KU2hhaGFyDQoNCg==
On 23 בנוב 2010, at 23:35, Josh Watts <[email protected]> wrote:
> On Tue, 2010-11-23 at 16:30 -0500, Josh Watts wrote:
>> On Tue, 2010-11-23 at 21:13 +0200, Ido Yariv wrote:
>>> On Tue, Nov 23, 2010 at 10:34:14AM -0500, Josh Watts wrote:
>>>> I'm wondering if there's maybe some
>>>> minor component or setting that I'm missing (like radio-enable, or
>>>> perhaps limit to 802.11a, etc)?
>>> Hi Josh,
>>>
>>> These kind of problems could be caused by using a wrong reference clock
>>> value. Could you please double check that the reference clock
>>> (board_ref_clock) matches the reference clock connected to the wl1271?
>>>
>>> Regards,
>>> Ido.
>>
>> Does board_ref_clock refer to the SLOW_CLK signal fed to the TiWi board?
>
> Oops, I see now I was confused on this point. It appears board_ref_clock
> refers to the SDIO clock line, correct?
No, it's an external clock source hardwired to the 1271 device. You have no control of it, you just need to let the driver know its frequency.
So you can either consult with your module maker, or just try each of the possible options one by one, and see if any of these fix the issue :)
> It appears that my MMC/SDIO
> interface is auto-configuring itself to 25MHz. Is this close enough to
> 26MHz, or do you think I should look into adjusting/forcing the
> interface to operate at one of the rates listed in wl12xx/boot.c?
>
> --
> Josh Watts
On Tue, 2010-11-23 at 13:51 -0500, ext Josh Watts wrote:
> See attached (wlan0.log.20101123_1317 201.4KiB) for the debug log
> (copy of /var/log/messages) sans DEBUG_SDIO.
According to the logs, everything seems to go well, including the probe
requests seem to be configure correctly before the scan. But I don't
see any RX interrupts...
Do you have a sniffer or a device that can be put into monitor mode to
use with wireshark? If you do, an airlog of this scenario will probably
give us more clues...
--
Cheers,
Luca.
T24gVHVlLCAyMDEwLTExLTIzIGF0IDIxOjE0ICswMjAwLCBMdWNpYW5vIENvZWxobyB3cm90ZToK
PiBPbiBUdWUsIDIwMTAtMTEtMjMgYXQgMTM6NTEgLTA1MDAsIGV4dCBKb3NoIFdhdHRzIHdyb3Rl
Ogo+ID4gU2VlIGF0dGFjaGVkICh3bGFuMC5sb2cuMjAxMDExMjNfMTMxNyAyMDEuNEtpQikgZm9y
IHRoZSBkZWJ1ZyBsb2cKPiA+IChjb3B5IG9mIC92YXIvbG9nL21lc3NhZ2VzKSBzYW5zIERFQlVH
X1NESU8uIAo+IAo+IEFjY29yZGluZyB0byB0aGUgbG9ncywgZXZlcnl0aGluZyBzZWVtcyB0byBn
byB3ZWxsLCBpbmNsdWRpbmcgdGhlIHByb2JlCj4gcmVxdWVzdHMgc2VlbSB0byBiZSBjb25maWd1
cmUgY29ycmVjdGx5IGJlZm9yZSB0aGUgc2Nhbi4gIEJ1dCBJIGRvbid0Cj4gc2VlIGFueSBSWCBp
bnRlcnJ1cHRzLi4uCj4gCj4gRG8geW91IGhhdmUgYSBzbmlmZmVyIG9yIGEgZGV2aWNlIHRoYXQg
Y2FuIGJlIHB1dCBpbnRvIG1vbml0b3IgbW9kZSB0bwo+IHVzZSB3aXRoIHdpcmVzaGFyaz8gSWYg
eW91IGRvLCBhbiBhaXJsb2cgb2YgdGhpcyBzY2VuYXJpbyB3aWxsIHByb2JhYmx5Cj4gZ2l2ZSB1
cyBtb3JlIGNsdWVzLi4uCgpJIGRvbid0IGhhdmUgYW55IHNuaWZmaW5nIHNvZnR3YXJlIG9uIHRo
ZSBkZXZpY2UgYXQgdGhlIG1vbWVudCwgYnV0IEknbGwKZ2l2ZSB0aGF0IGEgc2hvdCBhcyBzb29u
IGFzIHdpcmVzaGFyayBmaW5pc2hlcyBiaXRiYWtpbmcuCgpJIHRyaWVkIHVzaW5nIG15IGxhcHRv
cCB0byB0cnkgYW5kIHNuaWZmaW5nIGZvciBhbnl0aGluZyBjb21pbmcgZnJvbSB0aGUKV0wxMjcx
LCBidXQgSSBkaWRuJ3Qgc2VlIGFueXRoaW5nIHdoZW4gbGltaXRpbmcgdG8gdGhlIE1BQyBhZGRy
ZXNzIG9mIG15CldMMTI3MS4KCldpbGwgZ2V0IGJhY2sgdG8geW91IGlmIEkgbWFuYWdlIHRvIGZp
bmQgYW55dGhpbmcKCi0tCkpvc2ggV2F0dHMK
On Tue, 2010-11-23 at 13:51 -0500, ext Josh Watts wrote:
> On Tue, 2010-11-23 at 19:51 +0200, Luciano Coelho wrote:
> > Hi Josh,
> >
> > On Tue, 2010-11-23 at 10:34 -0500, ext Josh Watts wrote:
> > > I've been trying to get the wl1271-sdio driver to work, and so far I've
> > > managed to get the device to start up, but am unable to see any access
> > > points. I'm using the latest head from Luciano's wl12xx tree, and for
> > > firmware I'm using the files committed to linux-firmware by Shahar Levi
> > > (wl1271-fw.bin version 6.1.0.0.343). I'm wondering if there's maybe some
> > > minor component or setting that I'm missing (like radio-enable, or
> > > perhaps limit to 802.11a, etc)?
> >
> > If you got that far, the scan "should" work. ;) My main guess is that
> > your device is not calibrated properly (the NVS that Shahar provided is
> > a "default" one and may work, but the results will vary wildly depending
> > on your RF).
> >
> > Which device are you using? If you bought a end-user device, you may
> > find the appropriate NVS lying somewhere in the filesystem. If you're
> > working on a new device, you will need to get it calibrated.
> > Unfortunately we don't have a publicly available application to do that
> > yet (but there's one under work).
>
> We are using the TiWi-R1 from LS Research. Connected to the U.Fl
> connector is a custom antenna board with a ceramic chip on it. Is this
> calibration specific to the TiWi-R1 itself, or to the entire system
> including antenna?
There are two main parts in the NVS. One is more or less per design.
Meaning that one type of board needs certain parameters. This is the so
called "Radio Parameters" in the NVS. Only the manufacturer or someone
with appropriate knowledge and equipment can provide you with that (I
have no clue about the details, because I'm RF illiterate). I suggest
you ask this from LS Research, since the probably have that already.
The other part is per device. Each individual device needs to be
calibrated. You don't need any special equipment for that, the firmware
can perform all the steps needed. But you need an application that
sends the commands to the firmware and reads the results (via
NL80211_TESTMODE).
> If my particular implementation requires calibration, what kind of
> expertise and equipment would we need to perform it? (I myself am no RF
> engineer ;-) If not, it seems I should get in contact with someone at LS
> Research to see about obtaining the proper NVS file?
The radio parameters part, as far as I know, is more important than the
per-device calibration. But you won't be able to achieve good
throughput and you'll see lots of retransmissions if you don't calibrate
it properly.
> > > With all debug information turned on in the driver, I see plenty of
> > > communication going back and forth w/o any (noticeable) errors, but I
> > > don't see any sign of magic strings such as any of the ESSIDs I expect
> > > to see in the area.
> >
> > Please send the debug information to us and we may be able to figure
> > something out from the logs. You probably don't need DEBUG_SDIO,
> > because that one will dump a *lot* of stuff that will probably not help
> > here...
>
> See attached (wlan0.log.20101123_1317 201.4KiB) for the debug log (copy
> of /var/log/messages) sans DEBUG_SDIO.
I'll take a look at it now...
--
Cheers,
Luca.