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/IWR6843: Enabling Global Breakpoints at group level when cores are running only shows it enabled on one core

Part Number: IWR6843


Tool/software: Code Composer Studio

CCS version : 9.2, windows 10

Launch target, group both cores, load cores with valid code, group run, code prints some statements on console after which it enters in real-time [i.e no more prints], at this point need to enable global breakpoints so trying at group level (right click with group selected and "Enable Global Breakpoints") to do this shows only one core (R4) succeeds, DSP does not. The R4 shows the "Running - Global breakpoint on" but DSP only shows "Running" and stopping R4 does not stop DSP confirming DSP  enabling was not successful. After this point if DSP is selected (while running) and attempt to enable global breakpoint on it, it does not succeed so it seems enabling global breakpoint in running state does not work for DSP. Don't know if this is a hardware limitation, if so, perhaps the GUI should prevent the group level enabling of global breakpoint in running state as it does not make sense to have only one core enabled by the definition/meaning of global breakpoint. If cores are stopped and attempt is made to enable global bp at group level, both cores succeed and feature works as expected i.e when both are running, stopping one stops the other.

  • Hi Piyush,

    I see the behavior you are describing. Actually I also see some inconsistent behavior even when trying to enable global breakpoints at the individual core level. There is some strange permutation when with the cores are executing and enabling global breakpoints. Not sure if it is by design (some resourcing thing) or a bug of some sort. I'll need to dig into this further

    Thanks

    ki