• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 2720 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using ULink debugger with XC164CS

Paul Shipley

Hi,

Has anyone had problems when debugging with the ULink USB adaptor? I'm using it on the Infineon XC164CS development board, which has the standard 'wiggler' interface, but I'm having a few problems particularly when using breakpoints.

One of the problems I had was trying to locate the source of some stack corruption I was experiencing. Something was overwriting the end of the stack, which happened to be at address 0xC668. I set a breakpoint to stop the program whenever 0xC668 is written to. The program stops at my initialisation code as expected, but uVision 2 crashes when I run the code again. In this situation, I have to go through task manager to quit uv2.exe.

Other problems wrise if I am stepping through some code like this:

if ( !led_output_ready() )
{
  do_something();
}

If the if statement contains a function like that above, then there is strange behaviour when stepping through the code. Instead of moving on to the next line, the program runs one full iteration of the main loop, and then stops on the next line. It's almost as if when stepping through, the debugger places a breakpoint on the next line and then runs the code, but it is missing the breakpoint first time round (if you see what I mean!!!).

Has anyone had any experience of this? Is there a way to solve these problems? I have tried to reinstall the driver as described at http://www.keil.com/support/docs/2418.htm but to no avail. Any advice will be greatly appreciated.

Thanks,
Paul.

Parents
  • 0 in reply to Stefan Fricke

    Hi Stefan,

    Thanks for your reply.

    I've managed to make some progress using different combinations of breakpoints and debug code.

    I did mention Wiggler, but this was a mistake on my part. I was using Wiggler until the ULink arrived, but neither connection method seems to be without its flaws. As for the actual physical connection, I think it is OK since debugging seems to fail only when performing certain activities, such as those mentioned in my first post, above.

    I will bear in mind your comments about using Memtool, it may make a difference when debugging in future.

    It is frustrating when a debugger causes your entire PC to crash - I'll have to invest in a CD of calming beach noises to play next time it happens!

    Thanks,
    Paul.

Reply
  • 0 in reply to Stefan Fricke

    Hi Stefan,

    Thanks for your reply.

    I've managed to make some progress using different combinations of breakpoints and debug code.

    I did mention Wiggler, but this was a mistake on my part. I was using Wiggler until the ULink arrived, but neither connection method seems to be without its flaws. As for the actual physical connection, I think it is OK since debugging seems to fail only when performing certain activities, such as those mentioned in my first post, above.

    I will bear in mind your comments about using Memtool, it may make a difference when debugging in future.

    It is frustrating when a debugger causes your entire PC to crash - I'll have to invest in a CD of calming beach noises to play next time it happens!

    Thanks,
    Paul.

Children
  • 0 in reply to Paul Shipley

    Hi Paul,

    thanks for answer.
    I tested a similar code like yours, but I
    got no crash results.
    I did a test with different PC's and OS.
    I tested with WIN98, WIN2K and colleaque did
    a test under WINNT4.0 (SP6).
    So may be that difficulties occur with XP or
    ME ?

    What about your driver settings for OCDS Driver XC16x ?
    I checked
    "Load application at startup"
    "Go till main()"
    Under 'restore debug session setting'
    "Breakpoints",
    "Toolbox",
    "Memnory Display"
    Under 'Settings'
    "KEIL ULINK"
    unchecked all --> 'CACHE OPTIONS'
    unchecked all --> 'RESET CONFIGURATION'
    ( last depends from your hardware )

    Since I do not know your versions:

    If you have a option "OCDS break level" do not set to values less the highest possible, or better get a newer version.

    There were some difficulties with background debug process as I remember.
    This option is not available anymore with newer versions.

    BTW:

    Which STACK is overwritten ?
    If I hold the userstack internal via USERSTACKDPP3 than I place it at memory range
    00Cxxxh.
    Do you deal with idata or sdata ?
    OK - this should not be relevant , but who knows ...

    Stefan