logo

Could not compile stylesheet for simplistic. Using last compiled stylesheet.
Issue

CONFIG_WIRELESS_EXT activation using Wilink8 with IGEPv2-RF60

posted in IGEPv2
Monday, February 08 2016, 02:02 PM
0
Hi,

I start working with IGEPv2-RF60 board and Wilink8 WiFi module, and then i follow this tutorial:
http://labs.isee.biz/index.php/Linux_Kernel_2.6.37.y_-_Wilink_8

I would need to activate the following kernel option to have wireless tools enabled (mandatory for our WiFi usages):
CONFIG_WIRELESS_EXT=y
Following configuring the kernel config file with igep00x0_wilink8_defconfig, and starting kernel build, the CONFIG_WIRELESS_EXT=y option disappears from .config file (maybe not compliant with other config options).

Next building Wilink8 modules with kernel without CONFIG_WIRELESS_EXT=y option, this line appears:
compat-wireless-wilink8-0/config.mk:239: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."
(i also tried to add CONFIG_LIBIPW=m option, and CONFIG_WIRELESS_EXT=y still disappears from .config file following kernel build.)

In our WiFi usage, we need to configure wlan0 interface with these commands (in /etc/network/interfaces):
auto wlan0
iface wlan0 inet static
wireless-mode ad-hoc
wireless-essid ObserverBnext
wireless-channel 4
address 192.168.10.1
network 192.168.10.0
netmask 255.255.255.0

These wlan0 parameters don't work, and trying to configure them with iwconfig command, there are the following errors:
root@igep00x0:~# iwconfig wlan0
wlan0 no wireless extensions.
root@igep00x0:~# iwconfig wlan0 essid "toto"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; Operation not supported.
root@igep00x0:~# iwconfig wlan0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Operation not supported.

Could you help me to know how to configure these WiFi settings with the new Wilink8 module please?
- how to activate CONFIG_WIRELESS_WEXT=y kernel option?
- others Linux commands are required to configure WiFi for these usages now?

Thanks in advance for your help.

