S/W breakpoints on CCS5.4

Hi,

 Since software breakpoints are implemented in software, their number is virtually unlimited. So long as there is memory on the host to store the breakpoint information, a software breakpoint can be implemented. However, software breakpoints can only be used in RAM. If the target memory cannot be written to, then the breakpoint op-code cannot be inserted. If it’s necessary to set a breakpoint in ROM, Hardware Breakpoints should be used.

First of all did you try by setting s/w bp when your code executes only through RAM? (no flash involvement) 

I guess what you're facing is some kind of memory conflict issue which is not allowing you to set the bp.

Regards,

Gautam

Thanks for your response, Gautam.

Yes, address 0x200019c0 is a ram location. When I enter tha address as the breakpoint, CCS5.4 declares it to be a H/W BP. When I try to enable the breakpoint, it tells me that it is out of range. This is obviously true for a H/W BP. Why can't I set it as a S/W BP. I do have S/W BPs enabled in the options.This appears to be a bug in CCS5.4, would you say?

Pat

Pat Harris said:

I am trying to set a breakpoint in RAM at location 0x200019c0. This is a ramfuncs routine that is transferred to ram from flash on power up. CCS5.4 will not let me enable the breakpoint there claiming it is out of range. I tried to set this address as "breakpoint" but it comes up as H/W BP.

Which device are you using? Are you sure that address is a valid address not only on the device but also to the debugger? In the CCS Debug perspective you can go to menu Tools->Memory Map and that will show you the memory map as seen by the debugger. Is the address you are trying to set a breakpoint at listed here as a valid RAM address?

AartiG,

Thanks for your reply. Yes, this address is a valid R/W location on the f28m35h52c1 and it is listed on the debug ->tools -> memory list.

Thanks,

Pat

Yes, this is valid memory on the M3 core of the F28M35H52C1. How exactly are you trying to set the breakpoint? From the breakpoints view or by double-clicking on the line margin in the editor or disassembly view? Are you sure the M3 core is selected and in focus in the Debug view when you are setting this breakpoint?

It is difficult to say what may be happening without reproducing the behavior. If you could send us detailed steps to reproduce the issue (including a project or .out file, if possible) and possibly screenshots that capture the error, that would be very helpful in enabling us to reproduce the behavior and look into it further.