Symbols ![]()
loading...
Files ![]()
loading...
esp_execute_shared_stack_function() function
Calls function on user defined shared stack space After returning, the original stack is used again. @warning This function does minimal preparation of the provided piece of memory (\c stack). DO NOT do any of the following in \c function or any of its callees: * Use Thread-local storage * Use the Floating-point unit on ESP32-P4 * Use the AI co-processor on ESP32-P4 * Call vTaskDelete(NULL) (deleting the currently running task) Furthermore, backtraces will be wrong when called from \c function or any of its callees. The limitations are quite sever, so that we might deprecate this function in the future. If you have any use case which can only be implemented using this function, please open an issue on github.
Syntax
void esp_execute_shared_stack_function(SemaphoreHandle_t lock,
void *stack,
size_t stack_size,
shared_stack_function function);
Implemented in ![]()
expression_with_stack.c:45
Notes
if either lock, stack or stack size is invalid, the expression will be called using the current stack.
Related Functions
Found 16 other functions taking a ![]()
QueueDefinition
argument:
Function
Description
Unlock a mutex
Lock a mutex
Install UART driver and set the UART to the default configuration. UART ISR handler will be attached to the same CPU core that this function is running on.
Delete a semaphore
Create a new mutex
Create a hli queue, wrapping a FreeRTOS queue This queue can be used from high level interrupts, but **ONLY ON THE CPU WHERE hli_queue_setup WAS CALLED**. Values sent to this queue are automatically forwarded to "downstream" FreeRTOS queue using a level 3 software interrupt.
Create a customer hli queue, wrapping a FreeRTOS queue This queue can be used from high level interrupts, but **ONLY ON THE CPU WHERE hli_queue_setup WAS CALLED**. Values sent to this queue are automatically forwarded to "downstream" FreeRTOS queue using a level 3 software interrupt.
Create a hli queue, wrapping a FreeRTOS semaphore See notes on hli_queue_create.
Add the ring buffer to a queue set. Notified when data has been written to the ring buffer This function adds the ring buffer to a queue set, thus allowing a task to block on multiple queues/ring buffers. The queue set is notified when the new data becomes available to read on the ring buffer.
Remove the ring buffer from a queue set This function removes a ring buffer from a queue set. The ring buffer must have been previously added to the queue set using xRingbufferAddToQueueSetRead().
Check if the selected queue set member is a particular ring buffer This API checks if queue set member returned from xQueueSelectFromSet() is a particular ring buffer. If so, this indicates the ring buffer has items waiting to be retrieved.