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.

Btool, 2 Connections with 1 Central possible?

Other Parts Discussed in Thread: CC2650, CC2541, CC2650STK, BLE-STACK, CC2640

Hi everyone,

I try to get a Connection with two CC2650 with TestHost app and one mobilphone.

One cc2650 is central and one peripheral.

I can connect to each of them, but not at the same time. I use the 2.2 Stack and try to make a connection with btool.

My Question is: Is it possible to get a connection with two devices with TestHost-app/Btool?

What is the configuration?

cc2650 peripheral-steps:

reboot->GAP_DeviceInit(disable Central and enable peripherals)->GAP_UpdateAdervtisingData->GAP->MakeDiscoverable

(Advertising with public ID)

mobilephone steps:

Advertising with random ID

cc2650 central-steps:

reboot-> scan->establish withfirst device-> try to establish with second device and get "GAP_EstablishLinkRequest Failed. There are no Resouces Available".

The Output of the central cc2650

[1] : <Tx> - 02:03:03.979

-Type : 0x01 (Command)

-OpCode : 0xFE09 (GAP_EstablishLinkRequest)

-Data Length : 0x09 (9) byte(s)

HighDutyCycle : 0x00 (0) (Disable)

WhiteList : 0x00 (0) (Disable)

AddrTypePeer : 0x00 (0) (Public)

PeerAddr : 68:C9:0B:08:55:0D

Dump(Tx):

0000:01 09 FE 09 00 00 00 0D 55 08 0B C9 68 ........U...h

--------------------------------------------------------------------

[2] : <Rx> - 02:03:03.999

-Type : 0x04 (Event)

-EventCode : 0x00FF (Event)

-Data Length : 0x06 (6) bytes(s)

Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)

Status : 0x00 (0) (Success)

OpCode : 0xFE09 (GAP_EstablishLinkRequest)

DataLength : 0x00 (0)

Dump(Rx):

0000:04 FF 06 7F 06 00 09 FE 00 .........

--------------------------------------------------------------------

[3] : <Info> - 02:03:04.067

Device Connected

Handle = 0x0000

Addr Type = 0x00 (Public)

BDAddr = 68:C9:0B:08:55:0D

--------------------------------------------------------------------

[4] : <Rx> - 02:03:04.059

-Type : 0x04 (Event)

-EventCode : 0x00FF (Event)

-Data Length : 0x14 (20) bytes(s)

Event : 0x0605 (1541) (GAP_EstablishLink)

Status : 0x00 (0) (Success)

DevAddrType : 0x00 (0) (Public)

DevAddr : 68:C9:0B:08:55:0D

ConnHandle : 0x0000 (0)

ConnRole : 0x08 (8) (Central)

ConnInterval : 0x0050 (80)

ConnLatency : 0x0000 (0)

ConnTimeout : 0x07D0 (2000)

ClockAccuracy : 0x00 (0)

Dump(Rx):

0000:04 FF 14 05 06 00 00 0D 55 08 0B C9 68 00 00 08 ........U...h...

0010:50 00 00 00 D0 07 00 P......

--------------------------------------------------------------------

[5] : <Tx> - 02:03:31.003

-Type : 0x01 (Command)

-OpCode : 0xFE09 (GAP_EstablishLinkRequest)

-Data Length : 0x09 (9) byte(s)

HighDutyCycle : 0x00 (0) (Disable)

WhiteList : 0x00 (0) (Disable)

AddrTypePeer : 0x03 (3) (PrivateResolve)

PeerAddr : 42:DE:31:E5:4E:E8

Dump(Tx):

0000:01 09 FE 09 00 00 03 E8 4E E5 31 DE 42 ........N.1.B

--------------------------------------------------------------------

[6] : <Rx> - 02:03:31.029

-Type : 0x04 (Event)

-EventCode : 0x00FF (Event)

-Data Length : 0x06 (6) bytes(s)

Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)

Status : 0x15 (21) (There Are No Resources Available)

OpCode : 0xFE09 (GAP_EstablishLinkRequest)

DataLength : 0x00 (0)

Dump(Rx):

0000:04 FF 06 7F 06 15 09 FE 00 .........

--------------------------------------------------------------------

