Bluetooth not working on WL1835MOD

Hi Ankur,

First of all, this forum is meant for CC256x.

To answer your question,

I hope you have taken the Kernel changes to enable TI-BBW cape from the below link. 

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

Also you can try using the default images provided for BB + bluetopia addon in the above link.

Hello Sundeep,

Sorry for posting here.

Thanks for your message, Yes, I am using the TI-BBW cape rootfs.tar.gz and boot.tar.gz available. But still I am having the same issue.

Regards,

Ankur

Hi Ankur,

It looks to me like either the GPIO is not configured correctly or Init script is not loaded correctly

I hope you have replaced the init script(TIInit_11.8.32.bts) in the location "/lib/firmware" as per the below ink

http://processors.wiki.ti.com/index.php/WL18xx_Bluetopia_Platform_Manager_Demo_Guide#Software

and for GPIO I suggest that you can do a build having all the below changes considered using SDK06.00.00.00(http://processors.wiki.ti.com/index.php/Bluetooth:_Stonestreet_One_Build_Process)

From the link http://processors.wiki.ti.com/index.php/WL8_release_download_page

Also see: http://processors.wiki.ti.com/index.php/StoneStreet_One_Bluetopia_Platform_Manager_Bluetooth_Stack_for_TI_WL18xx#Installing_Bluetopia_Platform_Manager

Hello Sundeep,

Thank you for taking interest.

I have placed the firmware binary under /lib/firmware. Here is the output:

root@am335x-evm:/lib/firmware# ls

LICENCE TIInit_11.8.32.bts TIInit_7.2.31.bts ti-connectivity

TIInit_10.6.15.bts TIInit_12.8.32.bts TIInit_7.6.15.bts

And, I might do have downloaded the correct rootfs and kernel binary from the http://www.ti.com/tool/linuxezsdk-am335x-wilink8 "LINUXEZSDK-WILINK8-BT-BB", as on the board I have WiFi working and the patch includes enabling of both WiFi and BT.

Feel free to share if you need further debug info to get closer to the issue, I am happy to provide it.

Regards,

Ankur.

Hi Ankur,

Thanks you for bringing it to our notices.

We were able to see the same issue as you mentioned with the latest BBW boards.

I have informed the respective team to look in to the issue(they suspect that the new BBW UART interface is moved to UART 1, where the images is based on the UART4. which is causing the issue).

We will have a solution soon, please stay tuned.