Execution Trace when using Olimex ARM-USB-OCD?


1 comment

  • Avatar


    I thought I'd follow up to say that I no longer need an answer on this... I was trying to track down a tough-to-find bug that was causing the processor to reset. I ended up finding it the old fashioned way: By setting a GPIO pin on and off around regions of code and viewing the output on a logic analyser. I was able to narrow it down to a write to a single register...

    I'm still curious about how to use the trace window in Crossworks (the manual is a lot vague), but I'll leave figuring that out to another time.


    Comment actions Permalink

Please sign in to leave a comment.