iwlist no scan results

Michael Carrier

Other Parts Discussed in Thread: WL1271

We have a custom board utilizing the wl1271 TiWi-R2 module. We are using Ubuntu embedded distro running on kernel 3.0. We have all necessary modules loaded via insmod. When interface wlan0 is brought up the firmware loads successfully -- firmware booted (Rev 6.1.5.50.69).

If at this point I execute "iwlist wlan0 scan" I get no scan results. However, if I use a distro with kernel 2.637 the scan returns all 11 APs in our building.

1. Has anyone seen this type of issue?

2. in debugging I notices that the 2.6.37 kernel reports :

wl1271_scan: Function Exiting
    wl1271: EVENT on mbox 0
    wl1271: MBOX DUMP:
    wl1271:         vector: 0x10000
    wl1271:         mask: 0xbf9a1bfe
    wl1271: vector: 0x10000
    wl1271: EVENT on mbox 1
    wl1271: MBOX DUMP:
    wl1271:         vector: 0x200000
    wl1271:         mask: 0xbf9a1bfe
    wl1271: vector: 0x200000
    wl1271: DUMMY_PACKET_ID_EVENT_ID
    wl1271: EVENT on mbox 0
    wl1271: MBOX DUMP:
    wl1271:         vector: 0x400
    wl1271:         mask: 0xbf9a1bfe
    wl1271: vector: 0x400
    wl1271: status: 0x55

but the 3.0 kernel does report vector: 0x200000

any thoughts?

over 12 years ago

0 Victor_Lin over 12 years ago

TI__Genius 12935 points

Hi Michael,

iwlist is a deprecated command. Please use iw instead.

Also, it seems like your driver & firmware is outdated. Please update to the latest by following the instruction: http://processors.wiki.ti.com/index.php/WL12xx_NLCP_Build_Instructions

0 Michael Carrier over 12 years ago

Intellectual 370 points

iw also shows no APs. I doubt the drivers are out of date as they came from compat-wireless.

what is vector 0x200000 and when does the wl1271 chip generate such an event?

0 Victor_Lin over 12 years ago in reply to Michael Carrier

TI__Genius 12935 points

Hi Michael,

Can you provide the boot log? According to the message "firmware booted (Rev 6.1.5.50.69).", this version is outdated.

How & When did you build the driver?

0 Michael Carrier over 12 years ago in reply to Victor_Lin

Intellectual 370 points

This particular firmware version was borrowed from the 2.6.37 kernel I tested against. I also used version 6.1.5.50.74 with the same "no scan results".

0 Victor_Lin over 12 years ago in reply to Michael Carrier

TI__Genius 12935 points

Hi Michael,

I'm not sure what you meant by borrowing the firmware from a kernel.

Can you please provide the info I asked for earlier?

On the other hand, can you explain how the kernel report vector is related to this problem?

0 Michael Carrier over 12 years ago in reply to Victor_Lin

Intellectual 370 points

I have two of our custom boards. One board has 2.6.37 kernel and our board startup file. The second board has 3.0 kernel and our board startup file. I took the wl12xx firmware and the NVS from the 2.6.37 filesystem and placed them on the 3.0 filesystem. That is what I meant by "borrowed."

On the two boards I enabled wl12xx debug messages and compared the output from both boards. The outputs were identical except for the line which says vector 0x20000. The 2.6.37 board which is working fine has this debug message where as the 3.0 board does not.

I was asking what the 0x20000 event is hoping that might give a clue as to what the 3.0 issue might be.

0 Michael Carrier over 12 years ago in reply to Michael Carrier

Intellectual 370 points

I am not sure what boot logs you are referring to but I will send the dmesg output first thing tomorrow. It contains the wl12xx debug messages that were enabled in the drivers.

0 Michael Carrier over 12 years ago in reply to Michael Carrier

Intellectual 370 points

This is the nonworking log

0 Michael Carrier over 12 years ago in reply to Michael Carrier

Intellectual 370 points

This is the working log

0 Victor_Lin over 12 years ago in reply to Michael Carrier

TI__Genius 12935 points

Hi Michael,

This is not the dmesg I'm looking for. I'll need you do disable the debug messages and provide me the dmesg all the way from system boot.

By the way, when you built your driver, which git tag did you grab it from?

0 Michael Carrier over 12 years ago in reply to Victor_Lin

Intellectual 370 points

Git commit 600caefd83a406540b2a789be6415e44c9b87add

0 Michael Carrier over 12 years ago in reply to Michael Carrier

Intellectual 370 points

Victor any thoughts on the dmesg logs?

0 Victor_Lin over 12 years ago in reply to Michael Carrier

TI__Genius 12935 points

Hi Michael,

Sorry for the delay. We're looking into this. Will get back to you ASAP.

0 Michael Carrier over 12 years ago in reply to Victor_Lin

Intellectual 370 points

Victor,

Not sure if there is an update on this or not. Can you confirm if there is an issue running the WL1271 part in 3.0 kernel? I can't wait much longer and will probably have to design out the WL1271 in favor of a different vendors Wifi chip set.

0 Barak Schlosser over 12 years ago in reply to Michael Carrier

TI__Intellectual 1710 points

Hi Michael,

The drivers of the WL1271 can be used with Kernel 3.0 and above.

Please refer to the following link and compile the newest driver (you're currently using an old driver):

http://processors.wiki.ti.com/index.php/WL12xx_NLCP_Build_Instructions

Regards,

Barak

0 SUNIL KOTTARY over 12 years ago in reply to Michael Carrier

Intellectual 460 points

Hi Michael

After the boot up follkow these steps

1.if ifconfig -a shows wlan0 then platform initialization is correct

2.ifconfig wlan0 up .if this command executes ten you should observ firmware initialization message

3.after wlan0 is up and iw dev wlan0 scan does not show any result then you need to check the reference clock for the module you are using the by the below link

http://processors.wiki.ti.com/index.php/WL127x_Modules

Refer my posting

http://e2e.ti.com/support/low_power_rf/f/307/p/291593/1022372.aspx#1022372

Sunil kottary

Wi-Fi

Wi-Fi forum

iwlist no scan results