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: Opening Two Different Debug Sessions on Two Different Targets

Tool/software: Code Composer Studio

hi all,

i need to test Communication between two boards " IDK AM437x  and Delfino Kit " , so i need to open two debug sessions separately for each one
i tried to open CCS twice with Different work space but CCS rejected

what can i do ?

  • Ahmed,

    Are you using the XDS100v2 debug probes that are embedded on these boards? Can you explain what you mean by "CCS rejected"? Did CCS fail to open or did you get an error when launching a debug session?

    You should be able to open 2 instances of CCS as long as they are using different workspaces. However you can also create a target configuration for use in a single CCS workspace that has both boards in it. One thing that you are going to have to do in either case is set the serial number on each of the XDS100s so that CCS knows which board to connect to.

    This video shows how to have a single target configuration file with multiple boards that use XDS100 debug probes.
    www.youtube.com/watch

    If you want to use separate CCS instances for each board you would still need to follow the steps for setting the serial numbers on each.

    Regards,
    John
  • i open a debug session for the first target on CCS instance in Work space 1 using Texas instruments XDS100v2

    when i open another CCS instance in work space 2 also using Texas instruments XDS100v2
    the first session gives me error and exit
  • Try building a configuration like shown in the video. You will need to setup the serial numbers.

    By doing what is shown in the video you will be able to debug either or both of your boards.


    John
  • thanks JohnS
    but let me modify something for your reply and the video
    to Debug two different targets simultaneously we just need
    1 - using two different work spaces
    2 - modifying the target configuration file for each target to use serial numbers instead of Default settings as the video states

    now everything works correctly
    thank you very much