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.


Part Number: SIMPLELINK-CC13X2-26X2-SDK
Other Parts Discussed in Thread: SYSCONFIG, CC2651R3

Device                                       CC2640R2LAUNCHXL  to  CC26x2LAUNCHXL

SDK                                           simplelink_cc2640r2_sdk_4_20_00_04   to     simplelink_cc13x2_26x2_sdk_5_20_00_52

IDE                                             Code Composer Studio 9.1.0      to     Code Composer Studio 10.3.0

Reference project                     multi_role

Hi TI,

       We have a project similar to multi_role  of BLE 4 stack now we are moving the project to BLE 5 as we can see that the earlier versions are having two files they are Application and Stack ,now there is only tirtos_ccs file where Application and stack are in single build.So we are facing a problem with porting the stack part to merge as single build , the documentation of porting CC2640r2 to CC26x2 is just showing the indication of changes but not the exact stack porting.

Problem statement :

How to exactly port the stack files of BLE 4 to BLE 5 into single build project ?


Niranjan Hegde 

  • Hello Niranjan,

    Moving from BLE -> BLE5 stack can be challenging, but we do have some guides to help you with this process. In my experience, the simplest approach is to begin with the CC26x2 project and port over the application from the CC2640R2.

    Are there any changes that were made to the stack files on the CC2640R2 that you would like to retain? If yes, what are they?

    Here are some guides to get you started:

    One of the biggest changes to keep aware of is the integration of SysConfig. With this tool, you can configure the stack, advertisement sets, pairing/bonding information, etc. When you build a project on the CC26x2, the SysConfig generated files will be located in a syscfg folder located inside the Release directory (where your .out file is located). These files are only modifiable via the SysConfig tool; any change to the files will automatically be overwritten in the next build.

    I would take a moment to familiarize yourself with the settings that are defined by the SysConfig tool. If you have any questions, feel free to ask them here.

  • Now that we are building multirole kind application on CC2642R1F variant ,in future we are willing to use CC2651R3 variant .

    So the question is can we directly use the application of CC2642R1F on to the CC2651R3 variant just by changing Linker command file or do we have to change any other 

  • Hey Niranjan,

    This should be all you need. It certainly is our design to make migrations like this easy. We currently don't have a guide on this but if you have any issues, feel free to post your questions as they come up.

  • Thankyou Ammar N, we are porting our application as you said our application over to CC26x2 .If we got stuck anywhere we will reach you.