Service Patches for PAN1326, AVPR and LE support

Hi Ron,

The PAN1326(CC2564/ENW89823A2KF) does not support Assisted mode even if you apple the patch mentioned below. If you want to use Assisted mode you can use PAN1326B(CC2564B/ ENW89823A3KF).

I hope the patch you are talking about is http://processors.wiki.ti.com/index.php/CC256x_MSP430_Bluetopia_Basic_Demo_APPS#CC256XB_Information , Could you please confirm?

If you want to use the HFP without Assisted mode, I should be possible. But the default demo will not work directly, you need to make the modification to make it work.

The voice data is available at the CC2564 PCM/I2S interface and be aware that you need an external CODEC for HFP. Please see the Datasheet http://www.ti.com/lit/ds/swrs121d/swrs121d.pdf to see the difference between assisted mode and normal mode.

From the software prospective, patches are provided by TI and Stone Street One,  which are listed on the TI wiki.

Without knowing what patch you are referring to and what is the Bluetopia version you are using, it is hard to comment.

But one think is for sure that for the chip you are using you don’t have to apply any patches the default Bluetopia image should work, If you have configured the UART correctly as per the CC256x MSP430 Bluetopia SDK\v1.4 R1\Documentation\ Hardware Porting Guidelines.pdf provided as per of the Bluetopia SDK.

I am referring to the patches at http://processors.wiki.ti.com/index.php/CC256x_Downloads compared to the patch found in CC2564B.h in the SS1 stack.

I am using the SS1 R1.4 stack listed on the TI website.

Hi Ron,

Ok, you are talking about the service packs. The service pack depends on the module you are using.

As I mentioned earlier post  for the chip you are using you don’t have to apply any patches the default Bluetopia image should work, If you have configured the UART correctly as per the CC256x MSP430 Bluetopia SDK\v1.4 R1\Documentation\ Hardware Porting Guidelines.pdf provided as per of the Bluetopia SDK.

 NOTE: there is a new SDK release V1.4 R1.

Yes I am aware of the SDK release V1.4 R1. So you are saying that the PAN1326 patches are the same as the ones listed in the stack for CC2564 ?

If I were to establish an unassisted WB HFP call, you would expect to see encoded samples on the I2S link to the host ?

Ron

Hi Ron,

Yes, but note that they are not patches they are service packs. A service pack is downloaded to initialize the CC256x chip(firmware download). 

Yes, PCM/I2S interface. As mentioned earlier please see the HFP 1.6 Architecture from the datasheet.

You also need to make sure that your PCM/I2S Interface and If Codec is hooked up to the PCM lines, see the link below and also 

http://processors.wiki.ti.com/index.php/CC256x_System_Design_Guide#PCM.2FI2S_Interface

see http://processors.wiki.ti.com/index.php/CC256x_VS_HCI_Commands#HCI_VS_Write_CODEC_Config_.280xFD06.29 for writing the codec configuration.

Ok, so why are the service packs different between the code base and whats on the website and why is the Bluetooth hardware tool not generating any LE packs but the base pack ?

Hi Ron,

As I mentioned earlier The service pack to be used depends on the module you are using.

And If there is a new service pack released with new fixes in it, this will be part of the new release. and also published here http://processors.wiki.ti.com/index.php/CC256x_Downloads 

The Service pack from the above link "CC2564_BT_BLE_SP_BTS" ->"bluetooth_init_cc2564_2.12.bts" includes BLE. So it will be part of the Base patch. 

This is not taking me anywhere. I generated the header file from the SP 2.12 for CC2564 and compared it to whats in the SS1 stack and they are not the same. Is Panasonic/SS1 adding some extras that are not in the SP 2.12 on the TI website ?

Did you check the SP version in the SS1 stack BasePatch[] ?

In my codebase (1.4R1), it reads:

   /* *********************************************************************** */

   /* ************************** Patch RAM Version ************************** */

   /* - Base                                                                  */

   /*   - WL1271L1 (CC256x) BT SP 2.10                                        */

   /* - Add Ons                                                               */

   /*   - XTAL Configuration                                                  */

   /*   - LE Add-On Pack for SP 2.10 (Optional).                              */

   /* *********************************************************************** */

You have downloaded SP v 2.12 from wiki, converted it to an array and comparing it with an older SP. Obviously it will be different.

However, I recommend you to upgrade to BT SP 2.12. You can replace the BasePatch[] from SS1 stack with the one you created.

Panasonic/SS1 does not add anything extra to what you found on the TI website.

Please, can you do the following:

- Download the SP2.10 from TI's wiki.
- Using the Bluetooth hardware tool, generate the header file for the patch.
- Compare this version to what is in the code base.
Here is what I see:

TI generated header:

static BTPSCONST BTPSVEND_PATCH_LOCATION unsigned char BasePatch[] =
{
0x01, 0x36, 0xFF, 0x04, 0x00, 0xC2, 0x01, 0x00, 0x01, 0x37, 0xFE, 0x02, 0x06, 0x0F, 0x01, 0x05, ...

SS1 header for 2.10 in R1.4R1:

static BTPSCONST BTPSVEND_PATCH_LOCATION unsigned char BasePatch[] =
{
0x01, 0x37, 0xFE, 0x02, 0x06, 0x0F, 0x01, 0x05, 0xFF, 0xFF, 0xA0, 0x62, 0x08, 0x00, 0xFA, 0x06,

Supposedly, if I were to ignore the first few bytes which is the HCI command to change the baud rate, look at the data from both files towards the end, they're different !!!!

I have attached the files for your diff'ing pleasure.

0116.2564-210.h6683.CC256X.h

In your previous post, you told you generated the header from SP 2.12 and compared with SS1. They will be totally different.

Like I mentioned in my previous post, the one in TI wiki contains BLE changes in BasePatch [towards the end]. Beginning is a Set Baud Rate command.

I don’t really understand what you are trying to achieve diffing 

FYI : I have done this before my previous post.

Like I mentioned, we have released a new SP (v2.12) and using It , and I recommend that  you do the same.