More Hooks for Schedulers and RTOS's

[Michael2MacDonald]

Especially for higher powered arm microcontrollers, I would like to see hooks that allow more control over the underlying code that allow schedulers and task management, on single and multicore microcontrollers, to become easier to implement without having to change the underlying Arduino code.

Maybe even other forms of built in suport for these types of task and program management through a unified Arduino scheduler or functions.

[pnndra]

@Michael2MacDonald actually we are proposing an approach to multitasking that should prevent exposing OS specific API... please have a look at this: https://github.com/arduino-libraries/Arduino_Threads

[Michael2MacDonald]

Thanks! I just saw that last night after I posted this but it was really late for me so I went to bed.

It is possible that other people may have a use (other than scheduling) for hooks but I agree that adding multitasking support directly is a much better idea.

[pnndra]

Thank you for clarifying it. the whole intent to open a discussion is to hear from our user base which are their requirements to provide the best possible solution. adding multitasking functions in arduino language such as bare threads, mutexes, semaphores, queues, etc is something we're reluctant to do because it would require users to be aware of the pitfalls of multitasking, reentrancy etc and since Arduino is synonym of ease of use i don't think we shall go in that direction.
as opposed to this we've been trying to create an infrastructure that lets you just run multiple sketches in parallel, almost unmodified from traditional ones, in a way that you don't have any issue with concurrency and reentrancy.

[dsyleixa]

std::thread (freeRTOS-based) is already available since many years for the ESP32-Arduino API and it works like a charm, even for beginners, no problem at all.
it only should come with even more extensive examples.

[per1234]

@dsyleixa that is off topic for this discussion. You have already repeatedly expressed your opinion about std::thread. Message received. You don't need to post it over and over again.

Also, please stop posting the same reply repeatedly.

We welcome your input, but please be more respectful in your participation.

[dsyleixa]

it have been 2 different answeres to 2 different posts which required the same information to be given.
OTOH, in both cases the topic was scheduling which is clearly exploited by the underlying freeRTOS code (as to ESP32-arduino and ESP32-IDF)
so please stopp annoying me with your snooty attitude.