RTOS/CC2650MODA: problem with connection between cc2650lanchpad(host_test) and cc2650moda(simple_peripheral)

Hi,

I am assigning an expert to follow-up. Stay tuned

Hi,

to explain the situation more clearly, I attach some code which i try to implement the data length extension base on simple_peripheral .

These code I add works properly with IPAD BLE scanner

// this part is in simple_peripheral.c

// in order to understand what I do for data length extension, I remove the original part in simple_peripheral
static uint8_t SimpleBLEPeripheral_processGATTMsg(gattMsgEvent_t *message) {
    if (message->hdr.status == blePending) {

    } else if (message->method == ATT_MTU_UPDATED_EVENT) {
        // MTU size updated
        // this buffer is used to debug
        // when i connect it to my ipad , it do show the value i set
        headstage_debug_buffer[0] = 0x0f;
        headstage_set_debug_information();
        headstage_data_length_extension();
    }
}

static void headstage_data_length_extension(){
    while(1){
        headstage_debug_buffer[4] ++;
        headstage_set_debug_information();
        while (!Queue_empty(application_message_queue))
        {
          sbpEvt_t *pMsg = (sbpEvt_t *)Util_dequeueMsg(application_message_queue);
          if (pMsg)
          {
            // Process message.
            SimpleBLEPeripheral_processAppMsg(pMsg);

            // Free the space from the message.
            ICall_free(pMsg);
          }
        }
        if (EVENT_MASK > 0) {
            headstage_event_handle();
        }
    }
}

static void SimpleBLEPeripheral_init(void) {
    /*
     * the same as original one , to catch the point more easily, I remove the original part. 
     */

    HCI_LE_ReadMaxDataLenCmd();

    HCI_LE_WriteSuggestedDefaultDataLenCmd(251 , 2120); // this is used for data length extension
}

// in simple_peripheral_stack build_config.opt

/* BLE v4.2 Features */
// I have already uncommented it 
 -DBLE_V42_FEATURES=EXT_DATA_LEN_CFG 

/* 
 * In simple_gatt_profile.h
 * I modify characteristic 4 length for notification with data length extension 
 */
#define SIMPLEPROFILE_CHAR4_LEN 244

for some experiement with packet sniffer. 

I don't see any data length extension procedure which is done over air.

another question about LL_feature_set_meaning , acorrding to official document of bluetooth , page 2653 feature support. 

It looks like my simple peripheral don't support data length extension. How come?

condition : cc2650(host_test with btool ) connect to cc2650(simple_peripheral)

condition 2: IPad (BLE scanner) connect to cc2650(simple_peripheral)

if the feature set is little endian, we can find that simple peripheral do not support LE Data packet data length extension according to

specification of bluetooth system, v5.0 page 2653 feature support.

If i make some mistake about its meaning or I follow the wrong procedure?

into my application? 

HI

     Sorry for reply so late. I do really uncomment  /* -DBLE_V42_FEATURES=EXT_DATA_LEN_CFG */ in config.opt.

I have tried to use characteristic 4 value to do notification.

In my knowledge, the characteristic length would control the packet length every time I try to notify.

If i need to enlarge this value to achieve a larger packet length, or I need to queue to notify like the method in throughput_peripheral do?

Hi,

    there is some problem with host_test,

if I uncomment /* -DBLE_V42_FEATURES=EXT_DATA_LEN_CFG */  in host_test_stack config.opt

from btool, the connection will disconnect right away.

if i want to send gatt_GATTWriteCharValue , there is an error occur because of msg buffer is not available.