FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [April 2014 Threads] Limitation using task??Posted by noobdeluxe2000 on April 26, 2014 I am using freeRtos to handle some task..
I've added 4 task where one of the isn't running. (used for debug purpose, but it should be runnning)
when I add another task to my scheduler, crashes freeRtos, and nothing run..
Have i reach some kind of limit or how come doesn't freeRtos run any task on my µc???
Limitation using task??Posted by edwards3 on April 26, 2014 There are lots of possible reasons including a mistake in your code, a linker script error, a configuration error, and so on.
Do you have a debugger attached? If so look at the return values when you call xTaskCreate(), and where the program counter is when it crashes (maybe its just in an assert() call?). Do you have a malloc failed hook defined [http://www.freertos.org/a00016.html]? Do you have a stack overflow hook defined [http://www.freertos.org/Stacks-and-stack-overflow-checking.html]?
Limitation using task??Posted by noobdeluxe2000 on April 26, 2014 Does shared FreeRtos queues need mutex lock or are the included in the queue???
Cause..it doesn't crash when I remove one of the task that shares a queue with,
Limitation using task??Posted by rtel on April 26, 2014 Queues are part of FreeRTOS, and as such are thread safe, so you do not need to use your own mutex lock.
Maybe if you posted the code we could see what was wrong.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|