BP-CC3301: BT is missing in CC33XX by using v00.04.02.00

Dear Sirs:

  I do more tests on the issue:

1. If we try to modify the dts as in the v1.3.2 driver, the /dev/ttyS1 does show up, and the hciconfig or hcitool also show the interface, but the final result is the same.

2. If we try to use SDIO inband interrupt in dts instead of external interrupt in the system, the result is the same.

Regards,

/ckhsu

Dear Sirs:

It is confirmed to be a CC3301 which is a WiFi+BLE chip.

Regards,

/ckhsu

Hi,

I've assigned this to one of our Bluetooth SW engineers, please allow until tomorrow for a reply.

Shlomi

Dear Sir:

  Thank you.

  For your information, our latest BP-CC33X1 board in hand for PG2.0 is Rev E3 printed on PCB.

Regards,

/ckhsu

Hi,

It seems as though the Device uart is not being picked up by the Beaglebone. I want to make sure the reworks needed in the beaglebone adapter for the CC3301 is correct. The reworks look like the following.

I have just tested running the scripts on a setup with an OOB distribution and it worked properly.

Kind Regards,

Rogelio

Hi Rogelio:

  Ok, it seems the BP-CC33-BBB-ADAPT need modification.

  Can you let me know where can I find the detail hardware modification inside the document?

Regards,

/ckhsu

Hi Rogelio:

  Based on your picture for BP-CC33-BBB-ADAPT, I try to compare the BoosterPack header assignment inside the SDK document in docs/html/CC33XX/BP-CC3301_HW_UserGuide.html

This is PG2 Rev E3(00.04.02.00)

This is PG1 MCU107E1(R1.2)

Inside the 00.04.02.00,

1. The UART_CTS in table is written as P2.37 but the graph link in header P2.36

2. The UART_RTS in table is written as P2.36 but the graph link in header P2.35

3. The IRQ_BT in table is written as P2.11 but missing in the graph and shows COEX_PRIORITY  P1.30

Before I got the schematics of Rev E3 from TI, I suppose UART_CTS should be P2.37, UART_RTS should be P2.36, and IRQ_BT should be P2.11.

Am I correct?

And here comes my question:

Are the modifications of the BP-CC33-BBB-ADAPT for PG1 should change the UART_CTS and UART_RTS to reverse order to fit the PG2? Are these the modifications show on your pictures?

Regards,

/ckhsu

Hi Rogelio:

  It seems my assumption is something incorrect or the UART RTS/CTS MUST be enabled. Looking forward for the modification on the BP-CC33-BBB-ADAPT.

  My verifying process are as below:

  1. I thought if only the RTS/CTS is wrong, then I try to create a new cc33xx-conf.bin based on the one inside /lib/firmware/ti-connectivity by using cc33xxconf.

  2. I dump the /lib/firmware/ti-connectivity/cc33xx-conf.bin into a conf file by following the README of cc33xxconf and using /usr/sbin/cc33conf/cc33xxconf.

  3. Then I modify the field core.enable_FlowCtrl from 1 to 0 and recreate the cc33xx-conf.bin.

  4. I put the new conf file as /lib/firmware/ti-connectivity/cc33xx-conf.bin and reboot.

  After that, I see below:

The hci interface created by btti_uart but no RX from CC3301.

  However the dmesg shows that I CANNOT disable the flow control or the BLE will not work.

  And to confirm my CC3301 Rev E3 is good in chip side, and the driver is working. I try to recompile the kernel described inside the document and modify dts with BLE over SDIO and reuse the original cc33xx-conf.bin.

  I can see the below hci interface:

And

This imply the Rev E3 is working in chip/driver side.

And by using the below commands

btmgmt -i hci0 info
btmgmt -i hci0 power off
btmgmt -i hci0 le on
btmgmt -i hci0 connectable on
btmgmt -i hci0 bondable off
btmgmt -i hci0 pairable off
btmgmt -i hci0 privacy off
btmgmt -i hci0 name cc33xxble
btmgmt -i hci0 advertising on
btmgmt -i hci0 power on

  I can see the ble on the mobile side

  This implies the Rev E3 board is totally working, now our only work is to make the UART to be okay through BP-CC3301 Rev E3 to BP-CC33-BBB-ADAPT and BBB board.

Regards,

/ckhsu