TiWi R2 Power-up sequence not happening

GrantHatamosa

Expert 1930 points

Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hi,

We are using the TiWi R2 with out OMAP-L138 SOM board in a custom board.

We notice that the TiWi R2 is not following the power up sequence as documented in LS Research's TiWi R2 datasheet. The issue we are seeing is that the WLAN IRQ is not transitioning to '1' from an initial state of '0' after the WL_EN has been toggled.

Can you please advise us on what is the likely cause of this issue?

over 14 years ago

0 Eyal a over 14 years ago

TI__Genius 9240 points

Hi,

In order to operate the WLAN on the OMAPL138 then you will need to run it from the CLI (serial terminal), since with the first release the GUI is not operational.

After boot type the following:

root@am180x-evm:~#

root@am180x-evm:~# cd /usr/share/wl1271-demos/

root@am180x-evm:/usr/share/wl1271-demos# cd wlan/

root@am180x-evm:/usr/share/wl1271-demos/wlan# ./install-wlan.sh

and then enter the CLI by typing wlan_cu

from the WLAN CU try the following:

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit

.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/

Application scan started

.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

BssId List: Num=2

MAC Privacy Rssi Mode Channel SSID

00.0f.f7.0c.e8.f0 0 -45 Infra 1 ecs123

*00.21.d8.49.c7.40 0 -62 Infra 11 ecs

c ecs

126

TIWLAN: 1203.029260: ************ NEW CONNECTION ************

TIWLAN: 1203.034868: -- SSID = ecs

TIWLAN: 1203.040156: -- BSSID = 0-21-d8-49-c7-40

TIWLAN: 1203.044621: ****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

BssId List: Num=2

MAC Privacy Rssi Mode Channel SSID

00.0f.f7.0c.e8.f0 0 -45 Infra 1 ecs123

*00.21.d8.49.c7.40 0 -62 Infra 11 ecs

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

Status : CONNECTED

MAC : 08.00.28.12.34.56

SSID : ecs

BSSID : 00.21.d8.49.c7.40

Channel : 11

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

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

TiCon_Signal - got signal Ctrl+c ... exiting

Input selection mismatch (0x1)...

[2] + Segmentation fault ./temp/endpoint

root@arago:/usr/share/wl1271-demos/wlan# root@arago:/usr/share/wl1271-demos/wlan# ping 10.2.30.31

PING 10.2.30.31 (10.2.30.31): 56 data bytes

64 bytes from 10.2.30.31: seq=0 ttl=128 time=14.057 ms

64 bytes from 10.2.30.31: seq=1 ttl=128 time=3.340 ms

64 bytes from 10.2.30.31: seq=2 ttl=128 time=3.104 ms

64 bytes from 10.2.30.31: seq=3 ttl=128 time=4.519 ms

Regards,

Eyal

0 GrantHatamosa over 14 years ago in reply to Eyal a

Expert 1930 points

Hi Eyal,

The reason why I've asked the question is because I cannot get the CLI to run.

I've attached the crash dump for your reference.

Fullscreen 6663.crashDump.txt Download

root@arago:~# cd /usr/share/wl1271-demos/wlan/
root@arago:/usr/share/wl1271-demos/wlan# ./install-wlan.sh
Installing WL1271-WLAN kernel modules...
TI WiLink 1271 SDIO: Driver loaded
  Success
TIWLAN: driver init
TIWLAN: 2873.610297:
Zoom2 use external board configuration as well
wifi_probe: got wlan irq 207
wifi_probe: got wlan irq trigger falling flag
  Success
