EWSTM8 of IAR - problems with breakpoints

Dear,


I have been trying IAR EWSTM8 Beta version. This beta version has solved a problem with crashes as result of Live Watch activation and yet some improvements.
Still, one of the annoying issues with EWSTM8 is breakpoints. 
When breakpoint breaks the program, I can't run or go step-by-step, until the breakpoint is removed, so it is not so convenient. As well, sometimes I see some communication timeout errors. The 1st problem occurs in the most places in my program, but there are some places where it works properly. In my work we have 3 EWSTM8 seats and the problem is visible in everyone of them. Nevertheless, at IAR site the problem is not reproducible, so they're stuck.

I'm kindly asking here, if somebody has been facing the same problem or have some other issues, to share them here. It would be very important also to get your understanding of the problem. 

Thank you,
E.L. 

Op Fri, 21 Sep 2012 11:11:24 +0200 schreef <elil1975@yahoo.com>:
> I have been trying IAR EWSTM8 Beta version. This beta version has solved  
> a problem with crashes as result of Live Watch activation and yet some  
> improvements.

I am curious what kind of Beta version this is.  Sometimes an unofficial  
patch is sent to specific customers with problems and sometimes chip  
vendors receive a pre-release version or patch that they can sometimes  
re-distribute to their key customers.

> Still, one of the annoying issues with EWSTM8 is breakpoints.
> When breakpoint breaks the program, I can't run or go step-by-step,  
> until the breakpoint is removed, so it is not so convenient.

That sounds like you hit a hard limit of the number of breakpoints  
supported by the debug environment (debug probe + on-chip debug  
hardware).  Note that some features require a breakpoint to be available.

> As well, sometimes I see some communication timeout errors.

Communication between what and what?

> The 1st problem occurs in the most places in my program, but there are  
> some places where it works properly. In my work we have 3 EWSTM8 seats  
> and the problem is visible in everyone of them. Nevertheless, at IAR  
> site the problem is not reproducible, so they're stuck.

Do they have access to the same target board as you are using?

> I'm kindly asking here, if somebody has been facing the same problem or  
> have some other issues, to share them here. It would be very important  
> also to get your understanding of the problem.




-- 
Gemaakt met Opera's revolutionaire e-mailprogramma:  
http://www.opera.com/mail/

Dear Boudewijn Dijkstra,

Thank you for you comments.

Regarding the breakpoints, it's obviously not a matter of number of breakpoints, since if I removing a BP to another place, the problem is being solved.
IAR cannot reproduce the problem, since we work with different HW targets and source code. I thought to send that them but because I have been assuming that the project is going to be completed, I haven't done it yet.

Communication error mentioned here is the communication between the IAR debugger 
and my target by means of SWIM bus.

Best regards,
Eli