Hello,
I'm using MDK 4.14 for an LPC2478. Trying to catch a presumed data corruption, I'm want to halt my program when some variable (or preferably memory address?) contains a value larger than a certain constant. Now that works when the constant (=variable value) is a power of 2 and the conditional used is either "==" or "<" or "<=" but never ">" (I need that!). It complains about alignment, but nothing changed in the expression but the sign. Even a comparison with 0 (> 0, >= 0) fails, while <, <= works !
what happening here? Is there a workaround? can I compare the contents of a memory address with a constant rather than a global variable with a constant?
There have been lots of strange magic with Keil releases the last year. Me thinks that the "Keil, an ARM company" have somehow resulted in lots of tasks having been moved to different people. So there have been "Keil, a qualiity-challenged company".
You're right. I mean, it looks like the function discussed above has not been tested for a LONG time (when was 4.14 released? How come it was never fixed? How come that there are issues with breakpoints in recent releases? What is going on there!?). However, Keil products seem to be very hot nowadays - 2 colleagues returned from Embedded World recently and reported a lot of interest. But the conditional breakpoints don't work !!! ;-)
Maybe hot. But not hotter than some customers wondering about implications of getting their code ported to alternative tools.
when a giant buys a midget "cost savings" often get imposed.
At every company that I worked at that got bought layoffs followed the buyout (fortunately I was never included)
Let alone when "absorbtion" is a more precise word. I worked at a place that got "absorbed" and in the end there was 3 of us left of the ~100 the company employed before the absorbtion.
Erik