• State Accepted Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 24 subscribers
  • Views 3754 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

What will happen if we remove the for(;;); from the main in the freeRTOS kernel??

omkardixi

Actually I read from the Mastering in the FreeRTOS documentation that,

/* If all is well then main() will never reach here as the scheduler will
now be running the tasks. If main() does reach here then it is likely that
there was insufficient heap memory available for the idle task to be created.
Chapter 2 provides more information on heap memory management. */
for( ;; );

what if I removed for( ;; ); from the main? I mean in case if anything happens in the project and if the control goes to that infinite loop then the product will hang forever.

So my question is why we use this?? can we remove it??

  • 0 Arm Employee Badge

    missing the required endless loop I expect that your program terminates within a sys_exit() (or similar) call

  • 0

    That's actually the wrong question.  Where exactly do you expect your program to go after it fell off the end of main()?  And how do you expect that result to be in any way, shape or form better than to be stuck in a well-defined endless loop?

  • 0 in reply to Broeker

    lets say if we have code

    void main(void)
{

}

    at the end contains a return statement although we didn't explicitly put it there ourselves. When main returns the CPU executes the next instruction which is simply a GOTO to go back to the beginning of the code. main() is simply called over and over again. So why we preffer to stuck in while loop (at the end of the main) rather than calling main function again and again.

    Sir please can you elaborate what you are saying. I really want to clear this concept in my mind.

  • 0 in reply to omkardixi
    omkardixi said:
    When main returns the CPU executes the next instruction which is simply a GOTO to go back to the beginning of the code.

    Do you just assume that happens, or did you look it up in some documentation about this tool chain?

  • +1 in reply to Broeker

    I got the answer on the FreeRTOS forum

    What happens when you exit an embedded program is only defined by a particular implementation. Some may restart the program, but many just loop to stall. In any case, your program had a major failure where the system didn’t start up, and retrying is unlikely to change that. Ideally you want it easy to see what happened when debugging, so having the loop right there is helpfull.