Loading firmware...
Success
Bringing-up the WLAN interface...
pInitParams->RoamingScanning_2_4G_enable 0
hPlatform_DevicePowerOn: timeout waiting for sdio init
kernel BUG at drivers/net/wireless/wilink/SdioDrv.c:342!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c6dd4000
[00000000] *pgd=c6cb4031, *pte=00000000, *ppte=00000000
Internal error: Oops: 817 [#1] PREEMPT
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: tiwlan_drv sdio dm365mmap dsplinkk cmemk ipv6
CPU: 0    Not tainted  (2.6.33-rc4 #48)
PC is at __bug+0x20/0x2c
LR is at schedule+0x2d8/0x360
pc : [<c0031414>]    lr : [<c0340048>]    psr: 60000013
sp : c6dc5c70  ip : 00000000  fp : c6dc5c7c
r10: 000000fb  r9 : c7b71ec8  r8 : c7b71c14
r7 : 00000200  r6 : bf1053f0  r5 : 00000009  r4 : bf133278
r3 : 00000000  r2 : 00000000  r1 : c7ad75e0  r0 : 0000003f
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 0005317f  Table: c6dd4000  DAC: 00000015
Process ifconfig (pid: 1057, stack limit = 0xc6dc4270)
Stack: (0xc6dc5c70 to 0xc6dc6000)
5c60:                                     c6dc5c8c c6dc5c80 bf08a338 c0031404
5c80: c6dc5cb4 c6dc5c90 bf11a078 bf08a310 c7b71ddc c7b71de0 c7b71c14 00000001
5ca0: 00000002 c7b63f00 c6dc5ce4 c6dc5cb8 bf1055a0 bf119fc4 c7b71dd4 c7b71dd8
5cc0: c7b71ddc c7b71de0 c797b9d4 00000000 00000000 c7b71efc c6dc5d14 c6dc5ce8
5ce0: bf104c38 bf105538 bf103d14 c7b71f04 c7b71f08 c6dc5d00 00000001 c7b71e14
5d00: 00000000 00000001 c6dc5d64 c6dc5d18 bf092444 bf104bb4 c7b71f04 c7b71f08
5d20: 00000000 c7bff9c0 00000000 c7b71f08 c7b71f04 c7b71efc c6dc5d64 c7b71e14
5d40: c6dc96d4 c7b71a14 00001002 c7b63a0c 00000000 c7ab0400 c6dc5d84 c6dc5d68
5d60: bf093304 bf092078 c00a2528 c00a2290 c7b71a2c 00000006 c6dc5dac c6dc5d88
5d80: bf106994 bf093180 00001002 c7b63a0c c6dc5dbc c7b71a14 00000006 00000001
5da0: c6dc5dd4 c6dc5db0 bf106c3c bf1068cc bf106a14 bf116ccc bf116af8 c0059164
5dc0: c7b71e14 c6dc96d4 c6dc5dfc c6dc5dd8 bf092e4c bf106b98 00000000 c6dc5de8
5de0: c6dc5e04 c7b63f00 c7ab0400 00001043 c6dc5e14 c6dc5e00 bf116158 bf092d0c
5e00: c7ab0400 bf132948 c6dc5e2c c6dc5e18 c02a2c58 bf116124 c7ab0400 00000041
5e20: c6dc5e4c c6dc5e30 c02a20cc c02a2bac 00000000 00000001 c7b63a00 c6dc5e68
5e40: c6dc5eb4 c6dc5e50 c02e9580 c02a2044 beb23b80 00008914 6c776974 00306e61
5e60: 00000000 00000000 40011043 00000001 00000001 00000000 40011043 00000001
5e80: 00000001 00000000 40011002 beb23b80 00008914 beb23b80 c7bf6500 beb23b80
5ea0: c6dc4000 0008ee74 c6dc5ecc c6dc5eb8 c02eada8 c02e92a0 c7bf6500 00008914
5ec0: c6dc5eec c6dc5ed0 c02900b8 c02eace8 c7bf6500 00008914 beb23b80 c7bf6500
5ee0: c6dc5f0c c6dc5ef0 c00b3834 c028fecc 00000003 c7bf6500 00000003 c7bf6500
5f00: c6dc5f7c c6dc5f10 c00b3f48 c00b3810 c74b1580 c6dc5f38 c6dc5f64 c6dc5f28
5f20: c0291420 c00a6da0 c6dc4000 00000000 00000000 c03d8bcb c7839b00 c74bcc00
5f40: 00000000 00000002 00000003 00000119 c002e0a4 00000003 beb23b80 00008914
5f60: c7bf6500 c002e0a4 c6dc4000 0008ee74 c6dc5fa4 c6dc5f80 c00b3fe4 c00b39c4
5f80: c029200c 00000000 0008eed8 00000004 beb23eb0 00000036 00000000 c6dc5fa8
5fa0: c002df20 c00b3fb4 0008eed8 00000004 00000003 00008914 beb23b80 0008eed8
5fc0: 0008eed8 00000004 beb23eb0 00000036 00001043 00000042 0008ee74 0008d274
5fe0: beb23db0 beb23b60 0000eee4 4018faec 20000010 00000003 00000000 00000000
Backtrace:
[<c00313f4>] (__bug+0x0/0x2c) from [<bf08a338>] (sdioDrv_EnableFunction+0x38/0x50 [sdio])
[<bf08a300>] (sdioDrv_EnableFunction+0x0/0x50 [sdio]) from [<bf11a078>] (sdioAdapt_ConnectBus+0xc4/0xec [tiwlan_drv])
[<bf119fb4>] (sdioAdapt_ConnectBus+0x0/0xec [tiwlan_drv]) from [<bf1055a0>] (busDrv_ConnectBus+0x78/0x160 [tiwlan_drv])
[<bf105528>] (busDrv_ConnectBus+0x0/0x160 [tiwlan_drv]) from [<bf104c38>] (txnQ_ConnectBus+0x94/0xa4 [tiwlan_drv])
 r7:c7b71efc r6:00000000 r5:00000000 r4:c797b9d4
[<bf104ba4>] (txnQ_ConnectBus+0x0/0xa4 [tiwlan_drv]) from [<bf092444>] (drvMain_SmEvent+0x3dc/0x9e0 [tiwlan_drv])
 r7:00000001 r6:00000000 r5:c7b71e14 r4:00000001
[<bf092068>] (drvMain_SmEvent+0x0/0x9e0 [tiwlan_drv]) from [<bf093304>] (drvMain_InvokeAction+0x194/0x1f8 [tiwlan_drv])
[<bf093170>] (drvMain_InvokeAction+0x0/0x1f8 [tiwlan_drv]) from [<bf106994>] (context_DriverTask+0xd8/0xf8 [tiwlan_drv])
 r5:00000006 r4:c7b71a2c
[<bf1068bc>] (context_DriverTask+0x0/0xf8 [tiwlan_drv]) from [<bf106c3c>] (context_RequestSchedule+0xb4/0xbc [tiwlan_drv])
 r6:00000001 r5:00000006 r4:c7b71a14
[<bf106b88>] (context_RequestSchedule+0x0/0xbc [tiwlan_drv]) from [<bf092e4c>] (drvMain_InsertAction+0x150/0x1a4 [tiwlan_drv])
 r5:c6dc96d4 r4:c7b71e14
[<bf092cfc>] (drvMain_InsertAction+0x0/0x1a4 [tiwlan_drv]) from [<bf116158>] (wlanDrvIf_Start+0x44/0x9c [tiwlan_drv])
 r6:00001043 r5:c7ab0400 r4:c7b63f00
[<bf116114>] (wlanDrvIf_Start+0x0/0x9c [tiwlan_drv]) from [<c02a2c58>] (dev_open+0xbc/0x120)
 r5:bf132948 r4:c7ab0400
[<c02a2b9c>] (dev_open+0x0/0x120) from [<c02a20cc>] (dev_change_flags+0x98/0x170)
 r5:00000041 r4:c7ab0400
[<c02a2034>] (dev_change_flags+0x0/0x170) from [<c02e9580>] (devinet_ioctl+0x2f0/0x6a8)
 r7:c6dc5e68 r6:c7b63a00 r5:00000001 r4:00000000
[<c02e9290>] (devinet_ioctl+0x0/0x6a8) from [<c02eada8>] (inet_ioctl+0xd0/0x108)
[<c02eacd8>] (inet_ioctl+0x0/0x108) from [<c02900b8>] (sock_ioctl+0x1fc/0x254)
 r5:00008914 r4:c7bf6500
[<c028febc>] (sock_ioctl+0x0/0x254) from [<c00b3834>] (vfs_ioctl+0x34/0xb4)
 r7:c7bf6500 r6:beb23b80 r5:00008914 r4:c7bf6500
[<c00b3800>] (vfs_ioctl+0x0/0xb4) from [<c00b3f48>] (do_vfs_ioctl+0x594/0x5f0)
 r7:c7bf6500 r6:00000003 r5:c7bf6500 r4:00000003
[<c00b39b4>] (do_vfs_ioctl+0x0/0x5f0) from [<c00b3fe4>] (sys_ioctl+0x40/0x64)
[<c00b3fa4>] (sys_ioctl+0x0/0x64) from [<c002df20>] (ret_fast_syscall+0x0/0x28)
 r7:00000036 r6:beb23eb0 r5:00000004 r4:0008eed8
Code: e1a01000 e59f000c eb0c3a02 e3a03000 (e5833000)
---[ end trace 9dd2b5a8a110d334 ]---
Segmentation fault
Failed
Starting wpa_supplicant..

We are assuming that the kernel panic was related to the TiWi not powering up properly. If you think of another reason for this please do advise us what it is.

Also, we are thinking that due to some level translations that are happening that the TiWi is not power up properly. Is it possible for TI to review our schematics?

Please send me a private email at: ghatamosa@procept.com.au if that is OK.

Regards,

Grant

0 Eyal a over 14 years ago in reply to GrantHatamosa

TI__Genius 9240 points

Hi Grant,

From the log file that you sent i can see that:

hPlatform_DevicePowerOn: timeout waiting for sdio init
kernel BUG at drivers/net/wireless/wilink/SdioDrv.c:342!
Unable to handle kernel NULL pointer dereference at virtual address 00000000

So it might be that the SDIO integration to your platform is not well defined since in that case the SDIO handler gets NULL address.

Are you using the images provided with the OMAPL138 EVM? Or are you trying your own platform? Also Please note the EVM assumes that the WLAN is connected with SDIO using MMC2.

Regards,

Eyal

0 GrantHatamosa over 14 years ago in reply to Eyal a

Expert 1930 points

Hi Eyal,

thank you for your advice. We are looking at the SDIO data lines and we observe that D3 has this ramp up behavior that we believe is causing our communication issues.

I've attached an image showing this problem on the SDIO D3 and I hope that you are able to get some hardware engineer to comment on the possible cause of this issue.

Also, we are using the TiWi01-R2 on our system while the Mistral daughter board have the TiWi01. Is there any problems if we are using a more updated TiWi IC with the Linux driver that clearly has been tested with the TiWi01?

Hoping to hear some advise from your end.

0 GrantHatamosa over 14 years ago in reply to GrantHatamosa

Expert 1930 points

Hi Eyal,

Just want to get you across some updates on our debugging effort, we were able to eliminate the signal I've shown above by setting the TiWi to operate in 1.8V VIO and configuring the PIN as described by this document in the LSR WiKi http://wiki.lsr.com/GetFile.aspx?Page=TiWi&File=TiWi_R2_Pin_Table.xlsx

Now after doing this we get a different console output that seems to go much further now but still will hang up the system.

Below is the crash dump.

root@arago:~# cd /usr/share/wl1271-demos/wlan/
root@arago:/usr/share/wl1271-demos/wlan# ./install-wlan.sh
Installing WL1271-WLAN kernel modules...
TI WiLink 1271 SDIO: Driver loaded
Success
TIWLAN: driver init
TIWLAN: 3524.147559:
Zoom2 use external board configuration as well
wifi_probe: got wlan irq 207
wifi_probe: got wlan irq trigger falling flag
Success
Loading firmware...
Success
Bringing-up the WLAN interface...
pInitParams->RoamingScanning_2_4G_enable 0
mmc1: card claims to support voltages below the defined range. These will be ignored.
mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
mmc1: new SDIO card at address 0001
TIWLAN: Found TI/WLAN SDIO controller (vendor 0x97, device 0x4076, class 0x0)
sdioDrv_WriteSync: sdio error: -84
sdioDrv_WriteSync: sdio error: -84
TIWLAN: 3525.518956: CHIP VERSION... set 1273 chip top registers
TIWLAN: 3525.526673: ***** recovery trigger: BUS_FAILURE *****, ts=-344366825
TIWLAN: 3525.536539: .....drvMain_Recovery, ts=-344366815
sdioDrv_ReadSync: sdio error: -110
TIWLAN: 3525.651633: ***** recovery trigger: BUS_FAILURE *****, ts=-344366700
------------[ cut here ]------------
mmc1: card 0001 removed
WARNING: at drivers/mmc/core/core.c:237 mmc_wait_for_cmd+0x34/0x7c()
Modules linked in: tiwlan_drv sdio dm365mmap dsplinkk cmemk ipv6
Backtrace:
[<c0031730>] (dump_backtrace+0x0/0x114) from [<c033fadc>] (dump_stack+0x18/0x1c)
r7:00000000 r6:c02522dc r5:c040cae2 r4:000000ed
[<c033fac4>] (dump_stack+0x0/0x1c) from [<c0041bd8>] (warn_slowpath_common+0x50/0x68)
[<c0041b88>] (warn_slowpath_common+0x0/0x68) from [<c0041c08>] (warn_slowpath_null+0x18/0x1c)
r7:00000000 r6:c7875400 r5:c6d7bc44 r4:c6d7bc44
[<c0041bf0>] (warn_slowpath_null+0x0/0x1c) from [<c02522dc>] (mmc_wait_for_cmd+0x34/0x7c)
[<c02522a8>] (mmc_wait_for_cmd+0x0/0x7c) from [<c02560c0>] (mmc_io_rw_direct+0xc0/0x130)
r7:00000002 r6:00000001 r5:00000000 r4:c6d7bc44
[<c0256000>] (mmc_io_rw_direct+0x0/0x130) from [<c025701c>] (sdio_disable_func+0x58/0xa0)
[<c0256fc4>] (sdio_disable_func+0x0/0xa0) from [<bf08a38c>] (sdioDrv_DisableFunction+0x3c/0x50 [sdio])
r4:bf133278
[<bf08a350>] (sdioDrv_DisableFunction+0x0/0x50 [sdio]) from [<bf119f90>] (sdioAdapt_DisconnectBus+0x18/0x3c [tiwlan_drv])
[<bf119f78>] (sdioAdapt_DisconnectBus+0x0/0x3c [tiwlan_drv]) from [<bf10551c>] (busDrv_DisconnectBus+0x54/0x60 [tiwlan_drv])
r5:c6c96014 r4:00000000
[<bf1054c8>] (busDrv_DisconnectBus+0x0/0x60 [tiwlan_drv]) from [<bf104ba0>] (txnQ_DisconnectBus+0x14/0x18 [tiwlan_drv])
[<bf104b8c>] (txnQ_DisconnectBus+0x0/0x18 [tiwlan_drv]) from [<bf09281c>] (drvMain_SmEvent+0x7b4/0x9e0 [tiwlan_drv])
[<bf092068>] (drvMain_SmEvent+0x0/0x9e0 [tiwlan_drv]) from [<bf093304>] (drvMain_InvokeAction+0x194/0x1f8 [tiwlan_drv])
[<bf093170>] (drvMain_InvokeAction+0x0/0x1f8 [tiwlan_drv]) from [<bf106994>] (context_DriverTask+0xd8/0xf8 [tiwlan_drv])
r5:00000006 r4:c6c9622c
[<bf1068bc>] (context_DriverTask+0x0/0xf8 [tiwlan_drv]) from [<bf106c3c>] (context_RequestSchedule+0xb4/0xbc [tiwlan_drv])
r6:00000001 r5:00000006 r4:c6c96214
[<bf106b88>] (context_RequestSchedule+0x0/0xbc [tiwlan_drv]) from [<bf092e4c>] (drvMain_InsertAction+0x150/0x1a4 [tiwlan_drv])
r5:c6da0b94 r4:c6c96014
[<bf092cfc>] (drvMain_InsertAction+0x0/0x1a4 [tiwlan_drv]) from [<bf116158>] (wlanDrvIf_Start+0x44/0x9c [tiwlan_drv])
r6:00001043 r5:c6d8a000 r4:c7ada700
[<bf116114>] (wlanDrvIf_Start+0x0/0x9c [tiwlan_drv]) from [<c02a2c58>] (dev_open+0xbc/0x120)
r5:bf132948 r4:c6d8a000
[<c02a2b9c>] (dev_open+0x0/0x120) from [<c02a20cc>] (dev_change_flags+0x98/0x170)
r5:00000041 r4:c6d8a000
[<c02a2034>] (dev_change_flags+0x0/0x170) from [<c02e9580>] (devinet_ioctl+0x2f0/0x6a8)
r7:c6d7be68 r6:c7ada500 r5:00000001 r4:00000000
[<c02e9290>] (devinet_ioctl+0x0/0x6a8) from [<c02eada8>] (inet_ioctl+0xd0/0x108)
[<c02eacd8>] (inet_ioctl+0x0/0x108) from [<c02900b8>] (sock_ioctl+0x1fc/0x254)
r5:00008914 r4:c6c8f700
[<c028febc>] (sock_ioctl+0x0/0x254) from [<c00b3834>] (vfs_ioctl+0x34/0xb4)
r7:c6c8f700 r6:be8a7b80 r5:00008914 r4:c6c8f700
[<c00b3800>] (vfs_ioctl+0x0/0xb4) from [<c00b3f48>] (do_vfs_ioctl+0x594/0x5f0)
r7:c6c8f700 r6:00000003 r5:c6c8f700 r4:00000003
[<c00b39b4>] (do_vfs_ioctl+0x0/0x5f0) from [<c00b3fe4>] (sys_ioctl+0x40/0x64)
[<c00b3fa4>] (sys_ioctl+0x0/0x64) from [<c002df20>] (ret_fast_syscall+0x0/0x28)
r7:00000036 r6:be8a7eb0 r5:00000004 r4:0008eed8
---[ end trace aff7f838d27db398 ]---
------------[ cut here ]------------
WARNING: at drivers/mmc/core/core.c:164 mmc_wait_for_req+0x5c/0x130()
Modules linked in: tiwlan_drv sdio dm365mmap dsplinkk cmemk ipv6
Backtrace:
[<c0031730>] (dump_backtrace+0x0/0x114) from [<c033fadc>] (dump_stack+0x18/0x1c)
r7:00000000 r6:c02521d4 r5:c040cae2 r4:000000a4
[<c033fac4>] (dump_stack+0x0/0x1c) from [<c0041bd8>] (warn_slowpath_common+0x50/0x68)
[<c0041b88>] (warn_slowpath_common+0x0/0x68) from [<c0041c08>] (warn_slowpath_null+0x18/0x1c)
r7:00000000 r6:c7875400 r5:c6d7bc0c r4:c6d7bbe0
[<c0041bf0>] (warn_slowpath_null+0x0/0x1c) from [<c02521d4>] (mmc_wait_for_req+0x5c/0x130)
[<c0252178>] (mmc_wait_for_req+0x0/0x130) from [<c0252314>] (mmc_wait_for_cmd+0x6c/0x7c)
r6:c7875400 r5:c6d7bc44 r4:c6d7bc0c
[<c02522a8>] (mmc_wait_for_cmd+0x0/0x7c) from [<c02560c0>] (mmc_io_rw_direct+0xc0/0x130)
r7:00000002 r6:00000001 r5:00000000 r4:c6d7bc44
[<c0256000>] (mmc_io_rw_direct+0x0/0x130) from [<c025701c>] (sdio_disable_func+0x58/0xa0)
[<c0256fc4>] (sdio_disable_func+0x0/0xa0) from [<bf08a38c>] (sdioDrv_DisableFunction+0x3c/0x50 [sdio])
r4:bf133278
[<bf08a350>] (sdioDrv_DisableFunction+0x0/0x50 [sdio]) from [<bf119f90>] (sdioAdapt_DisconnectBus+0x18/0x3c [tiwlan_drv])
[<bf119f78>] (sdioAdapt_DisconnectBus+0x0/0x3c [tiwlan_drv]) from [<bf10551c>] (busDrv_DisconnectBus+0x54/0x60 [tiwlan_drv])
r5:c6c96014 r4:00000000
[<bf1054c8>] (busDrv_DisconnectBus+0x0/0x60 [tiwlan_drv]) from [<bf104ba0>] (txnQ_DisconnectBus+0x14/0x18 [tiwlan_drv])
[<bf104b8c>] (txnQ_DisconnectBus+0x0/0x18 [tiwlan_drv]) from [<bf09281c>] (drvMain_SmEvent+0x7b4/0x9e0 [tiwlan_drv])
[<bf092068>] (drvMain_SmEvent+0x0/0x9e0 [tiwlan_drv]) from [<bf093304>] (drvMain_InvokeAction+0x194/0x1f8 [tiwlan_drv])
[<bf093170>] (drvMain_InvokeAction+0x0/0x1f8 [tiwlan_drv]) from [<bf106994>] (context_DriverTask+0xd8/0xf8 [tiwlan_drv])
r5:00000006 r4:c6c9622c
[<bf1068bc>] (context_DriverTask+0x0/0xf8 [tiwlan_drv]) from [<bf106c3c>] (context_RequestSchedule+0xb4/0xbc [tiwlan_drv])
r6:00000001 r5:00000006 r4:c6c96214
[<bf106b88>] (context_RequestSchedule+0x0/0xbc [tiwlan_drv]) from [<bf092e4c>] (drvMain_InsertAction+0x150/0x1a4 [tiwlan_drv])
r5:c6da0b94 r4:c6c96014
[<bf092cfc>] (drvMain_InsertAction+0x0/0x1a4 [tiwlan_drv]) from [<bf116158>] (wlanDrvIf_Start+0x44/0x9c [tiwlan_drv])
r6:00001043 r5:c6d8a000 r4:c7ada700
[<bf116114>] (wlanDrvIf_Start+0x0/0x9c [tiwlan_drv]) from [<c02a2c58>] (dev_open+0xbc/0x120)
r5:bf132948 r4:c6d8a000
[<c02a2b9c>] (dev_open+0x0/0x120) from [<c02a20cc>] (dev_change_flags+0x98/0x170)
r5:00000041 r4:c6d8a000
[<c02a2034>] (dev_change_flags+0x0/0x170) from [<c02e9580>] (devinet_ioctl+0x2f0/0x6a8)
r7:c6d7be68 r6:c7ada500 r5:00000001 r4:00000000
[<c02e9290>] (devinet_ioctl+0x0/0x6a8) from [<c02eada8>] (inet_ioctl+0xd0/0x108)
[<c02eacd8>] (inet_ioctl+0x0/0x108) from [<c02900b8>] (sock_ioctl+0x1fc/0x254)
r5:00008914 r4:c6c8f700
[<c028febc>] (sock_ioctl+0x0/0x254) from [<c00b3834>] (vfs_ioctl+0x34/0xb4)
r7:c6c8f700 r6:be8a7b80 r5:00008914 r4:c6c8f700
[<c00b3800>] (vfs_ioctl+0x0/0xb4) from [<c00b3f48>] (do_vfs_ioctl+0x594/0x5f0)
r7:c6c8f700 r6:00000003 r5:c6c8f700 r4:00000003
[<c00b39b4>] (do_vfs_ioctl+0x0/0x5f0) from [<c00b3fe4>] (sys_ioctl+0x40/0x64)
[<c00b3fa4>] (sys_ioctl+0x0/0x64) from [<c002df20>] (ret_fast_syscall+0x0/0x28)
r7:00000036 r6:be8a7eb0 r5:00000004 r4:0008eed8
---[ end trace aff7f838d27db399 ]---
mmc1: card claims to support voltages below the defined range. These will be ignored.
mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
mmc1: new SDIO card at address 0001
TIWLAN: Found TI/WLAN SDIO controller (vendor 0x97, device 0x4076, class 0x0)
TIWLAN: 3526.962108: CHIP VERSION... set 1273 chip top registers
TIWLAN: 3526.970563: Working on a 1273 PG 2.0 board.
TIWLAN: 3526.977852: Starting to process NVS...
TIWLAN: 3526.986853: No Nvs, Setting default MAC address
TIWLAN: 3526.994116: pHwInit->uEEPROMCurLen: 1c
TIWLAN: 3527.006080: ERROR: If you are not calibating the device, you will soon get errors !!!
TIWLAN: 3527.023008: Chip ID is 0x4030111.
TIWLAN: 3527.041352: FEM Type 1
TIWLAN: 3527.258370: Firmware successfully downloaded.
TIWLAN: 3527.264523: FW download OK...
TIWLAN: 3527.281305: Firmware successfully downloaded.
TIWLAN: 3527.286246: FW download OK...
TIWLAN: 3527.292441: Firmware successfully downloaded.
TIWLAN: 3527.297382: FW download OK...
TIWLAN: 3527.307177: Firmware successfully downloaded.
TIWLAN: 3527.313310: FW download OK...
TIWLAN: 3527.319537: Firmware successfully downloaded.
TIWLAN: 3527.326268: FW download OK...
TIWLAN: 3527.332774: Finished downloading firmware.
TIWLAN: 3527.337682: Firmware running.
TIWLAN: 3527.358197: Firmware successfully downloaded.
TIWLAN: 3527.364320: FW download OK...
TIWLAN: 3527.390812:
TIWLAN: 3527.392897: --------------------------------------------------------------------
TIWLAN: 3527.405507: Driver Version : WiLink_Driver_6.1.0.0.144
TIWLAN: 3527.420804: Firmware Version: Rev 6.1.0.0.335
TIWLAN: 3527.425761: Station ID : 08-00-28-12-34-56
TIWLAN: 3527.439742: Interrogate TX/RX parameters
--------------------------------------------------------------------
TIWLAN: 3527.453583:
TIWLAN: 3527.455766: .....drvMain_RecoveryNotify: End Of Recovery, ts=-344364896

0 Eyal a over 14 years ago in reply to GrantHatamosa

TI__Genius 9240 points

Hi Grant,

Based on the log, there are still issues with the SDIO, as can be seen as follows:

sdioDrv_WriteSync: sdio error: -84
TIWLAN: 3525.518956: CHIP VERSION... set 1273 chip top registers
TIWLAN: 3525.526673: ***** recovery trigger: BUS_FAILURE *****, ts=-344366825
TIWLAN: 3525.536539: .....drvMain_Recovery, ts=-344366815
sdioDrv_ReadSync: sdio error: -110
TIWLAN: 3525.651633: ***** recovery trigger: BUS_FAILURE *****, ts=-344366700

However at the end of the log i can see that the driver is brought up and then log that implies that the recovery had ended. what’s now do you have a prompt? are you able to run the CLI (wlan_cu)?

Regards,

Eyal

0 GrantHatamosa over 14 years ago in reply to Eyal a

Expert 1930 points

hi Eyal,

Thank you for the continued support, we are able to get past the installation procedure and invoke wlan_cu successfully.

However when I tried to invoke 's' in the CLI I get this error:

ERROR - IPC_STA_Private_Send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8021501, res = -1, errno = 95)

If I continue on and issue 'b' then 'c [access point name]' I then get this error

c myAccessPoint
2
OK
cmdQueue_Error: **ERROR** Command Occured
                                        Cmd = CMD_DISCONNECT , Len = 12
                                        NumOfCmd = 5
                                        MAC TimeStamp on timeout = -344285900
TIWLAN: 3606.473968: --------------- cmdQueue_PrintHistory of 5 -------------------
TIWLAN: 3606.482321: Cmd index 0 CmdType = CMD_DISCONNECT , Len = 12, Place in Queue = 26
TIWLAN: 3606.490964: Cmd index 1 CmdType = CMD_START_JOIN , Len = 60, Place in Queue = 25
TIWLAN: 3606.499028: Cmd index 2 CmdType = CMD_CONFIGURE (DOT11_CUR_TX_PWR) , Len = 8, Place in Queue = 24
TIWLAN: 3606.509051: Cmd index 3 CmdType = CMD_SET_TEMPLATE , Len = 264, Place in Queue = 23
TIWLAN: 3606.521877: Cmd index 4 CmdType = CMD_SET_TEMPLATE , Len = 264, Place in Queue = 22
TIWLAN: 3606.530192: -----------------------------------------------------------------------

Can you please clarify what these error messages indicate?

0 Eyal a over 14 years ago in reply to GrantHatamosa

TI__Genius 9240 points

Hi,

In the log that you provided I can see 2 kind of issues, the first one is: ERROR - IPC_STA_Private_Send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8021501, res = -1, errno = 95)

