Messages

1

µTasker general / Re: fnReduceSWTimers underflow

« on: May 26, 2011, 02:39:05 PM »

Hi Mark:

I think I found the problem. Instead, you find the problem.
I have a timer in an interrupt. I did not know it was 'illegal'.
I could provoke the error after causing multiple interrupts per second.
attached Excel with the data of what has happened, if someone wants to see the event with all the data.

I modified the software so that now the timer is out of the interruption. The error has not yet appeared.

It is a bug so hard to find (I have pretty long behind him) I think it's a good idea to update the documentation of the use of timers as not to be used in interruptions. I've been searching and have not seen any note.

Thank you for everything.

A greeting.

2

µTasker general / Re: fnReduceSWTimers underflow

« on: May 24, 2011, 05:18:58 PM »

Hi Mark:

I'm still in search of error discussed.

However, I fail to understand the following operation:

UTASK_TICK RemainingTime = TimeStamp + NextFire; 
        if (RemainingTime >= uTaskerSystemTick) {
            RemainingTime -= uTaskerSystemTick;
        }
        else {
            RemainingTime = uTaskerSystemTick - RemainingTime;
        }

I think I always have to subtract the value of uTaskerSystemtick because:

uTaskerSystemTick = 0xFFFFFFFF
TimeStamp = 0xFFFFFFFE
NextFire = 0x0004

Result according to the formula of the program is 0xFFFFFFFA when it should be 3  .

Am I wrong?

I think this "possible error" is not what is happening to me because being the variables of type long, have to spend almost 500 days to do this subtraction. I have a 10 ms tick resolution.

Thanks.

3

µTasker general / fnReduceSWTimers underflow

« on: May 23, 2011, 05:46:57 PM »

Hello,

We currently have version V1.3 for coldfire M5223x uTasker.
For some strange reason, the software timers disappear. Following the path I have learned that the error is the "fnReduceSWTimers" causes a subtraction of greater value than the contents of the timer time. This causes an underflow and the timer goes down. Well, actually it is not idle, but will run after more than a year of operation.
This bug I can not specify at all, since I have not been debugging the error. Just left a mark on whether that operation was passing and it seems that it was.

I wonder if someone else has happened and as something fixed.

On the other hand, I see a correction in version V1.4 where it says "Correct Starting a new timer fires an existing Just Before"
I do not know if this arrangement would solve this error. I can not have the code for that correction V1.3 license since I have is not complete.
If this correction solve this problem, we would see how to buy the full license.

I hope I can provide some help on the subject.
Thanks.