CC2642R-Q1: CC2642R-Q1

Part Number: CC2642R-Q1
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi, hello,

I am referring to this document C:/ti/simplelink_cc13xx_cc26xx_sdk_7_41_00_17/docs/ble5stack/ble_user_guide, specifically the "Connection Oriented Channels Example," and using the example at C:\ti\simplelink_cc13xx_cc26xx_sdk_7_41_00_17\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\simple_peripheral to debug the L2CAP CoC functionality.

I would like to ask if there is any mobile app that can be used to test this functionality during debugging?

For example, after establishing a Bluetooth connection using the CC2642, I call the function L2CAP_ConnectReq(connHandle, App_SPSM, App_SPSM) to establish the L2CAP CoC channel. Then, I periodically call Application_sendL2capData to send data. At this point, I expect to see the data I send in an Android app, but I currently cannot see the data using nrfconnect. So, I would like to inquire if there is any specific app for this purpose?

  • Hi,

    Usually for this, we would recommend to use another board. The L2CAP_COC project contains both the initiator and responder, and can be setup using sysconfig. I'm not sure if NRFConnect has the capability of setting up a connection like this without creating a custom application on Android.

    Make sure that L2CAP Connection Oriented Channels is selected.

    In the L2CAP settings, set one project to COC Responder, and the other to initiator. 

    Best,

    Nima Behmanesh

  • Hi ,

    I couldn't find  L2CAP settings in Syscfg in the SDK0741 example located at C:\ti\simplelink_cc13xx_cc26xx_sdk_7_41_00_17\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\simple_peripheral. Am I using the wrong version?

    Here is the information about my project.

  • Hello,

    I see you're using the simple_peripheral project, please try using the basic_ble project.

    Best,

    Nima Behmanesh

  • Hi,
    1、I couldn't find the L2CAP settings in the basic_ble project, multi_role project, or simple_central project.However, this is no longer important to me.

    2、I referred to your "ble5stack-users-guide.html" Connection Oriented Channels Example and implemented L2CAP COC communication between two development boards.

    3、I used Ellisys to capture the air packets of L2CAP COC communication between two development boards, and here are the screenshots:

    I saw that the 245-byte data of L2CAP is split into multiple 27-byte packets for transmission in the Link Layer.

    I am trying to figure out the reason behind this packet segmentation.

    In Core_v4.1, I found the following description: here, the Length is 5 bits, which can represent a maximum value of 31. Subtracting the 32-bit MIC, this results in exactly 27 bytes. From this information, it seems that the segmentation of 27 bytes is due to the rules in Core_v4.1.

    However, starting from Core_v4.2, the Length is 8 bits, and both of the development boards we are using now support Bluetooth 5.2.

    My question is, when using two devices with Bluetooth version 5.2, can the L2CAP data in the Link Layer be segmented according to an 8-bit Length?

    Best,

    xdz

  • Hi,

    Yes you should be able to use a larger size for the data transfer. 

    Best,

    Nima Behmanesh