I am using the wl1271 within the LSi TiWi-R2 module mounted on the Boundary Devices nitrogen6x board. I have gotten BT to initialize and work for testing purposes. However, if WiFi seems to be initializing a connection during startup the BT init seems to fail. Even when BT claims, "Device init complete" an "hcitool scan" reports:
"/ # hcitool scan # Scan for devices
Scanning ...
hci_cmd_timer: hci0 command tx timeout
Inquiry failed: Connection timed out
"
then fails.
If I wait some time for the WiFi connection to succeed, then I initialize BT everything works.
1. Are there times when WiFi and BT don't play well together? Should I avoid initializing each interface during certain operations or times during system initialization?
a) If so, how should the initialization of WiFi/BT be serialized?
b) If NOT, then what could be causing this apparent conflict?
BT Initialization is as follows:
bluetoothd
# Toggle BT_EN
echo 176 >/sys/class/gpio/export
echo low >/sys/class/gpio/gpio176/direction
sleep 1 # is needed here if you write a script
echo high >/sys/class/gpio/gpio176/direction
# Initialize the BT interface
hciattach -t 30 -s 115200 /dev/ttymxc2 texas 2000000 flow
hciconfig hci0 up
WiFi wpa_supplicant init:
/usr/sbin/wpa_supplicant -d -Dwext -c /media/mmcblk1p1/wifi/wpa_supplicant.conf -iwlan0 -B
I have tried to initialize the above code prior to and after doing an "ifup wlan0" and starting the wpa_supplicant. Neither approach showed any benefit.
Any suggestions would be much appreciated.
Linux Kernel version: 3.0.35
/ # calibrator get drv_info wlan0
Driver wl1271_sdio
version 3.0.35-nitro+
FW version Rev 6.1.5.50.74
Bus info mmc2:0001:2
HW version 0x4030111