• State
  • Locked Locked
  • Replies 12 replies
  • Subscribers 53 subscribers
  • Views 1094 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.

Original question:

Trouble setting breakpoint CCS6.1.1 Multiple Tiva processors with XDS200

CCS/TM4C1294NCPDT: ERROR: Trouble Setting Breakpoint with the Action "Terminate Program Execution"

Alan Goran
Prodigy 110 points
Part Number: TM4C1294NCPDT

Tool/software: Code Composer Studio

Hello,

I am using a TI XDS200 USB Debug Probe to download code and debug two TM4C1294NCPDT microcontrollers. Loading the program into the MCUs seem to be working fine but I keep getting an error (see below). I have also tried to unchecked one of the CORTEX_M4 under the main tab in debug configurations so that it debugs only one of the MCUs, for simplicity reasons, but I get the error anyway. Your help is greatly appreciated.

This is what the console says:

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

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

And when I type in eval("DEBUG_DumpBreakpoints()") in Scripting Console, this is what I get: 

CORTEX_M4_1: Breakpoint Manager Dump: Total Allocated Logical Breakpoints: 14

CORTEX_M4_1: Breakpoint Manager Dump: Total Allocated Software Physical Breakpoints: 16

CORTEX_M4_1: Breakpoint Manager Dump: Total Allocated Legacy Hardware Physical Breakpoints: 0

CORTEX_M4_1: Breakpoint Manager Dump: Total Allocated 55 Hardware Physical Breakpoints: 0

CORTEX_M4_1: Breakpoint Manager Dump: Total Allocated Thread Physical Breakpoints: 0

CORTEX_M4_1: Breakpoint Manager Dump:

CORTEX_M4_1: Breakpoint Manager Dump: Enabled: 0

CORTEX_M4_1: Breakpoint Manager Dump:

CORTEX_M4_1: Breakpoint Manager Dump: Disabled: 5

CORTEX_M4_1: Breakpoint Manager Dump:

CORTEX_M4_1: Breakpoint Manager Dump: Hardware Configuration

CORTEX_M4_1: Breakpoint Manager Dump: Location: "C$$EXIT" (0xa6ec)

CORTEX_M4_1: Breakpoint Manager Dump: Debugger Response

CORTEX_M4_1: Breakpoint Manager Dump: Condition:

CORTEX_M4_1: Breakpoint Manager Dump: Skip Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Current Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Action: Terminate Program Execution

CORTEX_M4_1: Breakpoint Manager Dump: Miscellaneous

CORTEX_M4_1: Breakpoint Manager Dump: Group: Default Group

CORTEX_M4_1: Breakpoint Manager Dump: Name:

CORTEX_M4_1: Breakpoint Manager Dump: Breakpoint set by the system

CORTEX_M4_1: Breakpoint Manager Dump:

CORTEX_M4_1: Breakpoint Manager Dump: Hardware Configuration

CORTEX_M4_1: Breakpoint Manager Dump: Location: "C$$IOE$$"

CORTEX_M4_1: Breakpoint Manager Dump: Debugger Response

CORTEX_M4_1: Breakpoint Manager Dump: Condition:

CORTEX_M4_1: Breakpoint Manager Dump: Skip Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Current Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Action: Process CIO

CORTEX_M4_1: Breakpoint Manager Dump: Miscellaneous

CORTEX_M4_1: Breakpoint Manager Dump: Group: Default Group

CORTEX_M4_1: Breakpoint Manager Dump: Name:

CORTEX_M4_1: Breakpoint Manager Dump: Breakpoint set by the system

CORTEX_M4_1: Breakpoint Manager Dump:

CORTEX_M4_1: Breakpoint Manager Dump: Hardware Configuration

CORTEX_M4_1: Breakpoint Manager Dump: Location: "SVC_Handler"

CORTEX_M4_1: Breakpoint Manager Dump: Debugger Response

CORTEX_M4_1: Breakpoint Manager Dump: Condition:

CORTEX_M4_1: Breakpoint Manager Dump: Skip Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Current Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Action: Semi hosting

CORTEX_M4_1: Breakpoint Manager Dump: Miscellaneous

CORTEX_M4_1: Breakpoint Manager Dump: Group: Default Group

CORTEX_M4_1: Breakpoint Manager Dump: Name:

CORTEX_M4_1: Breakpoint Manager Dump: Breakpoint set by the system

CORTEX_M4_1: Breakpoint Manager Dump:

CORTEX_M4_1: Breakpoint Manager Dump: Hardware Configuration

CORTEX_M4_1: Breakpoint Manager Dump: Location: "C$$EXITE"

CORTEX_M4_1: Breakpoint Manager Dump: Debugger Response

CORTEX_M4_1: Breakpoint Manager Dump: Condition:

CORTEX_M4_1: Breakpoint Manager Dump: Skip Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Current Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Action: Terminate Program Execution

CORTEX_M4_1: Breakpoint Manager Dump: Miscellaneous

