Still problem to configure wiimx28 revc card wlan0 cfg80211

Embedded Devices Linux
, , , ,
1

So, i setup a uboot/kernel/rootfs with :

  • invalidate all Bluetooth & Eth1

Then, updated with them.

I have got

Starting network.
Starting bluetooth services.
/etc/init.d/rcS: FAILED (variant 0x07 does not support bluetooth)
ath6kl: temporary war to avoid sdio crc error
Starting dropbear sshd: OK

ifconfig gave me : eth0 & wlan0 available.

Is it normal to get a bluetooth failed even with no bluetooth asked ?

=================================

After that, in our user software i need to create wifi AP using wpa-supplicant. Up to now, i used cfg80211 driver and got no problem.

Then , i tried to add “cfg80211” driver.
So, i checked the cfg80211 checkbox and wireless lan (as i did with my old ccard). I got a lot of warnings during the make process and as result on linux console :

Starting network.
Starting bluetooth services.
/etc/init.d/rcS: FAILED (variant 0x07 does not support bluetooth)
modprobe: can’t load module ath6kl_sdio (extra/ath6kl_sdio.ko): Invalid argument
Loading ath6kl_sdio module: [FAILED]
ifconfig: SIOCGIFFLAGS: No such device
Starting dropbear sshd: OK

ifconfig gave me : eth0 but no wlan0 available.

=================================

Could you tell me, please :

  • if i have to use cfg80211 to set an AP with wpa-supplicant ?
  • and, if yes, how to configure correctly it ?

Thank you very much Leonid

2

So are you able to use wifi now and connect to wireless AP.

>Is it normal to get a bluetooth failed even with no bluetooth asked ?
Are you sure you have updated both kernel and rootfs with images you have built?

If basic wifi works you can proceed to the next step and configure SoftAP.
DEL documentation shows how to configure ccwimx28 wifi in SoftAP mode:
The ConnectCard for i.MX28 module includes a wireless chip by Qualcomm Atheros. The driver supports 802.11a/b/g/n and 802.11h/d/i/e. The driver for this chip is provided in source code and built as an external module. This chapter describes some of the driver specific features and control commands.

The Atheros wireless driver can be configured in SoftAP mode using wpa_supplicant.

The following excerpt shows the /etc/wpa_supplicant.conf configuration file for making the target work as SoftAP in open authentication and no encryption mode, at 2.412 GHz:

SoftAP mode (open/no encryption)

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
fast_reauth=1
update_config=1

ap_scan=2
network={
ssid=“ath6kl-ap”
mode=2
frequency=2412
key_mgmt=NONE
}
A client station that wants to connect to the target’s SoftAP needs to configure its /etc/wpa_supplicant.conf like this:.

Client that connects to the SoftAP

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
fast_reauth=1
update_config=1

ap_scan=1
network={
scan_ssid=1
ssid=“ath6kl-ap”
key_mgmt=NONE
}
The following excerpt shows the /etc/wpa_supplicant.conf configuration file for making the target work as SoftAP with WPA2-PSK authentication and AES-CCMP encryption, at 2.412 GHz using the pass phrase 12345678:

SoftAP mode (WPA-PSK/AES)

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
fast_reauth=1
update_config=1

ap_scan=2
network={
ssid=“ath6kl-ap”
mode=2
frequency=2412
key_mgmt=WPA-PSK
proto=RSN
pairwise=CCMP
psk=“12345678”
}
To connect to the AP from a client station, a PSK key must be generated based on the SoftAP SSID and its pass phrase. The wpa_passphrase application can be used to get such key. In our example:

wpa_passphrase ath6kl-ap 12345678

network={
ssid=“ath6kl-ap”
#psk=“12345678”
psk=27b9137ab2d24609864128ea8c97399f06ca37ff2ca40c6617a17d265e57b171
}
Once we have the key, we can establish the complete configuration for the client station.

Client that connects to the SoftAP

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
fast_reauth=1
update_config=1

ap_scan=1
network={
scan_ssid=1
ssid=“ath6kl-ap”
key_mgmt=WPA-PSK
proto=RSN
pairwise=CCMP
#psk=“12345678”
psk=27b9137ab2d24609864128ea8c97399f06ca37ff2ca40c6617a17d265e57b171
}