It doesn't override as gpio_config uses the argument to configure the hardware directly; it doesn't retain a link to the struct. After the call, you're free to re-use or free or whatever it, it won't change the settings for the configured GPIOs.

Many thanks.

The read only is an attribute of FreeRtos x taskcreate restricted. In it can be allocated 3 memory regions with
As is shown in FreeRtos IDF

Systems that include MPU support can alternatively create an
MPU constrained task using xTaskCreateRestricted().


Not sure how clear I must make this ...

The question about pinned to core restricted is because can be defined the array. Two task use same region one read only for example the other read/write

Is still valid in static handle the array with
vTaskAllocateMPURegions( );?

The ESP-IDF FreeRTOS as running on ESP32 devices does not ...

I.o.w., every task in an IDF application can freely access all memory. Tasks can share any memory in any way they like.

In order to avoid issues with multiple tasks reading+writing the same memory concurrently, you should be making use of the FreeRTOS synchronization primitives like mutexes and ...

I.o.w., every task in an IDF application can freely access all memory. Tasks can share any memory in any way they like.

In order to avoid issues with multiple tasks reading+writing the same memory concurrently, you should be making use of the FreeRTOS synchronization primitives like mutexes and ...

I am learning ADC and in the example shows

//zero-initialize the config structure.
gpio_config_t io_conf = {};
//disable interrupt
io_conf.intr_type = GPIO_INTR_DISABLE;
//set as output mode
io_conf.mode = GPIO_MODE_OUTPUT;
//bit mask of the pins that you want to set,e.g.GPIO18/19
io_conf ...

Many thanks for your answers..I supposed that statically saved only was necessary to save the register or PC program counter and stack pointer because all variables should be static in a memory region and not in registers.
The question about pinned to core restricted is because can be defined the ...

I am reading FreeRtos (IDF) ESP32 documentation.
Some issues I have to clarify the reading.
I understood that IDF ESP32 port use bytes instead of words in memory allocation.
When is dynamically allocated is understood that change does not affect, but as is said this is the lazy memory allocation ...

I am new in this and I want to start to use FreeRtos. I seen that statically memory allocation is done by an array and depth is in bytes and not words. But array is of type StackType_t

Example says:

#define STACK_SIZE 200

...
// Buffer that the task being created will use as its stack. Note ...