• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 1018 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.

Problem placing breakpoint (seeing symbols) in first file of a UNION in CCS4

Andrew Goblirsch
Prodigy 20 points

Other Parts Discussed in Thread: TMS320F2812

Here is my original issue report to TI:

I am using a CCS v4.2.4.00033 to debug a tms320f2812. I have a UNION in my linker file to do a memory overlay (See linker in zip file). When I try to place a breakpoint in the first file listed in the UNION the breakpoint does not get set properly (it shows up greyed out with an exclamation point on it). When I go into the breakpoint manager and try to enable it I get the following error message: No code is associated with "eva_reg_isr.c", line 65 in any loaded symbols. If I reverse the order of the 2 sections listed in the GROUP in the first part of the UNION I then get breakpoint problems with the other section and am able to set breakpoints in eva_reg_isr.c. Since the problem follows the first file in the UNION, is there a bug in CCS v4 where the first symbol in the first GROUP of the UNION is getting overwritten with the first symbol of the 2nd GROUP (since the run address is identical)?

 

Update: The code size of the first object of the UNION makes a difference. If I comment out one of the instructions in the file I can then set a breakpoint (IDE can find the symbols).

Attached is a screenshot of the error I get in CCSv4. I've also in included a simplified project.

Is this a CCS bug? Has anyone seen this issue, have a solution? Thanks.

2260.temp_overlay_prob.zip1072.Breakpoint problem screenshot.docx

  • 0
    TI__Guru**** 173310 points

    Andrew,

    Thank you for providing a simple reproducible test case. With your project I was able to reproduce the behavior you describe. It is certainly odd that the size of the first code section affects whether the symbol association with that source file works or not. I ran the example on both CCS 4.2.4 and 5.1.1 and noticed the same behavior in both.

    I have entered a bug report in our system so the debugger experts can analyze it further. The tracking # is SDSCM00043250. If they have additional comments/workarounds after analyzing the issue we will update this thread.

  • 0 in reply to AartiG
    Prodigy 20 points

    AartiG,

    I haven't heard anything on this yet, do you have an update on this bug? This makes it extremely hard to debug my code.

    Thanks,

    Andy

     

  • 0 in reply to Andrew Goblirsch
    TI__Guru**** 173310 points

    Andy,

    This bug has been added to the list to be fixed for CCS 5.2.1, which I believe is currently scheduled for 3Q2012.