When should I use threads within tasks? - FreeRTOS

Question

I'm about to develop an FreeRTOS based embedded system that will run on a ESP32 chip. According to the API Reference I can create tasks and as well as pthreads.

Is there any rule of thumb that tells me if I should implement a functionality as a task or as thread? For example: If I'd like to handle three peripherals paralelly (just simple reading, so: short code, low performace, nearly any memory needed), I should create a new task or a new thread?

'simple' and 'reading' are not often seen in the same sentence when discussing I/O in an RTOS environment. Interrupts, DMA and kenel signaling are usually required to perform I/O in any kind of efficient, RTOS-friendly manner:( — Martin James
– Martin James, Commented Jul 11, 2018 at 15:50

lkanab · Accepted Answer · 2018-11-01 03:20:26Z

3

FreeRTOS have tasks. pthread is suggested as a wrapper to task for portability and compatability with POSIX systems and code.

Anyway, FreeRTOS do not have memory seperation, virtualization and remapping on context switch between tasks, so all it's tasks are what POSIX would call threads.

answered Nov 1, 2018 at 3:20

lkanab

9541 gold badge7 silver badges21 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

When should I use threads within tasks? - FreeRTOS

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related