The user space is interacting with the kernel space (WLAN driver) with Wext commands and with private commands that are carried out on dedicated Wext, and in that case the ioctl (wext) command sent from the user space to the Driver failed. And in that case it is (SCAN_CNCN_START_APP_SCAN = SET_BIT | SCAN_CNCN_PARAM | 0x01 | ALLOC_NEEDED_PARAM,) “start application scan” command that failed.

Then going below the log we can see the following:

cmdQueue_Error: **ERROR** Command Occured

Cmd = CMD_DISCONNECT , Len = 12

NumOfCmd = 5

MAC TimeStamp on timeout = -344285900

TIWLAN: 3606.473968: --------------- cmdQueue_PrintHistory of 5 -------------------

TIWLAN: 3606.482321: Cmd index 0 CmdType = CMD_DISCONNECT , Len = 12, Place in Queue = 26

TIWLAN: 3606.490964: Cmd index 1 CmdType = CMD_START_JOIN , Len = 60, Place in Queue = 25

TIWLAN: 3606.499028: Cmd index 2 CmdType = CMD_CONFIGURE (DOT11_CUR_TX_PWR) , Len = 8, Place in Queue = 24

TIWLAN: 3606.509051: Cmd index 3 CmdType = CMD_SET_TEMPLATE , Len = 264, Place in Queue = 23