Best Regards,
Simon
Responses (8)
  • Accepted Answer

    abenete
    abenete
    Offline
    Tuesday, February 09 2016, 11:23 AM - #permalink
    0
    Hi Simon,

    the Wilink8 module doesn't support ad-hoc mode, but it can be configured as an AP for interconnectivity. Also iwconfig can't be used, as you stated in your other post ( https://www.isee.biz/support/questions-about-default-wifi-wilink8-usage-on-igepv2-rf60-boards ). For the module configuration as an access point, you should install and use hostapd on one of the boards.
    Then you must change the wpa_supplicant.conf file on the other boards in order to fit the requirements of the ap you arose:
    network={
        ssid="your_ssid"
        proto=WPA
        key_mgmt=WPA-PSK
        psk="your_password"
    }
    


    Then, for connecting, you should use the following commands:

    ip link set wlan0 up
    wpa_supplicant -Dnl80211 -i wlan0 -c /etc/wpa_supplicant.conf &
    


    You can also use the config you used in /etc/network/interfaces with some changes:
    auto wlan0
    iface wlan0 inet static
    address 192.168.10.1
    network 192.168.10.0
    netmask 255.255.255.0
    


    Hope that helps,

    Alejandro
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, February 09 2016, 02:38 PM - #permalink
    0
    Hello Alejandro,

    Thanks for the help, i understand better now why i encounter problems with using iwconfig wext tools.
    I would like to test the new configurations you adviced me.
    Could you help me to know how it is possible to install hostapd on IGEPv2 please? (zypper, source compilation, yocto build, ...)

    Thanks for your help,
    Simon
    The reply is currently minimized Show
  • Accepted Answer

    egavinc
    egavinc
    Offline
    Wednesday, February 10 2016, 09:34 AM - #permalink
    0
    Hello Simon,
    I have attached a link with hostapd and config file example, you can see the steps to create an AP below.

    https://www.dropbox.com/s/01bl4kbj5qmlvut/hostap-files.tar.gz?dl=0

    root@igep00x0:~# ifconfig wlan0
    wlan0 Link encap:Ethernet HWaddr DE:AD:BE:EF:00:00
    inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    root@igep00x0:~# ifconfig wlan0 down

    root@igep00x0:~# echo 0 > /sys/class/gpio/gpio139/value
    root@igep00x0:~# echo 1 > /sys/class/gpio/gpio139/value
    root@igep00x0:~# hostapd ./hostap-test.conf &

    Best Regards
    Eduard Gavin
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, February 10 2016, 06:23 PM - #permalink
    0
    Hello Eduard,

    Thanks for the hostapd daemon cross-compiled for running on IGEPv2 and config file example, and also the different commands to enable wlan0.
    Using these features, I then managed to configure a WiFi AP on IGEPv2-RF60, on which i can connect from a remote PC.
    WiFi setup is now OK with new IGEPv2-RF60.

    Thanks for all the support.

    Best Regards,
    Simon
    The reply is currently minimized Show
  • Accepted Answer

    jhebert
    jhebert
    Offline
    Friday, November 17 2017, 11:03 AM - #permalink
    0
    Hello,

    I have the same problem like simon.
    So could I have the same link to get the hostapd and config file example please.

    Thanke a lot.

    Best regards
    Gilles Noyon
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 17 2017, 05:27 PM - #permalink
    0
    Hello,

    I attached the requested files to this post (cross-compiled hostapd for IGEPv2 and a hostapd.conf file example that I use), and here is a new link to download them:
    https://www.dropbox.com/s/kmcjoj2cei8wvxj/hostapd_files_sa.tgz?dl=0
    (hostapd.conf has to be used by default in /etc/hostapd.conf if hostapd is started as a daemon, otherwise hostapd can be executed in command line with a conf file as parameter - for example to test it).

    I have to say that this forum and files example were a start point to have Wifi Wilink8 driver working stable on my side. From my experience, the Wilink8 driver is not really stable using kernel 2.6.37 version on revision RF, and I had to migrate IGEPv2 system to kernel 3.17 to have Wifi Wilink8 working correctly.
    I don't know if this forum is a good place to detail the IGEPv2-RF migration steps to work on kernel 3.17. I can start to work on creating a howto for this migration if helps.

    Best Regards,
    Simon
    The reply is currently minimized Show
  • Accepted Answer

    jhebert
    jhebert
    Offline
    Monday, November 20 2017, 11:42 AM - #permalink
    0
    Hello Simon,

    Thanks for your reply.

    Just one question : you said you have to migrate from 2.6.37 kernel to 3.17. I think it is a big jump. But what problems you encountered about the kernel stabilties ?

    I think to realize this operation you needed lot of times ?

    Best regards

    Gilles
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, November 21 2017, 06:07 PM - #permalink
    0
    Hello Gilles,

    Actually I had the following problems with Wifi Wilink8 on IGEPv2-RF kernel 2.6.37:
    - using hostapd, the Wifi AP was appearing on my PC (this make me think you have also to configure a dns server on IGEPv2)
    - on some boards: connexion was possible, but not every time
    - on some other boards: connexion was never possible
    (sorry, I don't have system error logs here..).

    You're right, the migration effort to kernel 3.17 is really a big jump. I had to work on changing bootloader (using u-boot instead xloader), devicetree (that appeared with kernel 3), partitions, generating new rootfs and drivers. For my IGEPv2 usage, I didn't have to port all drivers, but changes were necessary to have all drivers I need to work (not only wifi wilink8 driver then..., for example i had to validate serial port, rs485, usb cdc-acm).
    Using kernel 3.17, Wifi Wilink8 connexion works each time on all boards. I may think that TI validated the ship on more recent kernels than 2.6.37. I picked 3.17 kernel on ISEE recommendation because they started to work on porting system on this kernel, but I'm not sure this is official.
    To have all this new system working on 3.17 kernel, I had strong and reactive support from ISEE (thanks to them!), but I think that all this work took to me around one or two months to have all ok.

    Best Regards,
    Simon
    The reply is currently minimized Show
Your Reply

SUPPORT


This email address is being protected from spambots. You need JavaScript enabled to view it.
This email address is being protected from spambots. You need JavaScript enabled to view it.
IGEP Community Wiki
IGEP Community Forum
IGEP Community Online Chat