I have been looking all day and can't find anywhere so that when I'm stepping through code using codewarrior and the BDI2000 debugger that it will step line at a time as opposed to stepping through the assembly.
I changed the view to view source code, however I have to step multiple times to execture every command.
Does anyone know a quick fix?
Hi, has there been a solution reached for this problem? I am encountering similar problems while trying to debug a MPC855T using the BDI2000 with Codewarrior Classic for PA v8.8.5.
After hitting a breakpoint, I can step through assembly code and "mixed" view assembly just fine. When I try to step through the C in "source" view, the protocol log shows bunches of stuff happening, but the program counter never advances. Furthermore, when instructing it to go (F5), it immediately breaks and never advances past the current line, even after removing the breakpoint.
After further testing, I've found that something about setting or reaching a breakpoint causes the instruction cache line corresponding to the breakpoint location to become corrupted. That is, it is no longer a reflection of the actual instruction memory. When I disable cache, either in my program, or in the debugger, I am able to step past the breakpoint. This problem occurs for me when using either the USBTAP or the BDI2000. I do not wish to disable the cache - anybody have any experience with this issue?
Without knowing which CW you are using to debug which architecture I don't think we can help. Please provide all the info as requested by the "[IMPORTANT] When Asking about CODEWARRIOR !!!" sticky post in the head of this forum.
Wild guess: Are you building with debug information?
Daniel
Using ABATRON BDI2000 hardware debugger.