TIWLAN: 3606.521877: Cmd index 4 CmdType = CMD_SET_TEMPLATE , Len = 264, Place in Queue = 22

TIWLAN: 3606.530192: -----------------------------------------------------------------------

Which indicate that the command Disconnect was sent from the Driver to the firmware (that is running on the ARM located in the 1271 chip) however the firmware did not acknowledge receiving that command and then there is a list of other commands that are still in the queue waiting to be transferred to the firmware. That issue may be caused due to issues in the SDIO or because the firmware did not respond to that command for some unclear reason.

Regards,

Eyal

0 GrantHatamosa over 14 years ago in reply to Eyal a

Expert 1930 points

hi eyal,

is there a way to confirm if the firmware is working properly other than to initiate a scan?

Also, how do you enable more debug messages in the wlan_cu so that I can get more information as to what is happening rather than just the error status.

0 Eyal a over 14 years ago in reply to GrantHatamosa

TI__Genius 9240 points

Hi Grant,

In order to get more logs from the Driver you can enable the “#define PRINTF_ROLLBACK” that is located at report.h file and then enable more logs from the CLI, you can get the information for that from http://processors.wiki.ti.com/index.php/OMAP35x_Wireless_Connectivity_WL1271_Command_Line_Interface_(CLI)_User%27s_Guide#Report_Menu

