• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 478 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.

CCS/LAUNCHXL-CC1312R1: A problem with the debug probe when I use both CCS and SCS

Adam Kozlowski
Expert 1805 points
Part Number: LAUNCHXL-CC1312R1
Other Parts Discussed in Thread: LAUNCHXL-CC1352R1

Tool/software: Code Composer Studio

Hi,

I work on LAUNCHXL-CC1312R1 (chip revision E)
I use Code Composer Studio 9.2.0.00013 and Sensor Controller Studio 2.5.0.84 (patches 1,2,3)
 
I have a problem with the debug probe when I use both Code Composer Studio (CCS) and Sensor Controller Studio (SCS) (alternately).
Every time I use CCS after debugging in SCS, I need to upgrade the firmware in the debug probe.
The same situation happens when I use debug probe in SCS after using it in CCS.
 
Please, take a look at the attached screenshots.


My colleague has the same issue.
The same situation occurs when I work on LAUNCHXL-CC1352R1.
 
How can I solve this issue?

/Adam

  • 0
    TI__Guru**** 162285 points

    Adam,

    The root of the issue is that CCS and SCS are using different versions of the XDS110 support software.  In general that is not an issue but in this case there is a compatibility issue in the versions they are using.  Thus to ensure proper operation each tool loads the compatible firmware to the XDS110.  I am not sure on the plans for SCS to update to a newer version of the XDS110 support software.  

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1805 points

    John
     
    Thank for your quick reply.
     
    When working with CC13x2 family using both RISC and CM4, it is necessary to switch between CCS and SCS environment multiple times. Upgrading firmware every time is both time-consuming and error-prone.
    Can anyone take this into account and perform synchronization between versions of XDS110 support software?
     
    Can I change (upgrade) the XDS110 support software in one of these environments on my own?
    Is there any way to solve this problem on my own, without waiting for TI to make changes in one of these environments?
     
    /Adam

  • 0 in reply to Adam Kozlowski
    TI__Guru**** 162285 points

    Adam,

    I am talking with the SCS team to see about manually dropping in the XDS110 files from CCS into SCS.  We believe it should work fine but they are going to try it out.

    John

  • 0 in reply to JohnS
    Expert 1805 points

    John,

    I appreciate your help and look forward to hearing from you.

    /Adam

  • 0 in reply to JohnS
    Expert 1805 points

    Hi John,

    Do you have any news regarding this issue?

    /Adam

  • 0 in reply to Adam Kozlowski
    TI__Guru**** 162285 points

    Adam,

    We have confirmed that you can copy over the updated XDS110 support software into SCS however we need to figure out how to change the TCLK frequency that is then used as the version in CCS uses a higher frequency that is causing some stability issues in SCS with CC13x2.

    John

  • 0 in reply to JohnS
    TI__Guru**** 162285 points

    Adam,

    We have a zip that you can drop into SCS that brings its level of XDS110 support up to the same level as CCSv9.2.

    scx_xds_patch_8.3.0.00003.zip

    I would suggest making a backup of the /drivers folder in the SCS installation.  I would then take the common and emulation folders from the zip and extract them into the ones in the SCS /drivers folder and replace the existing files.

    I tried this out and I was able to move back and forth between SCS and CCS without triggering the update. The first time I connected with SCS I had to do the update but that was it (if you had most recently been using CCS that would not have happened).

    One additional change that the SCS team suggested was to edit the XDS110.DAT file in /drivers/board_config

    make sure the tclk_program and tclk_frequency lines look like below

    $ uscif
    tdoedge=FALL
    tclk_program=SPECIFIC
    tclk_frequency=2.5MHz
    $ /

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1805 points

    Hi John

    Thank you, you're great.
    It works like a charm.
    Switching between SCS and CCS is now a lot faster.

    /Adam