This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2560B: Bridge 2 eSCO connections

Part Number: CC2560B

Hi Team,

I am a newbie. I am trying to bridge 2 eSCO connection on bluetooth chip. The details of the connection are as follows,



To bridge both these eSCO, I am using the following command,

hcitool -i hci0 cmd 0x3f 0x0106   0x00 0x01 0x00 0x40 0x1F 0x00 0x00 0x00 0x00 0x00 0x00   0x00   0x10 0x00 0x10 0x00 0x00 0x10 0x00 0x00 0x00 0x01   0x00   0x10 0x00 0x00 0x00 0x00 0x10 0x00 0x10 0x00 0x01   0x00

clock rate = 0x0100 // sample-rate * 32 / 1000
clock-direction/role = 0 // PCM rol master
frame-sync freq = 8000 // 8Khz
frame-sync duty cycle = 0 // 50% duty-cycle (I2S format)
frame-sync edge = 0 // sample at rising edge
frame-sync polarity = 0 // active high

Reserved = 0 // Reserved

chan1 data out size = 16 // 16 bits per channel
chan1 data out offset = 16 // swap channel positions on Data Out pin
chan1 out edge = 0 // Out data driven at rising edge (0) of the PCM clock
chan1 data in size = 16 // 16 bits per channel
chan1 data in offset = 0 // keep the correct channel positions on Data In pin
chan1 data in edge = 1 // In data sampled at falling edge (1) of the PCM clock

Fsync multiplier = 0 // This field is only relevant to CC256XB from SP 0.2 !!!

chan2 data out size = 16 // 16 bits per channel
chan2 data out offset = 0 // swap channel positions on Data Out pin
chan2 out edge = 0 // Out data driven at rising edge (0) of the PCM clock
chan2 data in size = 16 // 16 bits per channel
chan2 data in offset = 16 // keep the correct channel positions on Data In pin
chan2 data in edge = 1 // In data sampled at falling edge (1) of the PCM clock

Reserved = 0 // Reserved

Just after this we are also setting the Link Policy,

hcitool -i hci0 cmd 0x02 0x000f 0x06 0x00

HCI_Write_Default_Link_Policy_Setting: Disable Role-Switch, Enable Hold-Mode, Enable Sniff-Mode

When I run this, my assumption is both eSCO should be able to transfer SCO data with each other. But this does not happen.

1. Does this configuration has something to do with the type of link eSCO/SCO?

2. The configuration which I am sending, Is it correct?

3. Instead of both connection being eSCO, I made one SCO connection as well but still no luck.