However it looks like there is an issue with the SDIO, since the firmware was fully tested, and I expect for firmware stuck. The way to perform it is to write a user application that will read and write from the 1271 chip via the SDIO, the read/write can be from address 0x8, also I suggest writing that application to write then read from address 0x8 in a loop, and each time to verify if the read value is equal the write Value.

As for the SDIO driver you can use the SDIO driver that was supplied in the release.

Regards,

Eyal

0 Eyal a over 14 years ago in reply to Eyal a

TI__Genius 9240 points

I had a typo mistake in previous response, I meant that since the firmware was fully tested, then I don’t expect such a firmware stuck

Regards,

Eyal

0 GrantHatamosa over 14 years ago in reply to Eyal a

Expert 1930 points

Hi Eyal,

We finally are able to get the TiWi module working. We end up having to switch the VIO operation of the OMAP-L138 to 1.8V to get it to work.

We still don't know if it is even possible to use the TiWi with a 3.3V system via level shifters.

Regards,

Grant

0 Eyal a over 14 years ago in reply to GrantHatamosa

TI__Genius 9240 points

Hi,

right.... I think there is a new revision that supports 3.3V rather then 1.8V, you might try that since it is very complicated to handle 1.8V SD cards as they are expensive and les stable

Regards,

Eyal

0 GrantHatamosa over 14 years ago in reply to Eyal a

Expert 1930 points

Do you have a link to said TiWi device which supports 3.3V? Or is this device still in development?

Wi-Fi

Wi-Fi forum

TiWi R2 Power-up sequence not happening