• State Answer Suggested
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 968 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.

CCS 4.0.1.01001 Can't set breakpoint in Cortex R4 target sorce file

Eugene K
Expert 1685 points

Attempt to set BP in a source file (double click on the left margin)  fails with message:

CortexR4_0: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x2d0: Error 0x20000008/-1066 Severe Error during: Break Point,  Cannot set/verify breakpoint at 0x000002D0 
CortexR4_0: Breakpoint Manager: Retrying with a Cortex breakpoint

BP is not shown in source file but appears in disassembly window. Run command stops target at the line where attempt to set BP was made. Log file is attached.

Context menu New Breakpoint->Hardware Breakpoint does not produce error message but does not show BP in the source file either.

Eugene

 

debug.zip
  • 0
    TI__Guru**** 463831 points

    Hi Eugene,

    Are you trying to debug an application in flash (HW breakpoint)? Have you loaded the symbols for that application?

    Could you provide/attach a test case? I tried to reproduce the issue with my Cortex R4 target but had no problems setting breakpoints via the editor margin for an application in flash

    ki

  • 0 in reply to Ki
    Expert 1685 points

    Hi Ki,

    Yes, I'm using flash target and symbols are loaded. Here is the breakdown of my debug session. Could you look into it and possibly find problems? I can provide test case but I can not post it on the forum. You need to contact me directly.

    - Aries EVM with SD XDS510USB

    - all code and binaries pre-exist under project folder tree (multiple sub folders)

    - run command line project creation for SDT Make. CCSv4 WS is created under project tree and all sources and binaries are linked resources outside of WS.

    - sub-project to debug has two linked binaries and CCXML file with target description. These are also linked resources. CCXML has startup GEL with OnHalt() callback

    - set CCXML as Active/Default, select CPU to connect and one of the binaries to load as symbols under debug properties.

    - start debug session. CCS prompts me to select binary to debug (why? I had it selected already) and then goes into full rebuild of the whole project even though selected binary does exist and at the end opens Debug perspective.

    - connect. CCS issues message: "CortexR4_0: GEL: Error while executing OnHalt(): target is not connected."  Disassembly shows code but there is no correlation to source file

    - load symbols. Now, source correlation is possible. My expectation was that selecting binary in debug properties will load its symbols

    - double click on the source file margin. CCS issues error message. No BP in source but there is one in disassembly window

    - run. CCS stops at the BP

    - right click on a source line and select HW BP. No BP in source but one is visible in disassembly window

    - run will stop target at those BPs

    FYI, if symbols are loaded on disconnected target source correlation is not happening after connection. Symbols have to be reloaded after connection. Wasn't this fixed in CCSv3?

     

    Thanks,

    Eugene

  • 0 in reply to Eugene K
    TI__Guru**** 463831 points

    Hi Eugene,

    Can you "start a conversation" with me? Basically click on my profile and you will see an option to start a private conversation underneath my profile picture. That way I can provide details on where to send your test case.

    Thanks

    ki

  • 0
    Expert 1685 points

    The first two errors are related to non-configured memory map on a target -  user error.

    Second and third one are isssues with source file path resolution in CCSv4.

    Thanks,

    Eugene