Debug problem with usb tap: very slow execution

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Debug problem with usb tap: very slow execution

3,327 Views
lambtron
Contributor I
I'm using usb tap with cw 6.4 build 6 to debug my 52233 project. The firmware is too large for ram, so it's been flashed.
 
When the source code is displayed in Mixed mode, the debugger single steps through the code very quickly. When I display only the C source code, however, the debugger pauses for several seconds for each and every C statement executed, even if it is a very simple statement that corresponds to only a few machine language instructions. And when I run "full speed" to a breakpoint (regardless of the source display mode), the debugger takes an extraordinarily long time to execute the code.
 
Please help! What could be the problem here?
Labels (1)
0 Kudos
Reply
3 Replies

1,347 Views
lambtron
Contributor I
The access size in the .mem file doesn't appear to be related to this problem.
 
I was able to clear this up by touching all source files and then rebuilding the project.
0 Kudos
Reply

1,347 Views
Muneer
Contributor II
hi

I'm facing similar problem, but i'm using CW Ethernet TAP pro, CW v8.7 and MPC860 PQ I
I changed in .mem file also but in RAM it s writing byte by byte only...

Any other place we want to change to write 32 bits?
0 Kudos
Reply

1,347 Views
Black
Contributor I
Please check this thread for the download speed issue. The access size from .mem file might also affect the debugging speed. Please modify your .mem file accordingly.
 
If the problem remains, please log a service request here and attach an example CodeWarrior project where this issue is reproducible.
 
Thank you,
Black
0 Kudos
Reply