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: Can CC2642 software be used on CC2652 EVM?

Part Number: CC2642R
Other Parts Discussed in Thread: UNIFLASH, SIMPLELINK-CC13XX-CC26XX-SDK

Hi, 

My customer is using a CC2642R developed software by their end-customer onto LAUNCHXL-CC26X2R1 EVM which comes with CC2652 silicon. However after loading the code onto the EVM, there is no response from the EVM. They tried to modify a GPIOs to turn ON LED but it did not work accordingly. In such scenario, what would be the recommended approach to validate what may be wrong in the setup?

Thansk,

Christina 

  • Hi Christina,

    Please detail where they obtained the base code from and what application changes have been made.  What binary image are they using and what environment (ex CCS, Uniflash) are the using to program the firmware?  Have they tried evaluating a default BLE5-Stack or TI-Drivers CC26X2R1_LAUNCHXL example from the SIMPLELINK-CC13XX-CC26XX-SDK?  

    Regards,
    Ryan

  • Hi Ryan, 

    The SDK they are using is CC13xx_cc26xx_SDK_6_40_00_13 as seen below. 

    The only change they made is on a particular GPIO. I'm urging them to validate the setup using our default SDK on the web to isolate the issue further. 

    Meanwhile, fyi below is the hardware kit used. 

    If you do see any issue between the SDK 6_40_00_13 with the above hardware, pls let us know. 

    Thanks,

    Christina 

  • Please have them confirm that Rev E silicon is being used, not Rev C.  https://e2e.ti.com/f/1/t/767777 

    Rev C was discontinued after 2018, with SIMPLELINK-CC13XX-CC26XX-SDK v2.30 being the last supported SDK for this device version.  Otherwise Rev E hardware should be fine with SIMPLELINK-CC13XX-CC26XX-SDK v6.40

    Let me know when they've evaluated default examples from the release SDK, or what specific changes are made to sample projects.

    Regards,
    Ryan