CORTEX_M4_1: Breakpoint Manager Dump: Group: Default Group

CORTEX_M4_1: Breakpoint Manager Dump: Name:

CORTEX_M4_1: Breakpoint Manager Dump: Breakpoint set by the system

CORTEX_M4_1: Breakpoint Manager Dump:

CORTEX_M4_1: Breakpoint Manager Dump: Hardware Configuration

CORTEX_M4_1: Breakpoint Manager Dump: Location: "C$$IO$$"

CORTEX_M4_1: Breakpoint Manager Dump: Debugger Response

CORTEX_M4_1: Breakpoint Manager Dump: Condition:

CORTEX_M4_1: Breakpoint Manager Dump: Skip Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Current Count: 0

CORTEX_M4_1: Breakpoint Manager Dump: Action: Process CIO

CORTEX_M4_1: Breakpoint Manager Dump: Miscellaneous

CORTEX_M4_1: Breakpoint Manager Dump: Group: Default Group

CORTEX_M4_1: Breakpoint Manager Dump: Name:

CORTEX_M4_1: Breakpoint Manager Dump: Breakpoint set by the system

Best,

Alan

  • 0
    TI__Guru**** 449131 points

    Hi Alan,

    Alan Goran said:
    I have also tried to unchecked one of the CORTEX_M4 under the main tab in debug configurations so that it debugs only one of the MCUs, for simplicity reasons, but I get the error anyway.

    Did you try setting one of the MCUs in bypass in your target configuration file? If not, can you try it and see if you get the error?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 110 points

    Hi Ki, 

    Thanks for your answer. Yes I did try that, it did not help and I still get the error. 

  • 0 in reply to Alan Goran
    TI__Guru**** 449131 points

    Can you enable debugger logging and reproduce the issue? Then zip up the generated log and attach it to this thread.:

    https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

    Also, which exact version of CCS are you using? Based on your emulator pack version (8.4.0.00006), it sounds like an older version of CCS.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 110 points

    My CCS version is (9.3.0.00012), which is the latest version I think. But like you pointed out the emulator pack version is an older version, I guess its because the project was created with the old CCS version. Either way, I have now updated the emulator pack version to (9.1.0.00001) and tried again, but I get the same error still. The debugger logs is attached below and it is done with the newer version of emulator pack.

    Debug_Server_Log[1].zip

    Thanks a lot, 

    Alan

  • 0 in reply to Alan Goran
    TI__Guru**** 449131 points

    Thanks Alan,

    I'll get the logs analyzed and keep you posted of any updates I get.

    ki

  • 0 in reply to Ki
    TI__Guru**** 449131 points

    Hello Alan,

    Would it be possible to obtain the *.out file you are trying to load? If you do not wish to share it publicly, please start a private conversation with me.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 110 points

    Hello Ki, 

    Sorry for the delayed response .Unfortunately, I cannot share the .out file due to company confidentiality. But I do not think there is anything off with the .out file, since my colleague uses the same code, same debugger, same version of CCS and he does not get this error. Everything works fine on his computer. I have even manually copied all of his debug configurations and the error is still not going away. 

    Is there any other way you can help me without having to send the .out file? Did you find anything abnormal in the debug logs? Please let me know if I can assist in solving this problem of mine. 

    Again, thank you very much for your help. It is greatly appreciated. 

    Alan

  • 0 in reply to Alan Goran
    TI__Guru**** 449131 points

    Alan Goran said:
    But I do not think there is anything off with the .out file, since my colleague uses the same code, same debugger, same version of CCS and he does not get this error. Everything works fine on his computer. I have even manually copied all of his debug configurations and the error is still not going away. 

    Are you and your colleague using the same GEL startup file (if one is being used at all)? Can you provide a screenshot of your debugger memory map? I'm most interested in the range that includes 0xA6EC

    Also if you can provide a screenshot of the disassembly view at that address, that would be helpful.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 110 points

    Yes we are using the same GEL startup file. Below is the requested screenshots

  • 0 in reply to Alan Goran
    TI__Guru**** 449131 points

    Can you show me the Disassembly view of 0xA6EC (and surrounding range)? Can you manually set a breakpoint in the Disassembly view of that address?

  • 0 in reply to Ki
    Prodigy 110 points

    I can not manually set a breakpoint in the Disassembly. It gives me an error. 

  • 0 in reply to Alan Goran
    TI__Guru**** 449131 points

    I do not know why the debugger is unable to set breakpoints at that address. The debugger memory map identifies it as valid readable memory, and hence a HW breakpoint should work. I can set a breakpoint at that address using my TM4C1294 Launchpad. SInce the same exact setup works on a colleagues PC, I'm wondering if there is some issue with your installation. I'm wondering if you can try a clean new installation of CCS - perhaps try the latest CCS 10.0. Sorry to having to suggest you install another CCS version but I'm not sure what next to try,

    ki