bluetooth with omap-l138 / wl1271

Hi,

Sorry for the late response.

we don’t support the OMAPL138 with Bluetooth since it has no flow control support (CTS line is used for some other function) and for that reason the HCI level cannot work at all since the HCI layer need the hardware flow control in order to work, so OMAPL138 does not supports Bluetooth.

As for the AM18x platform, it does support Bluetooth. So the question is are you trying to run the BT_Demo.sh script on AM18x EVM and it is not working? Or is it customized board? Since in case it is customized board then maybe there is an issue with the flow control (CTS ,RTS) or the BT Enable signal (GPIO)

Regards,

Eyal

Hi Eyal, thanks for your response,

as I said we are using the OMAPl138 EVM. You said the OMAPL138 doesn't support Bluetooth, but as far as I understood ( tell me if I'm wrong ), this issue can be solved by configuring the kernel. Linux configuration allows to disable McASP, and enable flow control on UART1. After that, there are also some GPIOs that need to be configured properly.

That's why I said in my previous post I use the AM18x SDK with the OMAPL138 EVM. The kernel provided in this SDK is already configured to enable the flow control on UART1. Furthermore, the rootfs provided contains the module gpio_en.ko for the GPIOs configuration. So according to me, using the AM18x SDK with the OMAPL138 EVM should work, since the only difference between the two processors is only the DSP, which is not involved in the bluetooth process.

So I do believe we have some other problem here, or maybe other things I just don't understand properly ?

Thank you for your reply,

Arnaud

Hi Arnaud,

I think you are right, let me put a complete SD card image in FTP site tomorrow that we use to run WLAN and BT on AM18x platform. and please try it on the OMAPL138 EVM that you have and lets see if it works. then if it works then we will figure out how to continue.

I will send the FTP site information tomorrow on that e2e query.

Regards,

Eyal

sorry that your name was underline and red, i was left by the spelling check

No problem, thank you for your reply

Hi Arnaud,

one option is that you have the UART that is attached to the Bluetooth with default frequency (that is 115200) which cannot be modified by the User command, for that I had attached a BTS file that works with the default UART frequency, please replace the one you have in the file system with that one and boot the board and try to bring up the BT again.

the BTS file is:  1641.TIInit_7.2.31.bts     and modify its name to be TIInit_7.2.31.bts

As an alternative please download our Open source images on the AM18x platform to verify if the BT will work.

Please find the link to the SDK image (SD card)  in

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/sdk/AM1x/latest/index_FDS.html  and download the am180x-evm-sdk-bin-05.02.00.00.tar.gz  

Then in order to operate the Bluetooth please visit our WiKi page for instructions in http://processors.wiki.ti.com/index.php/AM37x_Wireless_Connectivity_NLCP_Bluetooth_Terminal

Regards,

Eyal

Hi Eyal, have a look at this !

$ hciattach /dev/ttyS1 texas 115200 &
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_7.2.31.bts
Loaded BTS script version 1
bluetoothd[660]: HCI dev 0 registered
bluetoothd[660]: Listening for HCI events on hci0
bluetoothd[660]: HCI dev 0 up
bluetoothd[660]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
bluetoothd[660]: Could not get the contents of DMI chassis type
bluetoothd[660]: Adapter /org/bluez/660/hci0 has been enabled
Device setup complete

$ hciconfig
hci0:   Type: BR/EDR  Bus: UART
        BD Address: 64:9C:8E:AE:4E:44  ACL MTU: 1021:4  SCO MTU: 180:4
        UP RUNNING PSCAN ISCAN
        RX bytes:1903 acl:0 sco:0 events:43 errors:0
        TX bytes:1206 acl:0 sco:0 commands:34 errors:0

$ hcitool scan --refresh
Scanning ...
        F0:B5:79:08:3D:74    MacBook Pro 13" Core 2 Duo
        4C:E8:FE:52:EA:25    ARNAUD-SYSCOM
        11:11:11:11:11:11    laptop-d630-debian-0

I tried the firmware, and it looks a lot better ! I guess that now, the only thing left is to configure the UART1 properly in the kernel, in order to have a full speed Bluetooth. I guess that it should be easy by looking at the sources of the AM18X SDK. I'll tell you if I have problems with that.

Thanks a lot !

Hi Arnaud,

thanks for the good news :) 

Regards,

Eyal

Hi Eyal,

  I was able to use your 1641.TIInit_7.2.31.bts to get my bluetooth running from a imx53, thanks for making it available.

  Is it possible to get a version of  TIInit_7.2.31.bts that goes at 2.5 MBits/sec?  Is it possible for me to generate one that goes at X baud rate?

  Thanks,

  Rick

Hi Rick,

it will not be possible for you to generate it since the tools for that requires NDA agreement with TI, I will be able to generate it for you however only next week, since we have a holiday now and i am not at work

Regards,

Eyal

Hi Eyal,

  Okay, thanks.  Please post or send a firmware running at about 2.25 MBits/sec.

  Thanks much.

  Rick

Hi Rick

attached please find BTS file for 2.25Mhz clock 6747.TIInit_7.2.31_2.25Mhz.bts please modify the name to TIInit_7.2.31.bts

Regards,

Eyal

Hi Eyal,

Kindly generate an initscript (TIInit_7.6.15.bts) for WL1271L BT with 115200 baudrate. Thanks.

hi everyone,

in the Bluetooth with OMAPL138,  there is a step to insert the module gpio_en.ko.  "$ insmod gpio_en.ko"

I follow the steps in the wiki below, but i cannot get the gpio_en.ko

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

How can i generate gpio_en.ko? I am using ti-dvsdk_omapl138-evm_04_03_00_06

victor

hi,

you can get from here:

git clone git://github.com/TI-ECS/bt_enable.git
cd bt_enable
git reset --hard dd75971705ada8fb0e88a0fb3f68833086c5bba4
patch -p1 < 0001-bt-enable-standalone-makefile.patch
cp ./gpio_en_${PLATFORM_DIR}.c ./gpio_en.c
make DEST_DIR=${ROOTFS} KERNEL_DIR=${KLIB_BUILD}  install || return

patch from:

 http://processors.wiki.ti.com/images/8/8f/Bt-enable-standalone-makefile.zip