• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 53 subscribers
  • Views 764 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/TM4C129CNCPDT: The debugger doesn't break at breakpoints after upgrading from CCS6 to CCS10

Nir Blinder
Intellectual 385 points
Part Number: TM4C129CNCPDT

Tool/software: Code Composer Studio

Hello. 

I've used CCS6 to build and debug my project successfully until today, but after transferring it to CCS10, I've encountered a problem to debug it properly -

After pressings the 'debug' button and flashing the program to the CPU I'm using(CORTEX_M4_1), the console outputs the following error lines -

CORTEX_M4_1: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0xecd4: (Error -1066 @ 0xECD4) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.2.0.00002) 

CORTEX_M4_1: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0xe752: (Error -1066 @ 0xE752) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.2.0.00002) 

CORTEX_M4_1: Trouble Removing Breakpoint with the Action "Finish Auto Run" at 0xe752: (Error -2044 @ 0xE752) Internal error: Requested breakpoint does not exist. Restart the application. If error persists, please report the error. (Emulation package 9.2.0.00002)

I've already tried to search those errors online and follow suggested solutions, but it still haven't solved my problem. 

Thanks for helpers.

Have a nice day. 

  • 0
    TI__Guru**** 421380 points

    Hello,

    It sounds like the debugger memory map is not properly configured in you CCS 10 environment. Can you confirm that it is properly configured?

    Also, what exact version of CCS 10 are you using?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 385 points

    Hey, Thanks for the fast response :)

    The CCS version I'm using is 10.1.0 (I also tried to run my project with the latest version 10.1.1, but the problem also presents there).

    About the memory map:

    1. when I'm debugging the project in CCS10, the console prints me:

    CORTEX_M4_0: GEL Output:
    Memory Map Initialization Complete
    CORTEX_M4_1: GEL Output:
    Memory Map Initialization Complete

    After those lines, it prints the errors that I mentioned before.
    I also cheeked both project's GEL files, and it seems that CCS6 is also using them to debug the project(As mentioned, I'm not encountering errors when running the project in CCS6)

    Is that answering your question?

    Also, I think its maybe important to mention that we use a custom board with two MCUs(both are TM4C129CNCPDT) that connected with a JTAG chain.
    The error only occurs in the second MCU in the chain(CORTEX_M4_1).

    Thank you.

  • 0 in reply to Nir Blinder
    TI__Guru**** 421380 points

    Nir Blinder said:
    Also, I think its maybe important to mention that we use a custom board with two MCUs(both are TM4C129CNCPDT) that connected with a JTAG chain.
    The error only occurs in the second MCU in the chain(CORTEX_M4_1).

    I see. Yes that is an important bit of info.

    For the GEL file being used, are you using the same one you used with v6 or one that comes with v10? Note that if a ccxml has a relative path to the GEL file, it will be relative to the a directory inside the CCS directory of the version being used.

    If you set the first MCU to bypass, and then flash the second MCU, do you still get the error?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 385 points

    Hi,

    I am using the new GEL file that came with v10. Also tried to bypass the first mcu and still get the error.

    I have another custom board with 2 mcus(different kind) and jtag chain and there also the second MCU gives these errors while the first one is ok.

    Any idea ?

    Thank you

  • 0 in reply to Nir Blinder
    TI__Guru**** 421380 points

    Can you manually launch a debug session and connect to just the second MCU? Do not load/flash any program. Can you manually try to set a breakpoint at 0xecd4 and 0xe752 in the Disassembly view? I am expecting the debugger to automatically set HW breakpoints

  • 0 in reply to Ki
    Intellectual 385 points

    I tried to set a breakpoint at the addresses you mentioned and got an error:

    CORTEX_M4_0: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xe752: (Error -1066 @ 0xE752) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.2.0.00002)

  • 0 in reply to Nir Blinder
    Intellectual 385 points

    Also important to mention the when I connect to target I get the error :

    Break at address "0xc67c" with no debug information available, or outside of program code.

  • 0 in reply to Nir Blinder
    TI__Guru**** 421380 points

    Nir Blinder said:

    I tried to set a breakpoint at the addresses you mentioned and got an error:

    CORTEX_M4_0: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xe752: (Error -1066 @ 0xE752) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.2.0.00002)

    I assume this works fine on the first CPU, correct?

    What debug probe are you using?

  • 0 in reply to Ki
    Intellectual 385 points

    yes works fine on the first CPU.

    XDS100v2

  • 0 in reply to Nir Blinder
    TI__Guru**** 421380 points

    Nir Blinder said:

    Also important to mention the when I connect to target I get the error :

    Break at address "0xc67c" with no debug information available, or outside of program code.

    This is expected. This is not an error but simply a message from the debugger that the target is halted at an address where there is no debug information associated with it. This is expected since no program/symbols were loaded.