• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1612 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.

Error enabling this function: Target Access Failed

Bruno Saraiva
Guru 13040 points

Other Parts Discussed in Thread: TM4C1294NCPDT

Hi there,

I'm using CCS Version: 6.0.0.00190, on a Windows 7 Pro SP1 64-bit. Developing on a EK board which has the Tiva TM4C1294NCPDT uC, via USB ICDI interface.

Most times while I am running the debugger and I try to add a breakpoint, I get an error window with the message:

"Error enabling this function: Target Access Failed"

Sometimes I work around it by pausing the code, adding the breakpoint and resuming. Other times this would result on a new "code" windows with a red message saying something like "the code is not available, would you like to view the assembly" (couldn't reproduct that message this morning so the wording is not exact).

Further, while I am following the code execution line by line using the F6 key, it seems that the flow is not linear, it bounces up and down through the lines... That seems weird, I am coming from a few years using IAR and never seen that.

I guess the main question is what is the "Error enabling this function" message? How do I fix that?

But any other comments on the other symptoms are welcome.

Cheers

  • 0
    TI__Guru**** 477651 points

    Hi Bruno,

    Bruno Saraiva said:
    I guess the main question is while the "Error enabling this function" message? How do I fix that?

    The debugger normally needs the target halted to set a breakpoint. Hence why pausing the target and then setting a breakpoint would work.

    Bruno Saraiva said:
    Other times this would result on a new "code" windows with a red message saying something like "the code is not available, would you like to view the assembly" (couldn't reproduct that message this morning so the wording is not exact).

    This means that where you halted, there was no source code correlation for that location. It could be you were halted in code from a library that was not compiled with any debug symbols.

    Bruno Saraiva said:
    Further, while I am following the code execution line by line using the F6 key, it seems that the flow is not linear, it bounces up and down through the lines... That seems weird, I am coming from a few years using IAR and never seen that.

    If you have optimization enabled during the build, that would explain the non-liner behavior of the source lines since code would get moved around and such.

    Hope this helps

    ki

  • 0 in reply to Ki
    Guru 13040 points

    Perfect reply, thanks you! It makes all the sense!!!

    Just as an additional curiosity/wish, is there something that can be enabled to allow for adding a breakpoint without pausing?

    IAR allows such, and it makes debugging a bit more practical, since you just leave things running, scroll the code to where your concerns are and add a break there, particularly to watch variable values. Or maybe there is a different "pause here" concept in CCS which I am blind to?

  • 0 in reply to Bruno Saraiva
    TI__Guru**** 477651 points

    Bruno Saraiva said:
    AR allows such, and it makes debugging a bit more practical, since you just leave things running, scroll the code to where your concerns are and add a break there, particularly to watch variable values

    What is happening is that when you set that breakpoint in IAR, the debugger will momentarily halt the target, set the breakpoint, and then autorun again. It happens so fast that to the user, it looks like the target was never halted. Old CCS used to work the same way. But people got confused because they assumed the target was never halted. The consensus was that people do not like debugger auto-halting the target under the hood. So this behavior was changed in recent CCS version where the target is never auto-halted. Now there is an option where you can enable this behavior back on. It is in the debugger options:

    But I have been playing around with this just now and it doesn't seem to work for me. Unless the behavior of this changed, it looks like a bug. I'll have to investigate further.

    ki

  • 0 in reply to Ki
    TI__Guru**** 477651 points

    It looks like a bug to me. I filed one. Tracking ID: SDSCM00050528

  • 0 in reply to Ki
    Expert 2070 points

    Any update on this?

    Few days ago, I have experienced same problem (after CCS update.) Fresh CCS6 install fixed it.

    However, today I was trying to debug my Tiva code and the same thing is happening. I was able to debug my code  on the same board before.