Dear Deouss, in Germany we say "The tone makes the music". So I grab all my politeness and try to explain, what seems so difficult to see for you. First lets look why core without RTOS can make sense. Here is the challenge: 1. Part You get a rising edge at an external pin. You have to set high an ou...

How is it done? void app_main(void) { start RTOS tasks and vOtherFunction(); .... ---------------------------- void vOtherFunction( void ) { TaskHandle_t xHandle = NULL; xHandle = xTaskCreateStaticPinnedToCore( CoopOS, // Function that implements the task. "CoopOS", // Text name for the task. STACK_...

@ deouss That you have never heard from that idea does not mean it is impossible :D I managed to run 8 RTOS Tasks (core 0) an 20 CoopOS tasks (core 1) and let them communicate. CoopOS has a lot of features of an RTOS: Signals, Priorities, non blocking delays etc. The big difference: task switches ar...

Thank you very much. I am not able to write all the stuff to install fast interrupt handlers in assembler. But from the tips and links you posted I found a way to detect pin changes very fast. While core 0 is doing the RTOS tasks I do a brute force loop on core 1 (interrupts disabled) like this: int...

For me a similar problem (core 0 tasks data --> core 1 tasks) had been solved with "volatile" variables
for ONE direction. For both directions or more than 2 tasks writing use a semaphore.

(Please excuse my english, I am german) I want to use one core with RTOS and the other core with my own cooperative OS (CoopOS), which I use since the days of Arduino. Yes, there are some reasons to do so - it is much faster in special circumstances.. It works and I am nearly happy. For the second c...