• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 250 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0G3519: automatic load program in multi-debug session CCS V20

DavidV
Prodigy 30 points
Part Number: MSPM0G3519

Tool/software:

Hi,

I'm trying to automate the startup process for a multi-debug session. In other words, I would like the .out file to be loaded automatically after connecting to the target.

I figured out that to achieve this, I need to modify the GEL file, so I added the following code:

OnTargetConnect()
{

       GEL_Load("c:\\mydir\\myfile.out", "cpu_a", "Emulator");

}

However, the program is not being loaded.

Any suggestions?

Thanks!

  • 0
    TI__Mastermind 24405 points

    Hi DavidV,

    Which GEL file you modify, mspm0_cs_dap_init.gel or the device.gel, or something else you manually set?

    B.R.

    Sal

  • 0 in reply to Sal Ye
    Prodigy 30 points

    first I modified the device.gel and then I tried with a custom file in which I wrote only the code above

  • 0 in reply to DavidV
    TI__Mastermind 24405 points

    Thanks.

    I will forward the thread to tool & compiler team for the suggestions on this topic.

    B.R.

    Sal

  • +1
    TI__Guru**** 463901 points
    DavidV said:
    I'm trying to automate the startup process for a multi-debug session. In other words, I would like the .out file to be loaded automatically after connecting to the target.

    I would do this in the launch configuration:

    https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-main.html#launch-configurations

    See the second screenshot in the above section for an example of auto-loading different programs to different cores of a multi-core debug session.

    Thanks

    ki 

  • 0 in reply to Ki
    Prodigy 30 points

    thank you very much for your suggestion.

    Now it works as I wanted. When I start the debug session, the program is loaded onto each core, ready for debugging. However, there is another issue. When I launch the debug, In the Debug Output view, I see these messages for every core after the program is loaded:

    CORTEX_M0P: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0xa64e: (Error -1001 @ 0x0) Requested operation is not supported on this device. (Emulation package 20.0.0.3283)
CORTEX_M0P: Breakpoint Manager: Retrying with a AET breakpoint
CORTEX_M0P: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x553c: (Error -1066 @ 0x553C) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 20.0.0.3283)
CORTEX_M0P: Breakpoint Manager: Retrying with a AET breakpoint

    Despite this, the debugging works, but every time I add a breakpoint, a similar message appears, even though the breakpoint functions correctly.

    CORTEX_M0P: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x5552: (Error -1066 @ 0x5552) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 20.0.0.3283)
CORTEX_M0P: Breakpoint Manager: Retrying with a AET breakpoint

  • +1 in reply to DavidV
    TI__Guru**** 463901 points

    It looks like the debugger tried setting a software breakpoint in flash (which won't work) and then switched to attempting to use a hardware breakpoint (which I assume was successful). This typically happens if the debugger memory map is not set. The debugger memory map is typically set in the startup GEL file. is the debugger memory map being initialized correctly?