WL1271 Porting

parth shah

Other Parts Discussed in Thread: WL1271, OMAP3530

Hello,

We are using jorjin module WG7310. Is it possib;e to port WL1271 driver on any other platform(samsung or Freescale) rather than OMAP?

We have Linux SDK for WL1271. Can we cross compile those and add the drivers in our BSP?

Thanks,

Parth

over 14 years ago

0 Eyal a over 14 years ago

TI__Genius 9240 points

Hi Parth,

in order to port the WLAN to other platforms, you will have to take care of the porting to the hardware interfaces, that is the 1271 works with SDIO for WLAN, in addition to the MMC (SDIO) there are 2 more GPIOs that one is WLAN_EN (wlan enable) and IRQ line, for Bluetooth there is a need to bring up the UART with CTS/RTS as well to support Bluetooth flow control.

beside that the driver we have work on Linux 2.6.37, so in case you work with different linux version then the porting should be done as well for example the network stack, GPIO support and so on, however that you will discover on compilation.

Regards,

Eyal

0 ramakumar badipatla over 13 years ago in reply to Eyal a

Prodigy 55 points

Iam porting Wl1271 to OMAP3730 board . i enabled two GPIO pins WL_EN and WL_IRQ. we are using mmc2 port for SDIO. iam getting following error .

TIWLAN: 1015.121785: -----------------------------------------------------
TIWLAN: 1015.128468: Driver Version : WiLink_Driver_6.1.0.0.144
TIWLAN: 1015.134267: Firmware Version: Rev 6.1.0.0.335
TIWLAN: 1015.139180: Station ID      : 08-00-28-72-85-37
TIWLAN: 1015.144276: -----------------------------------------------------
TIWLAN: 1015.150929:

tiwlan: 10 sec os_SignalObjectWait timeout
TIWLAN: 1030.117604: cmdQueue_Error: **ERROR** Command Occured
                                        Cmd = CMD_TEST , Len = 80
                                        NumOfCmd = 1
                                        MAC TimeStamp on timeout = 1792031480
TIWLAN: 1030.141103: --------------- cmdQueue_PrintHistory of 5 -------------------
TIWLAN: 1030.148549: Cmd index 0 CmdType = CMD_TEST , Len = 80, Place in Queue = 0
TIWLAN: 1030.156056: Cmd index 1 CmdType = CMD_RESET , Len = 0, Place in Queue = 29
TIWLAN: 1030.163655: Cmd index 2 CmdType = CMD_RESET , Len = 0, Place in Queue = 28
TIWLAN: 1030.171224: Cmd index 3 CmdType = CMD_RESET , Len = 0, Place in Queue = 27
TIWLAN: 1030.178822: Cmd index 4 CmdType = CMD_RESET , Len = 0, Place in Queue = 26

Please give me some suggestion........

0 Elad Raz92038 over 13 years ago in reply to ramakumar badipatla

Expert 1585 points

Hi Ramakumar.

It's seems like the WLAN_IRQ don't fire the OS. Can you please check:

1. Using a scope/logic if the HW WLAN_IRQ is getting trigger (default is falling edge)

2. Check the IRQ registration code in the kernel. (BTW his OS are you working on?)

Elad

0 ramakumar badipatla over 13 years ago in reply to Elad Raz92038

Prodigy 55 points

Hi Elad

thank you...

Now its working .... problem related to configuring WLAN_IRQ GPIO

Regards

-------------

Ramakumar Badipatla.

0 Chris Read over 13 years ago in reply to ramakumar badipatla

Genius 3345 points

What was the configuration change you had to make?

Thanks,

Chris

0 Chris Read over 13 years ago in reply to Chris Read

Genius 3345 points

I had forgotten that you have to configure those GPIOs (which ones and their PADCONF/pinmux values) in host_platform.h and host_platform.c in the directory V3.00.01.06-WL6.1.6.0.3/software/OMAP35x_WL1271_6.1.0.1.149/Sources/wireless/WiLink/platforms/hw/host_platform_omap3530/linux

0 Eyal a over 13 years ago in reply to Chris Read

TI__Genius 9240 points

Hi,

Is there still an issue, or can we close that Query?

Regards,

Eyal

0 Chris Read over 13 years ago in reply to Eyal a

Genius 3345 points

It seems to me that the way I have to configure the PADCONF registers and allocate and define the GPIOs for enable and IRQ is less than ideal. The driver has to be modified for each board.

I would think the allocation/configuration/pinmuxing should be put in the board file (board-omap3evm.c in arch/arm/mach-omap2/ for example), and that the driver would use those. Is there any plan to move in that direction?

- Chris

0 Eyal a over 13 years ago in reply to Chris Read

TI__Genius 9240 points

Hi Chris,

we are implementing the pinmuxing in the board file, we have some examples in the WiKi page. please see:

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

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

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

Regards,

Eyal

0 Chris Read over 13 years ago in reply to Eyal a

Genius 3345 points

Thanks, Eyal. That looks good.

Does that mean you're going to remove the pinmuxing setup from the driver?

Are you also moving toward specifying the power enable and IRQ in the board file?

Thanks,

Chris

0 Eyal a over 13 years ago in reply to Chris Read

TI__Genius 9240 points

Hi Chris,

The WiKi page I sent are the way we work with the latest Drivers which are based on Open source driver, and we have no plans to do the same for the Legacy driver, that will remain as it is although I agree with you that it is not the optimal way to do it

Regards,

Eyal

Wi-Fi

Wi-Fi forum

WL1271 Porting