• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 1311 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 v6.0.0.156 - Failure setting breakpoint

Vasili Galka
Expert 2690 points
Other Parts Discussed in Thread: AM3359

Hi,

Setup: CCS v6.0.0.156, Blackhawk XDS560v2 JTAG, AM3359 based board.
Code: Simple program based on SYS/BIOS Swi example (attached below).
Compiler: GCC 4.8.1 under Cygwin. Debug info configured to "-gdwarf-3 -gstrict-dwarf" which is claimed to be supported by CCS.

CCS source files path mapping configured to recognize Cygwin paths.

Scenario A
1. Connect to AM3359 Cortex-A8 target.
2. Reset, load ELF (CCS finds the source files correctly).
3. Step by step (or use run to line) to get to main (at address 0x80002c1c).

This scenario works fine. It demonstrates that all the debug info is loaded, the source files found and the target runs fine up to main().

Scenario B
1-2. Same as scenario A.
3. Open Swi.c in CCS (already opened from running previous scenario). Try putting breakpoint at main() by double clicking any line. The breakpoint is added but disabled:

4. Try enabling the breakpoint by the check-box in Breakpoints pane. The following error pops up.


Seems like a bug to me, is there a good reason why CCS should not recognize the code associated? I can manually locate main in dis-assembly view and put breakpoint and then in works fine. But that's very uncomfortable.

2818.Swi.zip


Best,
Vasili

  • 0
    TI__Genius 16180 points

    Hi Vasili,

    In Scenario B, did you load symbol? I was able to set a breakpoint in main by loading the attached out file, open the Swi.c file and double clicks on the margin in the editor.

    Patrick

  • 0 in reply to Patrick Chuong
    Expert 2690 points

    Hi Patrick,

    I've loaded the out file, it is supposed to load symbols from it, isn't it? In any case, I think the symbols were loaded since when I run by stepping through the assembly (Scenario A) it shows the symbols.

    That is very weird that it works for you but does not work for me. Are you using the same CCS version? What JTAG debugger do you use? What else can be different and have the effect? How can we figure out why it does not work in my case?

    Best regards,
    Vasili

  • 0 in reply to Vasili Galka
    TI__Genius 16180 points

    Hi Vasili,

    I am running CCS 6.0.0.00153 with XDX560 connecting to a Beagle board. My setup is not exactly the same as what you have, I only need the A8 on the Beagle to load the symbol files that you have attached.

    Are you launching the debug session with a project or without a project? I simply launch the debug session from the target configuration view by right clicking on the ccxml file, launch the debug session, load symbols, open the source file and set a breakpoint. I can see the breakpoint in the Breakpoints view resolved to a valid symbol.

    Patrick

  • 0 in reply to Patrick Chuong
    Expert 2690 points

    Hi Patrick,

    This is really strange. I fail reproducing the problem now too. Although it was quite consistent every time I tried it a while ago. Don't know what has changed. I'll get back to you if I bump into it again.

    Thanks,
    Vasili