Can't set point Problem Solved!

  According to this docment, i solved the problem finally!  

  the docment as follows:

'Can't Step' and 'Can't set point' errors

Description
When debugging with Multi-ICE or EmbeddedICE, the message 'Can't Step' may be displayed when trying to set a breakpoint. This is normally associated with trying to set a third breakpoint on ROM based code.

Solution
The EmbeddedICE Logic within the core of the ARM7TDMI contains two watchpoint units. These can be used to set a variety of breakpoints or watchpoints. For example:
Two hardware breakpoints on ROM 
One hardware breakpoint on ROM, multiple software breakpoints on RAM 
Whether a software breakpoint or hardware breakpoint is used is determined as follows. If there is a watchpoint unit free, then a hardware breakpoint will be set. If not, then a software breakpoint will be set.

However a software breakpoint can only be set on memory that is writeable by the ARM (i.e RAM). The target hardware MUST provide word, half-word and byte write access for this to work, (i.e. the memory controller must decode the MAS signal correctly), otherwise it will not be possible to set Thumb software breakpoints (only hardware ones will be possible) and an error message like "Can't set point" will be displayed, even if the breakpoint is being set on RAM.

When Multi-ICE or EmbeddedICE tries to set a software breakpoint, it will examine the memory afterwards to see if the breakpoint instruction has been written successfully. If it hasn't (e.g. for code in ROM) then it knows that software breakpoints cannot be set and will then either use a hardware breakpoint (if a unit is available) or report an error (e.g "Can't step").

A couple of other points to note here:

i) Stepping will cause a breakpoint to be set on the next instruction.
ii) Vector catch and semihosting will make use of breakpoints, though the debugger will not show this in the breakpoint window.

So,the method is check off the semihosting !