# When to create a task?

**URL:** <https://forums.freertos.org/t/when-to-create-a-task/23288>\
**Category:** Kernel\
**Created:** [June 17, 2025, 11:10pm UTC](https://forums.freertos.org/t/when-to-create-a-task/23288 "2025-06-17T23:10:51Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jg\_spitfire](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@jg\_spitfire](https://forums.freertos.org/u/jg_spitfire)\
**Post date:** [July 24, 2025, 3:32pm UTC](https://forums.freertos.org/t/when-to-create-a-task/23288/5 "2025-07-24T15:32:06Z")

</div>

Hi,

> [@richard-damon](#):
>
> The two tasks aren’t sharing the same serial port for some reason are they?

correct, each device is using its own serial port

Sorry, I think I have a “terminology issue” as mentioned in this post:

> [@Blocking code advice for a Newbie](https://forums.freertos.org/t/blocking-code-advice-for-a-newbie/11851/3):
>
> Maybe a terminology issue. Blocking can mean it just doesn’t return until the event occurs (ADC conversion result, or whatever). In the RTOS world the meaning of Blocking is extended to mean you don’t use any CPU time while you are waiting. Not using any CPU time means other tasks (threads of execution) can run while you are waiting. Ideally then the system will be event driven so no CPU time is wasted polling and instead all CPU cycles spent have the opportunity to do something useful (whi…

I associated blocking with a function that is in a loop waiting for data and only breaks the loop after get it, thanks

---

_[View the full topic](https://forums.freertos.org/t/when-to-create-a-task/23288)._