Provide WiFi support on Android ICS with Nitrogen6 iMx6Q board.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Provide WiFi support on Android ICS with Nitrogen6 iMx6Q board.

3,539 Views
girishadengi
Contributor I

Hi All,

I am using iMx6Q development board from boundary devices (Nitrogen6).

This development board has LS Research TIWi-2 WiFi+BT module.

As of now, there is no official support for WiFi on iMx6Q from Boundary device or from Freescale.

Can anybody please provide me a driver patch/module to WiFi support on iMx6Q.

Thanks and regards,

Girisha Dengi.

0 Kudos
10 Replies

1,055 Views
girishadengi
Contributor I

Hi All,

Any update on WiFi support for Nitrogen6 board (on Android - ICS).

Thanks in advance.

--Girisha Dengi.

0 Kudos

1,054 Views
EricNelson
Senior Contributor II

Hi Girisha,

Wifi is now up in our repositories, though not yet Bluetooth. If you've already agreed to our EULA and sent us your SSH key, you can grab and build it like so:

~/$ mkdir myandroid
~/$ cd myandroid
~/myandroid$ repo init \
   -u git://github.com/boundarydevices/imx-android-r13.4-ga.git \
   -b nit6x-wifi
~/myandroid$ repo sync
~/myandroid$ . build/envsetup.sh
~/myandroid$ lunch 4
~/myandroid$ m 2>&1 | tee build.out

If you already have the previous release, you can save some download time by switching to the nit6x-wifi branch like so:

~/myandroid$ repo init -b nit6x-wifi
~/myandroid$ repo sync
0 Kudos

1,055 Views
kunalsrivastav1
Contributor I

Hi Eric,

Do you have any updated patches for the TI Wifi support on Nitrogen 6x board ?

We are using and have integrated the Wifi driver files (Android ICS) out of your Nitrogen 6x repo source.

And we are facing some issues on the Wifi connectivity.

Issue:

We can see regular small duration disconnection when connected to a Wifi network. And then it immediately connects back and then same issue repeated after some interval.

The interval of disconnection varies and sometimes it starts happening after long time (Testing for > 1/2 Hour).

From Android Wifi settings application:

When the device is disconnected and connected, we can see the network showing status as below within 2 secs interval.

> Disconnected

> Obtaining IP address..

> Connected

"Ping" test from android terminal:

We did a continuous "ping" test from the android terminal on the Nitrogen board 6x board connected

to a stable Wifi network (We have one reference board which does not show any disconnection on this network)

> ping google.com

.

.

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=98 ttl=53 time=31.9 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=99 ttl=53 time=29.6 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=100 ttl=53 time=840 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=101 ttl=53 time=29.6 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=102 ttl=53 time=30.4 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=103 ttl=53 time=30.6 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=104 ttl=53 time=32.1 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=105 ttl=53 time=35.7 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=106 ttl=53 time=33.1 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=107 ttl=53 time=40.3 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=108 ttl=53 time=29.6 ms

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

wl1271: WARNING corrupted packet in RX with status: 0x1

From 192.168.255.249 icmp_seq=143 Destination Host Unreachable

From 192.168.255.249 icmp_seq=143 Destination Host Unreachable

ping: sendmsg: Network is unreachable

ping: sendmsg: Network is unreachable

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=118 ttl=53 time=31.9 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=119 ttl=53 time=29.6 ms

64 bytes from maa03s04-in-f14.1e100.net (74.125.236.46): icmp_seq=120 ttl=53 time=840 ms

..

.




I will create and attach a full log file.

Thanks & Best Regards,

Kunal

0 Kudos

1,055 Views
girishadengi
Contributor I

Hi Eric,

Thank you so much for your response and support.

I will try out to bring up the wifi on iMx6 and let you know for any feedback or suggestions from you.

Thank you for your time.

--Girisha Dengi.

0 Kudos

1,055 Views
EricNelson
Senior Contributor II

Hi Girisha,

We have WiFi and Bluetooth up and running in the office, but have a bit more testing to do before releasing it.

We expect to have a release by the end of next week.

0 Kudos

1,055 Views
michaeldiamond
Contributor III

