esp-idf/docs/api-reference/system/index.rst

System API
**********

.. toctree::
   :maxdepth: 1

   FreeRTOS <freertos>
   FreeRTOS Hooks <hooks>
   Heap Memory Allocation <mem_alloc>
   Heap Memory Debugging <heap_debug>
   Interrupt Allocation <intr_alloc>
   Watchdogs <wdts>
   Inter-Processor Call <ipc>
   High Resolution Timer <esp_timer>
   Logging <log>
   Application Level Tracing <app_trace>
   Power Management <power_management>
   Sleep Modes <sleep_modes>
   Base MAC address <base_mac_address>
   Over The Air Updates (OTA) <ota>


Example code for this API section is provided in :example:`system` directory of ESP-IDF examples.
Moved api documentation to new folders / categories 2017-01-16 23:08:35 +01:00			`System API`
			`**********`

			`.. toctree::`
			`:maxdepth: 1`

docs: add FreeRTOS API docs - Use `code` tags instead of a mix of `<pre></pre>` and `@verbatim .. @endverbatim` - Remove manually added function prototypes from comment blocks - Remove of grouping (`\defgroup`) — some extra work is needed to make groups compatible with the way we auto-generate API reference from Doxygen XML files. It's pretty easy to add the grouping directives back if/when we implement support for Doxygen groups in the later stages of documentation build process. - Hide private APIs under `@cond .. @endcond` - Convert some comments into Doxygen-compatible ones - Fix various documentation issues: missing documentation for some parameters, mismatch between parameter names in comment block and in function prototype. - Add doxygen comments for functions which didn't have them (thread local storage). - Add [out] param tags where necessary - Redefine `xTaskCreate` and `xTaskCreateStatic` as inline functions instead of macros. 2017-12-01 12:50:45 +08:00			`FreeRTOS <freertos>`
			`FreeRTOS Hooks <hooks>`
doc: Add docs for heap trace & poisoning 2017-07-19 09:07:17 +10:00			`Heap Memory Allocation <mem_alloc>`
			`Heap Memory Debugging <heap_debug>`
Moved api documentation to new folders / categories 2017-01-16 23:08:35 +01:00			`Interrupt Allocation <intr_alloc>`
			`Watchdogs <wdts>`
docs/ipc documentation This commit updates doxygen comments in the IPC header files and adds an rst docs page. 2017-11-22 15:16:29 +08:00			`Inter-Processor Call <ipc>`
esp_timer: add documentation, expose profiling option in Kconfig 2017-11-24 18:51:37 +08:00			`High Resolution Timer <esp_timer>`
Moved api documentation to new folders / categories 2017-01-16 23:08:35 +01:00			`Logging <log>`
esp32: SEGGER SystemView Tracing Support Implements support for system level traces compatible with SEGGER SystemView tool on top of ESP32 application tracing module. That kind of traces can help to analyse program's behaviour. SystemView can show timeline of tasks/ISRs execution, context switches, statistics related to the CPUs' load distribution etc. Also this commit adds useful feature to ESP32 application tracing module: - Trace data buffering is implemented to handle temporary peaks of events load 2017-03-22 06:07:37 +03:00			`Application Level Tracing <app_trace>`
docs: add FreeRTOS API docs - Use `code` tags instead of a mix of `<pre></pre>` and `@verbatim .. @endverbatim` - Remove manually added function prototypes from comment blocks - Remove of grouping (`\defgroup`) — some extra work is needed to make groups compatible with the way we auto-generate API reference from Doxygen XML files. It's pretty easy to add the grouping directives back if/when we implement support for Doxygen groups in the later stages of documentation build process. - Hide private APIs under `@cond .. @endcond` - Convert some comments into Doxygen-compatible ones - Fix various documentation issues: missing documentation for some parameters, mismatch between parameter names in comment block and in function prototype. - Add doxygen comments for functions which didn't have them (thread local storage). - Add [out] param tags where necessary - Redefine `xTaskCreate` and `xTaskCreateStatic` as inline functions instead of macros. 2017-12-01 12:50:45 +08:00			`Power Management <power_management>`
			`Sleep Modes <sleep_modes>`
			`Base MAC address <base_mac_address>`
			`Over The Air Updates (OTA) <ota>`
Moved api documentation to new folders / categories 2017-01-16 23:08:35 +01:00
Added links from api category TOC to example category folders Typo fix in bluetooth README.md 2017-01-18 21:04:11 +01:00
docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests. 2017-01-19 16:16:06 +08:00			Example code for this API section is provided in :example:`system` directory of ESP-IDF examples.