Alexey Gerenkov 55f1a63faf esp32: Adds functionality for application tracing over JTAG 9 лет назад
..
include 45581dbaca freertos: Delay context switch from queue/task APIs until exiting critical section 8 лет назад
test 0b57054ed3 freertos tests: Extend preemption test cases to cross-core wakeup 8 лет назад
FreeRTOS-openocd.c 4d8ad3c877 Fix int wdt iram, fix some fallout of moving panic stuff to esp32 9 лет назад
Kconfig 01ad387ac8 freertos: Add config parameters to customize FreeRTOS behaviour. 8 лет назад
component.mk 208e83def7 build system: Refactor component.mk to not need component_common.mk 9 лет назад
croutine.c fc53bb6ed5 Add UNTESTED_FUNCTION() call to untested functions, make Kconfig option to enable that to map to assert() 9 лет назад
event_groups.c 20212ee823 freertos: Fix cross-core usage of event groups 9 лет назад
heap_regions.c 93e72649dc Fix memory debugging code 9 лет назад
heap_regions_debug.c 293ad4cd36 Add xPortGetFreeHeapSizeCaps and xPortGetMinimumEverFreeHeapSizeCaps plus everything it entails. Allows querying the available memory for various capabilities. Also: xPortGetFreeHeapSize and xPortGetMinimumEverFreeHeapSize now return the expected value. Bonus: the linked list used in the allocator is now 4 bytes smaller, which should save some memory. 9 лет назад
license.txt bd6ea4393c Initial public version 9 лет назад
list.c bd6ea4393c Initial public version 9 лет назад
port.c 55f1a63faf esp32: Adds functionality for application tracing over JTAG 8 лет назад
portasm.S 0e39b77d4e Fix finding location of ISR stack space for CPU1 8 лет назад
queue.c 45581dbaca freertos: Delay context switch from queue/task APIs until exiting critical section 8 лет назад
readme_smp.txt 86d8f63005 Per-CPU interrupt handlers and args 9 лет назад
readme_xtensa.txt bd6ea4393c Initial public version 9 лет назад
ringbuf.c 6a8a9a0272 bugfix: ring buffer, fix api xRingbufferReceiveUpToFromISR 9 лет назад
stdint.readme bd6ea4393c Initial public version 9 лет назад
tasks.c 45581dbaca freertos: Delay context switch from queue/task APIs until exiting critical section 8 лет назад
timers.c 925fbb587e Add static initializers for muxes, add mutex init to vPortCPUAcquireMutex 9 лет назад
xtensa_context.S bd6ea4393c Initial public version 9 лет назад
xtensa_init.c bd6ea4393c Initial public version 9 лет назад
xtensa_intr.c 655fd2986a Add interrupt allocation scheme / interrupt sharing. Also modifies drivers and examples. Also allows interrupts 9 лет назад
xtensa_intr_asm.S 78161a1fe3 Replace non-multicore-aware rom funcs with multicore-aware funcs, ESP_LOG->ESP_EARLY_LOG fix, reserve ints used in wireless libs. Fixes WiFi crashing 9 лет назад
xtensa_overlay_os_hook.c bd6ea4393c Initial public version 9 лет назад
xtensa_vectors.S 0b79d07d34 add detection of invalid cache access 8 лет назад

readme_smp.txt

This version of FreeRTOS has been modified by Espressif to be SMP-aware. The
API is similar to the original FreeRTOS API, with the following changes:

- The xTaskCreate() function now creates tasks that will run on the first
core only, for backwards compatibility. To schedule tasks on another core,
use xTaskCreatePinnedToCore(), which will accept a core ID as the last
argument. If this is the constant tskNO_AFFINITY, the task will be dynamically
scheduled on whichever core has time.

- vTaskSuspendAll/vTaskResumeAll in non-SMP FreeRTOS will suspend the scheduler
so no other tasks than the current one will run. In this SMP version, it will
only suspend the scheduler ON THE CURRENT CORE. That is, tasks scheduled to
run on the other core(s) or without a specific CPU affinity, will still be
able to run.

- Enabling and disabling interrupts will only affect the current core.
Disabling the interrupts will not disallow other tasks to run as
it would on a single-core system: the other core still will keep on
executing all it's own. Use a mux, queue or semaphore to protect your
structures instead.

- This FreeRTOS version has the task local storage backported from the 8.2.x
versions. It, however, has an addition: you can also set a callback when you
set the pointer. This callback will be called by the idle task, with the
pointer as an argument, when the thread is destroyed. This depends on the idle
task getting CPU time; when a thread is hogging the CPU without yielding,
the idle thread won't be called and the delete callback won't be called either.