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.

TM4C1294NCPDT: Breakpoints disabled when running debug on Code Composer Studio with SEGGER J-Link probe

Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: SEGGER, EK-TM4C1294XL

Hi, I hope you are well.

I'm Mirko Albanese and I received via e-mail your advice to post my query in E2E. So in the following section there is my query.

When I running the debug execution in Code Composer Studio with SEGGER J-Link probe the breakpoint that I have entered are disabled when I start the debugging button.

I explain to you all the steps:

  1. Connect the J-Link to the target device via JTAG interface;
  2. Connect the J-Link to the PC host via USB;
  3. Power on the target device;
  4. Open CCS;
  5. Set a Breakpoint doing double-click next to the line number and CCS is showing a flagged box with a blu circle in the Breakpoint tab (And this is OK!);
  6. Start the debug with the debug option;
  7. After the debug launch, CCS creates a new breakpoint of the same properties of the one created (same name, same line and same type) but the icon shows a grey circle with a yellow warning symbol and next to "[S/W BP" CCS adds the strings " - disabled]".

Hope I had clarify the situation at most.

Waiting to your responce.

Kind Regards.

  • Hi Mirko,

       

    Mirko Albanese said:
    1. After the debug launch, CCS creates a new breakpoint of the same properties of the one created (same name, same line and same type) but the icon shows a grey circle with a yellow warning symbol and next to "[S/W BP" CCS adds the strings " - disabled]".

      I don't have a J-Link probe and therefore, can't really try to reproduce the issue. Are you saying the original breakpoint will be lost after the debug launch? I will need to forward your post to our CCS experts for some comments about the behavior. 

  • Hi Charles,

    Yes, sort of. When I click the debug button, all the breakpoint becomes disabled.

    Thank you so much.

  • Hello Mirko,

    Mirko Albanese said:
    After the debug launch, CCS creates a new breakpoint of the same properties of the one created (same name, same line and same type) but the icon shows a grey circle with a yellow warning symbol and next to "[S/W BP" CCS adds the strings " - disabled]".

    Can you provide a screenshot of the Breakpoints view that shows this?

    Also provide the CCS version and  J-Link driver version you are using.

    Thanks

    ki

  • Hello Ki,

    Here is the Breakpoint view on the breakpoint tab after pressing the debug button.

    The CCS version: 10.2.0.

    The J-Link driver version: 2.70.8.0

  • What happens when you try to enable it? Is it successful?

    The J-Link driver version: 2.70.8.0

    CCS 10.2.0 should come with 6.44.0.b. Can you confirm your version (Help -> About Code Composer Studio -> Installation Details)?

    Thanks

    ki

  • I can enable it only when the target is halted (aka execution paused) and then yes, it becomes succesfuly activated.

    I have two SEGGER J-Link, 6.44.0.b and 1.0.1.0.

  • Mirko Albanese said:
    I have two SEGGER J-Link, 6.44.0.b and 1.0.1.0.

    Thanks. That is the same versions I have with my CCS installation.

    I am unable to reproduce the issue with my EK-TM4C1294XL. 

    One thing that comes to mind is that you are trying to set a breakpoint on a source line where there is no associated code. But then it should try setting it on the next closest source line with code.

    Would it be possible to possible to provide a reproducible test case? I don't need the actual full project, it can be a stripped down version (the simpler the better) as long as the issue can be reproduced.

    Thanks

    ki

  • Hi,

    Sorry for the late reply, actualy I can't share code/stripped down version, but i want to try to use other target device in order to reproduce the same issue.

    I'll be back soon with news about it.

  • Hi Ki, 

    Please can you share your debug configuration? I changed with a different target but I reproduced the same issue. 

    Maybe is my fault with some debug inadequate configuration.

    Kind regards.

  • I've attached the target configuration file that I was using:

    /cfs-file/__key/communityserver-discussions-components-files/312/2818.target_5F00_config.ccxml

    To be honest, I don't think it will make a difference. The issue you are seeing is usually not related to the target configuration being used.

    Is optimization enabled for your project?

    Thanks

    ki

  • All the optimization are disabled

  • Thanks. We can rule out optimization then.

    To debug this further, a test case would be very helpful. Again, it can be a very simple example (even like "hello world"). The only requirement is that you can reproduce the issue with it.

  • I created a new "HelloWorld" CCS project, loaded the helloworld.out file inside the MCU, i setted a brekpoint just before the code print line and it worked!! The breakpoint doesn't becomes disabled and then CCS stops the execution in that point.

    The only different things, excluding the size of the project, is the loaded file: Until today I have always uploaded a .elf file, is that correct? Maybe .elf file is not suitable?

  • ELF is the default these days so that is not the issue.

    It must be something specific to that project/application. Perhaps you can strip down that project to the point that any sensitive information is removed, but the issue can be reproduced?