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.

CC2642R: Question about simple_serial_socket example.

Part Number: CC2642R


I'm testing the simple_serial_socket example in link below.

I prepared two CC26x2 LaunchPad for test.

First, I downloaded simple_serial_socket_server project to a CC26x2 LaunchPad in the CCS and I setup the host_test image on other CC26x2 LaunchPad.

Then I ran the BTool and simple_serial_socket_server.

The SimpleLink Starter can scanned the SimpleSerialSocket but the BTool cannot scan it.

I don't understand this problem.

I don't modified example project and only compiled and downloaded.

I think that If the mobile App can scan advertising of device, it should be see in the BTool.

  •  I suppose you should use  simple_serial_socket_client instead of host_test to work with simple_serial_socket_server

  • Hey SY,

    I was able to see the server in BTOOL with the unmodified example. Using BTOOL is not as straight forward unfortunately. Our mobile phones are able to scan for devices and send a scan request where the device will then respond with the scanResData1[]. In this case, you are able to see the name "SimpleSerialSocket" pop up on your mobile phone.

    In BTOOL, however, the scanner just scans for advertisements without requesting any information from the device discovered. In this case, you will only see the advData1[] in the BTOOL logs. I was able to discover the log by parsing the Data field of the scanner event, shown below:

    [20] : <Rx> - 12:21:27.265
    -Type           : 0x04 (Event)
    -EventCode      : 0x00FF (HCI_LE_ExtEvent)
    -Data Length    : 0x3B (59) bytes(s)
     Event          : 0x0613 (1555) (GAP_AdvertiserScannerEvent)
     Status         : 0x00 (0) (SUCCESS)
     EventId        : 0x00400000 (4194304) (
     AdvRptEventType: 0x13 (19) (Legacy_ADV_IND_or_Data_Complete)
     AddressType    : 0x01 (1) (ADDRTYPE_RANDOM)
     Address        : 5A:29:6B:6D:1A:ED
     PrimaryPHY     : 0x01 (1) (SCANNED_PHY_1M)
     SecondaryPHY   : 0x00 (0) (SCANNED_PHY_NONE)
     AdvSid         : 0xFF (255)
     TxPower        : 0x7F (127)
     RSSI           : 0xE0 (224)
     DirectAddrType : 0xFF (255) (ADDRTYPE_NONE)
     DirectAddr     : 00:00:00:00:00:00
     PeriodicAdvInt : 0x0000 (0)
     DataLength     : 0x001C (28)
     Data           : 02:01:06:11:06:00:00:00:00:00:00:00:B0:00:40:51:
    0000:04 FF 3B 13 06 00 00 00 40 00 13 01 ED 1A 6D 6B ..;
    0010:29 5A 01 00 FF 7F E0 FF 00 00 00 00 00 00 00 00 )Z..............
    0020:1C 00 02 01 06 11 06 00 00 00 00 00 00 00 B0 00 ................
    0030:40 51 04 C0 C0 00 F0 06 FF 0D 00 C0 FF EE       @Q............

    You'll find that in the Data column, you can see the advData1[] payload as it is inside ti_ble_config.c. The last 3 bytes are the "additional data", 0xC0, 0xFF, 0xEE.

    I hope this helps.

    EDIT: Please also note that the simple_serial_socket_server example is configured with RPAs enabled, so the advertisement address will change periodically.

  • I appreciate your kindly reply. 

    It was very helpful for me. 

    Thank you.