This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

floating point in cortex m0, always reset.

hi,I write an algorithm running in cortex M0. It has some floating point multiplication.But the program always resets when encounter a floating point multiplication.And the code showed below:

    for (k = 0; k < 4; k++) { tmpx =   dbuffer[0] * a[k + 1]; dbuffer[k + 1] = dbuffer[k + 1] - tmpx; }  


dbuffer[] and a[] are float array. tmpx is a float variable. When I debug the program, the M0 resets at line "tmpx = dbuffer[0] * a[k + 1];" .And the value of dbuffer[0] is 1429983,a[k+1] is 0.00974910986.
I have tested this multiplication in a new project.And the code goes well and result is right.The test code is like below:

            float a = 1429983; float b = 0.00974910986; float c; c = a* b;  


So, I know M0 use softVFP. I have seen asm code such as __aeabi_fmul corresponding to my code.
Could anybody tell me what's wrong with my code?
Thank you very much.

Parents
  • Does your main() end in an infinite loop ?

    -If not, it should; becaues on a microcontroller, main() is not supposed to return.

    I'm only asking in case your for-loop is placed inside main; if it's outside main, then a stack overflow of a single element will erase the return-address, if the array is the first (or only) variable on the stack.

    This is because the return-address is the last register pushed onto the stack, thus the last element.

    Note: If you have very little stack space available, then it might be helpful to save a few bytes of stack-space by adding __attribute__((naked)) in front of void main(); -but only for main or entry(), because those subroutines should never return.

    When a subroutine never returns, there's no reason for it to save the registers on the stack.

Reply
  • Does your main() end in an infinite loop ?

    -If not, it should; becaues on a microcontroller, main() is not supposed to return.

    I'm only asking in case your for-loop is placed inside main; if it's outside main, then a stack overflow of a single element will erase the return-address, if the array is the first (or only) variable on the stack.

    This is because the return-address is the last register pushed onto the stack, thus the last element.

    Note: If you have very little stack space available, then it might be helpful to save a few bytes of stack-space by adding __attribute__((naked)) in front of void main(); -but only for main or entry(), because those subroutines should never return.

    When a subroutine never returns, there's no reason for it to save the registers on the stack.

Children