I am trying to get the module to calibrate but do have the module working.

     make sure you use boundary devices kernel and bootloader image, not the one the freescale provides.

     in the kernel you need to enable the driver for the wifi module. (wl12xx) and the model is wl127x.

Here is an email from boundary that helped me get started.

You need the files from /lib/firmware/ti-connectivity before you can start up the device, but I think you should see the device if you run 'ifconfig -a'.

>

> The canonical place to get them is from linux-firmware:

>     http://linuxwireless.org/en/users/Drivers/wl12xx#Firmware

Here is some info from boundary devices. http://boundarydevices.com/i-mx6q-linux-release-3-0-35_1208-beta/

Quick notes on testing Wi-Fi with the 2012-08-Beta kernel on a Nitrogen6X board with WiFi option:

root@freescale ~$ modprobe wl12xx_sdio

root@freescale ~$ ifconfig wlan0 up wl1271: firmware booted (Rev 6.1.5.50.74)

root@freescale ~$ root@freescale ~$ iwlist wlan0 scan wlan0

Scan completed : ... Cell 01 - Address: 00:19:70:86:8C:31 Channel:11 Frequency:2.462 GHz (Channel 11) Quality=35/70 Signal level=-75 dBm Encryption key:on ESSID:"Wireless" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=00000001550e5771 Extra: Last beacon: 1650ms ago IE: Unknown: 0008576972656C657373 IE: Unknown: 010882848B960C121824 IE: Unknown: 03010B IE: Unknown: 2A0100 IE: Unknown: 32043048606C IE: Unknown: DD180050F2020101820003A4000027A4000042435E0062322F00 IE: Unknown: DD0900037F01010000FF7F IE: Unknown: DD0A00037F04010000004000

root@freescale ~$ iwconfig wlan0 mode managed essid Wireless key HEXVALUE

root@freescale ~$ wl1271: Association completed.

root@freescale ~$ udhcpc -f -q -n -i wlan0 udhcpc

(v1.20.2) started Sending discover... Sending select for 192.168.0.150... Lease of 192.168.0.150 obtained, lease time 86400 Deleting routers adding dns 204.130.255.3 adding dns 209.63.0.6

If your access point requires wpa encription you will need to install wpa_supplicant in ltib and then use the following post to help you.

ltib wpa_supplicant

let me know if you still have any questions.

0 Kudos

1,055 Views
girishadengi
Contributor I

Hi Michael,

Thanks for your response.

As per your instructions and the guide lines provided by the Boundary devices, now I am able to get WiFi on iMx6 with Linux and its working fine.

But my final goal is to bring up the WiFi on Android ICS.

As of now there is no official support of WiFi on Android ICS from the Boundary devices.

Is there any way to bring up the WiFi on Android or Can we follow the same procedure as Linux to bring up the WiFi on Android ?

If you any idea or feedback for bringing the WiFi on Android ICS, please let me know.

Thank you for your time.

--Girisha Dengi.

0 Kudos

1,055 Views
EricNelson
Senior Contributor II

Hi Grisha,

As discussed in http://boundarydevices.com/android-r13-4-stage-3/, we had some infrastructure needs to work through before we could address a set of changes as large as changing the Wi-Fi adapter in the R13.4 code base, but we are planning to provide full ICS support.

As Michael mentioned, the first part(s) are getting the modules and firmware installed. The remainder involves a handful of bindings for the Network Manager and some init scripts to start the proper daemons.


If you walk through the Freescale patches, you'll find a number of patches that add support for the Atheros chip-set. The need is essentially to remove all of those and replace them with the TiWi equivalents.

The good news is that the TiWi pieces are largely in AOSP already. We just need to configure them.

Because of other schedule pressures, I expect this to take a couple of weeks.

0 Kudos

1,055 Views
girishadengi
Contributor I

Hi Eric,

I am still not able to get wifi working on Nitrogen6 board.

Is there any good chance of hope to get wifi support from you guys within this week.

Eagerly waiting for wifi support on imx6 Android ICS.

Thank you for your time.

--Girisha Dengi.

0 Kudos

1,055 Views
michaeldiamond
Contributor III

I am not using android so I wouldn't know how to answer your questions there.  I would start with making sure the drivers are installed in the android kernal from boundary.

0 Kudos