Have someone an idea?

  • Are you trying to run CC2650 as multi role? If so, you vmcan try to refer to processors.wiki.ti.com/.../Cc2640_MultiRole_Demo and github.com/.../README.md
  • Hi Chen,

    MultiRole seems like not to be what I need. I Need the UART-Interface and want to control with one CC2650 as central the other devices(peripheral).
    Correct me, but it seems that Multirole show only all information on display and has no uart interface.

    But with TestHost(central) is it not possible to connect with two peripherals???
  • I don't understand your demand clearly. If you have one CC2650 running HostTest and act as BLE central, it's no problem to connect multiple BLE peripheral device to it.
  • Hi Chen.

    Okay...It it possible with HostTest. This is one answer.

    But what did I wrong in my configuration? In the last step if I want connect to the second peripheral I get back in Status "There Are No Resources Available". So I must forgot something to configere... Do you have an idea? It is the normal HostTest with the 2.2 stack.

    Could it be a Problem, that one peripheral is public and the other PrivateResolve?

  • What's your second peripheral?
  • My second peripheral is a Samsung Galaxy S6.
  • If you use anther CC2650 as seconds peripheral, do you see the same problem?
  • I don't know because I have only two ble boards. This is the reason, why I try to use a smartphone. But it is alright with my configuration on the top side of this thread? Should not be somewhere count the addresshandler?
  • Just test with my HostTest with CC2650DK and it has no problem to connect to two BLE peripherals. I think it's problem of your peripheral on Samsung Galaxy S6.
  • Hello everyone,

    I'm also working with CC2650(Lauchpad) and trying to connect to as much as possible peripherals.

    I also used to test this Lauchpad, flashed with Host Test project and tried connect more than 1 peripheral. But I met the same problem with Mr.Christian Chabrowski: After the first connection established successfully, the second connection to peripheral has also return to me: "There Are No Resources Available".

    My peripheral is CC2541 custom board, with the connection parameters:

    DEFAULT_DESIRED_MIN_CONN_INTERVAL     160

    DEFAULT_DESIRED_MAX_CONN_INTERVAL     800

    DEFAULT_DESIRED_SLAVE_LATENCY         1

    DEFAULT_DESIRED_CONN_TIMEOUT          2000

    DEFAULT_ENABLE_UPDATE_REQUEST         TRUE

    Please check this problem again.

    Thanks and Regards.

  • Hi,

    I got an CC2650SensorTag and I had the same problem.

    I will try to explain each step I do. At moment I have two peripherals(SensorTag and SmartRF06 with Simple_peripheral) and one central SmartRF06 with HostTest.

    I start Btool and connect with HostTest.

    Push the button "Scan" and find both.

    Push the button "Establish" with the first Device and can connect.

    Next I choose next "Slave BDA" with the Combobox and try again to click the "establish" button.

    But then Pop up the message "GAP_EstablishLinkRequest Failed. There Are No Resources Available."

    Count the address handler automatically? Or where must I count this?

    If I start Btool, the GAP_DeviceInit Show signCounter 1... I changed it, but I have the same Problem.

    I hope this info helps to find a solution what I did wrong.

    I tested the multirole stack and I can connect with both devices. So it must be my configuration...

  • For your reference, I just test with my BLE kit. I use BTOOL and see it can connect to one CC2650 SensorTag, one CC2541 Keyfob, and one CC2541 SensorTag without problem.

  • Hi Chen,

    I believe you that it works. But which stack do you use? What are the configurations of your device-initialisation? Ando do you do exactly the same steps like what I said?

    But you used the same ConnInterval config...

    You did only change the Addr Type and pushed establish again?

    Could you give your Uart-output?

    thanks for the help.

  • Yes, I do the steps as yours

    Push the button "Scan" and find both.

    Push the button "Establish" with the first Device and can connect.

    Next I choose next "Slave BDA" with the Combobox and try again to click the "establish" button.

    and I can get my CC2650STK connected without problem. I attach my log for your reference.

    [1] : <Info> - 10:27:18.583
    Port opened at 2016/8/12 上午 10:27:18
    --------------------------------------------------------------------
    [2] : <Tx> - 10:27:18.768
    -Type           : 0x01 (Command)
    -OpCode         : 0xFE00 (GAP_DeviceInit)
    -Data Length    : 0x26 (38) byte(s)
     ProfileRole    : 0x08 (8) (Central)
     MaxScanRsps    : 0x05 (5)
     IRK            : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
     CSRK           : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
     SignCounter    : 0x00000001 (1)
    Dump(Tx):
    0000:01 00 FE 26 08 05 00 00 00 00 00 00 00 00 00 00 ...&............
    0010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    0020:00 00 00 00 00 00 01 00 00 00                   ..........
    --------------------------------------------------------------------
    [3] : <Rx> - 10:27:18.912
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x06 (6) bytes(s)
     Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
     Status         : 0x00 (0) (Success)
     OpCode         : 0xFE00 (GAP_DeviceInit)
     DataLength     : 0x00 (0)
    Dump(Rx):
    0000:04 FF 06 7F 06 00 00 FE 00                      .........
    --------------------------------------------------------------------
    [4] : <Rx> - 10:27:18.923
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x2C (44) bytes(s)
     Event          : 0x0600 (1536) (GAP_DeviceInitDone)
     Status         : 0x00 (0) (Success)
     DevAddr        : 68:C9:0B:08:63:89
     DataPktLen     : 0x001B (27)
     NumDataPkts    : 0x0A (10)
     IRK            : 6D:24:CE:D9:0E:92:24:5C:5C:90:24:20:B5:87:F7:2D
     CSRK           : 5F:F8:FD:30:F6:2E:07:7E:78:9B:71:38:95:6E:D6:FB
    Dump(Rx):
    0000:04 FF 2C 00 06 00 89 63 08 0B C9 68 1B 00 0A 6D ..,....c...h...m
    0010:24 CE D9 0E 92 24 5C 5C 90 24 20 B5 87 F7 2D 5F $....$\\.$ ...-_
    0020:F8 FD 30 F6 2E 07 7E 78 9B 71 38 95 6E D6 FB    ..0...~x.q8.n..
    --------------------------------------------------------------------
    [5] : <Tx> - 10:27:19.088
    -Type           : 0x01 (Command)
    -OpCode         : 0xFE31 (GAP_GetParam)
    -Data Length    : 0x01 (1) byte(s)
     ParamID        : 0x15 (21) (Minimum Link Layer Connection Interval, 
                      When Using Connection Establishment 
                      Proc (mSec). TGAP_CONN_EST_INT_MIN)
    Dump(Tx):
    0000:01 31 FE 01 15                                  .1...
    --------------------------------------------------------------------
    [6] : <Tx> - 10:27:19.099
    -Type           : 0x01 (Command)
    -OpCode         : 0xFE31 (GAP_GetParam)
    -Data Length    : 0x01 (1) byte(s)
     ParamID        : 0x16 (22) (Maximum Link Layer Connection Interval, 
                      When Using Connection Establishment 
                      Proc (mSec). TGAP_CONN_EST_INT_MAX)
    Dump(Tx):
    0000:01 31 FE 01 16                                  .1...
    --------------------------------------------------------------------
    [7] : <Tx> - 10:27:19.109
    -Type           : 0x01 (Command)
    -OpCode         : 0xFE31 (GAP_GetParam)
    -Data Length    : 0x01 (1) byte(s)
     ParamID        : 0x1A (26) (Link Layer Connection Slave Latency, When Using 
                      Connection Establishment Proc (mSec) TGAP_CONN_EST_LATENCY)
    Dump(Tx):
    0000:01 31 FE 01 1A                                  .1...
    --------------------------------------------------------------------
    [8] : <Tx> - 10:27:19.119
    -Type           : 0x01 (Command)
    -OpCode         : 0xFE31 (GAP_GetParam)
    -Data Length    : 0x01 (1) byte(s)
     ParamID        : 0x19 (25) (Link Layer Connection Supervision Timeout, 
                      When Using Connection Establishment 
                      Proc (mSec). TGAP_CONN_EST_SUPERV_TIMEOUT)
    Dump(Tx):
    0000:01 31 FE 01 19                                  .1...
    --------------------------------------------------------------------
    [9] : <Rx> - 10:27:19.123
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x08 (8) bytes(s)
     Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
     Status         : 0x00 (0) (Success)
     OpCode         : 0xFE31 (GAP_GetParam)
     DataLength     : 0x02 (2)
     ParamValue     : 0x0050 (80)
    Dump(Rx):
    0000:04 FF 08 7F 06 00 31 FE 02 50 00                ......1..P.
    --------------------------------------------------------------------
    [10] : <Rx> - 10:27:19.143
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x08 (8) bytes(s)
     Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
     Status         : 0x00 (0) (Success)
     OpCode         : 0xFE31 (GAP_GetParam)
     DataLength     : 0x02 (2)
     ParamValue     : 0x0050 (80)
    Dump(Rx):
    0000:04 FF 08 7F 06 00 31 FE 02 50 00                ......1..P.
    --------------------------------------------------------------------
    [11] : <Rx> - 10:27:19.153
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x08 (8) bytes(s)
     Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
     Status         : 0x00 (0) (Success)
     OpCode         : 0xFE31 (GAP_GetParam)
     DataLength     : 0x02 (2)
     ParamValue     : 0x0000 (0)
    Dump(Rx):
    0000:04 FF 08 7F 06 00 31 FE 02 00 00                ......1....
    --------------------------------------------------------------------
    [12] : <Rx> - 10:27:19.164
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x08 (8) bytes(s)
     Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
     Status         : 0x00 (0) (Success)
     OpCode         : 0xFE31 (GAP_GetParam)
     DataLength     : 0x02 (2)
     ParamValue     : 0x07D0 (2000)
    Dump(Rx):
    0000:04 FF 08 7F 06 00 31 FE 02 D0 07                ......1....
    --------------------------------------------------------------------
    [13] : <Tx> - 10:27:20.149
    -Type           : 0x01 (Command)
    -OpCode         : 0xFE04 (GAP_DeviceDiscoveryRequest)
    -Data Length    : 0x03 (3) byte(s)
     Mode           : 0x03 (3) (All)
     ActiveScan     : 0x01 (1) (Enable)
     WhiteList      : 0x00 (0) (Disable)
    Dump(Tx):
    0000:01 04 FE 03 03 01 00                            .......
    --------------------------------------------------------------------
    [14] : <Rx> - 10:27:20.170
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x06 (6) bytes(s)
     Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
     Status         : 0x00 (0) (Success)
     OpCode         : 0xFE04 (GAP_DeviceDiscoveryRequest)
     DataLength     : 0x00 (0)
    Dump(Rx):
    0000:04 FF 06 7F 06 00 04 FE 00                      .........
    --------------------------------------------------------------------
    [15] : <Rx> - 10:27:23.922
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x0E (14) bytes(s)
     Event          : 0x060D (1549) (GAP_DeviceInformation)
     Status         : 0x00 (0) (Success)
     EventType      : 0x00 (0) (Connectable Undirect Advertisement)
     AddrType       : 0x03 (3) (PrivateResolve)
     Addr           : 50:D1:24:B7:E8:F7
     Rssi           : 0xDE (222)
     DataLength     : 0x01 (1)
     Data           : 00
    Dump(Rx):
    0000:04 FF 0E 0D 06 00 00 03 F7 E8 B7 24 D1 50 DE 01 ...........$.P..
    0010:00                                              .
    --------------------------------------------------------------------
    [16] : <Rx> - 10:27:23.932
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x24 (36) bytes(s)
     Event          : 0x060D (1549) (GAP_DeviceInformation)
     Status         : 0x00 (0) (Success)
     EventType      : 0x04 (4) (Scan Response)
     AddrType       : 0x03 (3) (PrivateResolve)
     Addr           : 50:D1:24:B7:E8:F7
     Rssi           : 0xDE (222)
     DataLength     : 0x17 (23)
     Data           : 16:FF:54:01:00:33:37:46:30:31:32:35:39:32:45:38:
                      38:04:02:03:0C:02:00
    Dump(Rx):
    0000:04 FF 24 0D 06 00 04 03 F7 E8 B7 24 D1 50 DE 17 ..$........$.P..
    0010:16 FF 54 01 00 33 37 46 30 31 32 35 39 32 45 38 ..T..37F012592E8
    0020:38 04 02 03 0C 02 00                            8......
    --------------------------------------------------------------------
    [17] : <Rx> - 10:27:24.644
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x1C (28) bytes(s)
     Event          : 0x060D (1549) (GAP_DeviceInformation)
     Status         : 0x00 (0) (Success)
     EventType      : 0x03 (3) (Non-connectable Undirect Advertisement)
     AddrType       : 0x02 (2) (PrivateNonResolve)
     Addr           : 36:53:8F:CB:AB:70
     Rssi           : 0xA2 (162)
     DataLength     : 0x0F (15)
     Data           : 02:01:1B:0B:FF:4C:00:09:06:03:E1:C0:A8:64:66
    Dump(Rx):
    0000:04 FF 1C 0D 06 00 03 02 70 AB CB 8F 53 36 A2 0F ........p...S6..
    0010:02 01 1B 0B FF 4C 00 09 06 03 E1 C0 A8 64 66    .....L.......df
    --------------------------------------------------------------------
    [18] : <Rx> - 10:27:24.744
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x18 (24) bytes(s)
     Event          : 0x060D (1549) (GAP_DeviceInformation)
     Status         : 0x00 (0) (Success)
     EventType      : 0x00 (0) (Connectable Undirect Advertisement)
     AddrType       : 0x00 (0) (Public)
     Addr           : 04:4B:ED:B1:EB:F7
     Rssi           : 0xA1 (161)
     DataLength     : 0x0B (11)
     Data           : 02:01:1A:07:FF:4C:00:10:02:01:00
    Dump(Rx):
    0000:04 FF 18 0D 06 00 00 00 F7 EB B1 ED 4B 04 A1 0B ............K...
    0010:02 01 1A 07 FF 4C 00 10 02 01 00                .....L.....
    --------------------------------------------------------------------
    [19] : <Rx> - 10:27:25.222
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x1B (27) bytes(s)
     Event          : 0x060D (1549) (GAP_DeviceInformation)
     Status         : 0x00 (0) (Success)
     EventType      : 0x00 (0) (Connectable Undirect Advertisement)
     AddrType       : 0x00 (0) (Public)
     Addr           : C4:BE:84:70:7B:09
     Rssi           : 0xDB (219)
     DataLength     : 0x0E (14)
     Data           : 02:01:05:03:02:80:AA:06:FF:0D:00:03:00:00
    Dump(Rx):
    0000:04 FF 1B 0D 06 00 00 00 09 7B 70 84 BE C4 DB 0E .........{p.....
    0010:02 01 05 03 02 80 AA 06 FF 0D 00 03 00 00       ..............
    --------------------------------------------------------------------
    [20] : <Rx> - 10:27:25.232
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x28 (40) bytes(s)
     Event          : 0x060D (1549) (GAP_DeviceInformation)
     Status         : 0x00 (0) (Success)
     EventType      : 0x04 (4) (Scan Response)
     AddrType       : 0x00 (0) (Public)
     Addr           : C4:BE:84:70:7B:09
     Rssi           : 0xDB (219)
     DataLength     : 0x1B (27)
     Data           : 11:09:43:43:32:36:35:30:20:53:65:6E:73:6F:72:54:
                      61:67:05:12:08:00:20:03:02:0A:00
    Dump(Rx):
    0000:04 FF 28 0D 06 00 04 00 09 7B 70 84 BE C4 DB 1B ..(......{p.....
    0010:11 09 43 43 32 36 35 30 20 53 65 6E 73 6F 72 54 ..CC2650 SensorT
    0020:61 67 05 12 08 00 20 03 02 0A 00                ag.... ....
    --------------------------------------------------------------------
    [21] : <Rx> - 10:27:30.583
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x24 (36) bytes(s)
     Event          : 0x0601 (1537) (GAP_DeviceDiscoveryDone)
     Status         : 0x00 (0) (Success)
     NumDevs        : 0x04 (4)
     Device #0
     EventType      : 0x00 (0) (Connectable Undirect Advertisement)
     AddrType       : 0x03 (3) (PrivateResolve)
     Addr           : 50:D1:24:B7:E8:F7
     Device #1
     EventType      : 0x03 (3) (Non-connectable Undirect Advertisement)
     AddrType       : 0x02 (2) (PrivateNonResolve)
     Addr           : 36:53:8F:CB:AB:70
     Device #2
     EventType      : 0x00 (0) (Connectable Undirect Advertisement)
     AddrType       : 0x00 (0) (Public)
     Addr           : 04:4B:ED:B1:EB:F7
     Device #3
     EventType      : 0x00 (0) (Connectable Undirect Advertisement)
     AddrType       : 0x00 (0) (Public)
     Addr           : C4:BE:84:70:7B:09
    Dump(Rx):
    0000:04 FF 24 01 06 00 04 00 03 F7 E8 B7 24 D1 50 03 ..$.........$.P.
    0010:02 70 AB CB 8F 53 36 00 00 F7 EB B1 ED 4B 04 00 .p...S6......K..
    0020:00 09 7B 70 84 BE C4                            ..{p...
    --------------------------------------------------------------------
    [22] : <Tx> - 10:27:41.403
    -Type           : 0x01 (Command)
    -OpCode         : 0xFE09 (GAP_EstablishLinkRequest)
    -Data Length    : 0x09 (9) byte(s)
     HighDutyCycle  : 0x00 (0) (Disable)
     WhiteList      : 0x00 (0) (Disable)
     AddrTypePeer   : 0x00 (0) (Public)
     PeerAddr       : C4:BE:84:70:7B:09
    Dump(Tx):
    0000:01 09 FE 09 00 00 00 09 7B 70 84 BE C4          ........{p...
    --------------------------------------------------------------------
    [23] : <Rx> - 10:27:41.421
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x06 (6) bytes(s)
     Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
     Status         : 0x00 (0) (Success)
     OpCode         : 0xFE09 (GAP_EstablishLinkRequest)
     DataLength     : 0x00 (0)
    Dump(Rx):
    0000:04 FF 06 7F 06 00 09 FE 00                      .........
    --------------------------------------------------------------------
    [24] : <Info> - 10:27:41.455
    Device Connected
    Handle = 0x0000
    Addr Type = 0x00 (Public)
    BDAddr = C4:BE:84:70:7B:09
    --------------------------------------------------------------------
    [25] : <Rx> - 10:27:41.449
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (Event)
    -Data Length    : 0x14 (20) bytes(s)
     Event          : 0x0605 (1541) (GAP_EstablishLink)
     Status         : 0x00 (0) (Success)
     DevAddrType    : 0x00 (0) (Public)
     DevAddr        : C4:BE:84:70:7B:09
     ConnHandle     : 0x0000 (0)
     ConnRole       : 0x08 (8) (Central)
     ConnInterval   : 0x0050 (80)
     ConnLatency    : 0x0000 (0)
     ConnTimeout    : 0x07D0 (2000)
     ClockAccuracy  : 0x00 (0)
    Dump(Rx):
    0000:04 FF 14 05 06 00 00 09 7B 70 84 BE C4 00 00 08 ........{p......
    0010:50 00 00 00 D0 07 00                            P......
    --------------------------------------------------------------------

  • Hi Chen,
    I compared the BTOOL.TXT with my output from btool. It is the same.
    So I think the problem is in the stack. I use the latest version (2.2 from 21-JUN-2016 ) and changed nothing. Which version do you have?
  • I test both BLE Stack 2.2 and 2.1 and all of them work fine.
  • Hello Christian. Has this been resolved?
  • Hello,

    If you are building host_test from CCS (BLE-Stack v2.2.0), please add the following to the predefined symbols in the App project:
    MAX_NUM_BLE_CONNS=8

    Best wishes

    Edited - corrected to add the predefined symbol

  • Thank you JXS.

    But what about the HEAPMGR_SIZE predefined symbol?! I read "Cc2640 MultiRole Demo" and "CC2640 Central to MultiPeripheral" sample from BLE Wiki, they both mention to the relationship between MAX_NUM_BLE_CONNS and HEAPMGR_SIZE.

    By default, the HEAPMGR_SIZE is predefined with 0. So if I add predefined symbol as you suggest, how should I define the HEAPMGR_SIZE?!

    #Update:

    I have tested with some HEAPMGR_SIZE predefined numbers and see that the maximum HEAPMGR_SIZE number I could predefine is 8619. Over that number, IDE will return error: "Program will not fit into available memory. run placement with alignment fails for section ".stack" size 0x400".

    So I stopped at HEAPMGR_SIZE = 8610, and tried using BTool to connect with my 8 sensor nodes. First 7 connections were established successfully. But at the 8th connection, BTool returned me: "GAP_EstablishLinkRequest Failed. There are no resources available". So I guest the real maximum connection number is 7.

    Could u confirm it for me?! 

    Best Regards.