• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 52 subscribers
  • Views 508 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2652R7: Conformation on Software for different hardware

mohan prasanna R
Intellectual 710 points

Part Number: CC2652R7
Other Parts Discussed in Thread: CC2642R, , ARM-CGT, CC2652R, SYSCONFIG

Hi,

We are planned to use the CC2652R7 in my product. Previously we used CC2642R chipset.

1) Is there any difference in SDK or software for these two chipsets ?

2) Previously we used "simplelink_cc13x2_26x2_sdk_5_20_00_52" SDK. In this while importing the project from SDK. It will show two option CCS, ticlang like below image 

In this we used tirtos_ccs code for CC2642R.

3) Currently we donwloaded the latest SDK "simplelink_cc13xx_cc26xx_sdk_7_10_01_24" and upgraded chipset CC2652R7 In this It showing only one option ticlang like below image,

In this no option we have to use tirtos7_ticlang code only. We are planning to reuse the code of CC2642R in this lates SDk for CC2652R7 chipset. Is both are similar or need o face any problem on this ?

Please reply for these 3 points   

  • 0
    TI__Guru** 101570 points

    Hi,

    Thank you for reaching out.

    Since SDK 6.20, we have removed support for TI ARM-CGT compiler examples and libraries, in favor of the TI Clang Compiler (see SDK 6.20 release notes: https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/6.20.00.29/exports/release_notes_simplelink_cc13xx_cc26xx_sdk_6_20_00_29.html).

    The tool-chain migration should be fairly straight forward. 

    For other migration questions, please make sure to refer to the migration guides: https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/7.10.01.24/exports/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/migration-cc13xx_cc26xx.html

    Also, in case you face some issues in the migration process, please make sure to ask for our support.

    I hope this will help,

    Best regards,

  • 0 in reply to Clément
    Intellectual 710 points

    Hi,

    We are planned to use the CC2652R7 in my product. Previously we used CC2642R chipset. So, we are planned to used the same FW(used in CC2642R) application for CC2652R chipset 

    1) Will It cause any issue ?

    2) Is there any difference in SDK or software for these two chipsets ?

  • 0 in reply to mohan prasanna R
    TI__Guru** 101570 points

    Hi,

    1) I am afraid CC2652R7 and CC2642R are not binary compatible. In other words you cannot directly used a binary built for CC2642R on CC2652R7 silicon.

    2) CC2652R7 and CC2642R share the same SDK and the same software APIs. Once you have migrated your project to use the newest SDK, the migration between CC2642R and CC2652R7 can be done through SysConfig with a few clicks.

    I hope this will help,

    Best regards,

  • 0 in reply to Clément
    Intellectual 710 points

    Hi Clement

    Thank you.

    HW using for development : CC2652R1 development kit 

    SW SDK using for development : simplelink_cc13xx_cc26xx_sdk_7_10_01_24

    HW planned to use in Traget board : CC2652R7 chipset

    Query 1 : 

    For development, We are using "simple_peripheral_CC26X2R1_LAUNCHXL_tirtos7_ticlang" source code from  simplelink_cc13xx_cc26xx_sdk_7_10_01_24 SDK.  Path : ~/ti/simplelink_cc13xx_cc26xx_sdk_7_10_01_24/examples/rtos/CC26X2R1_LAUNCHXL/ble5stack/simple_peripheral

    For "CC2652R7 chipset", we are assuming that "simple_peripheral_LP_CC2652R7_tirtos7_ticlang" from following path "~/ti/simplelink_cc13xx_cc26xx_sdk_7_10_01_24/examples/rtos/LP_CC2652R7/ble5stack/simple_peripheral" Code to be used. 

    Is our assumption is correct ?

    Query 2 :

    In case of our assumption is correct from Query 1, Please answer the below query. 

    We compared the both source codes, as given in below image,

    In this image only memory mapping and memory definition alone is the difference between these two source code (Difference file only listed in image). So please ensure that, Other than the file listed in above image, Source code which we currently developing using  "simple_peripheral_CC26X2R1_LAUNCHXL_tirtos7_ticlang" project shall be used for the "simple_peripheral_LP_CC2652R7_tirtos7_ticlang" project also ? While using CC2652R7 chipset in target board. 

  • 0 in reply to mohan prasanna R
    TI__Guru** 101570 points

    Hi,

    mohan prasanna R said:

    Query 1 : 

    For development, We are using "simple_peripheral_CC26X2R1_LAUNCHXL_tirtos7_ticlang" source code from  simplelink_cc13xx_cc26xx_sdk_7_10_01_24 SDK.  Path : ~/ti/simplelink_cc13xx_cc26xx_sdk_7_10_01_24/examples/rtos/CC26X2R1_LAUNCHXL/ble5stack/simple_peripheral

    For "CC2652R7 chipset", we are assuming that "simple_peripheral_LP_CC2652R7_tirtos7_ticlang" from following path "~/ti/simplelink_cc13xx_cc26xx_sdk_7_10_01_24/examples/rtos/LP_CC2652R7/ble5stack/simple_peripheral" Code to be used. 

    Is our assumption is correct ?

    Your assumption is correct.

    mohan prasanna R said:

    Query 2 :

    In case of our assumption is correct from Query 1, Please answer the below query. 

    We compared the both source codes, as given in below image,

    In this image only memory mapping and memory definition alone is the difference between these two source code (Difference file only listed in image). So please ensure that, Other than the file listed in above image, Source code which we currently developing using  "simple_peripheral_CC26X2R1_LAUNCHXL_tirtos7_ticlang" project shall be used for the "simple_peripheral_LP_CC2652R7_tirtos7_ticlang" project also ? While using CC2652R7 chipset in target board. 

    As you have mentioned the projects for CC26X2R and CC2652R7 devices are very close.

    However, there are a few configurations hidden from the user that are not identical, so I highly recommend to start development for a CC2652R7 leveraging the projects in the LP_CC2652R7 folder. While starting the development for CC2642R/CC2652R leveraging the projects in CC26X2R1_LAUNCHXL.

    If needed, you can consider migrating project from one device to the other.
    However, you should not attempt to flash an image compiled for CC2652R7 on a CC2642R/CC2652R or vice versa.

    I hope this will help,

    Best regards,