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: Lines advancing in Dissasembly window, but not in source code window



Tool/software: Code Composer Studio

Hello all,

While debugging, the line highlighting is advancing in the dissassembly window, but not in the source code window. This makes debugging more challenging than I would prefer.

I have tried reinstalling, creating a new project, using step into, step over, assembly step into, assembly step over buttons with no success.

Running the code via Blackhawk XDS100V2 emulator on the the Beaglebone Black Rev3.

Any help would be much appreciated!

-Tyler

  • Hello Tyler,

    That is interesting. I can't seem to reproduce that behavior (it works as expected for me). What CCS version are you using? And can you send me a little test case? It can be your project or a stripped down version of it as long as I can run it.

    Thanks

    ki

  • Hello,

    I am one of Tyler's students—he was posting this thread on my behalf.  The CCS version is 10.1.1.  This error does not occur in CCS version 8.3.1, but I would like to use v10, as it is the only version I can get running on Arch Linux.  (I have CCS v8 & v10 on Windows 10.)  The behavior is the same on Windows and Linux, so long as I'm using CCS v10.

    Here is the project I am using to learn CCS: HallArrayMult.zip

    An error was being suppressed when I talked with Tyler which may shed light on the situation: "Break at address "0x80000078" with no debug information available, or outside of program code."  That error comes up at every line of code except for the first executed line of sample.s, LDR R1, =MULTIPLICANDS.  Highlighting advances correctly to that line, but not to any other line.

    Here is another picture:

  • Zachary,

    Thanks for the test case. I am able to reproduce the issue. And I see the same behavior - works with 8.3.1 but not with 10.1.1.

    I filed a bug for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-10086

    Thanks

    ki