espressif/esp-idf
1
0
Fork 1
mirror of https://github.com/espressif/esp-idf.git synced 2026-05-04 20:05:25 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: update system API-guides for ESP32-C2

Browse Source
This commit is contained in:
Marius Vikhammer
2022-07-11 17:11:27 +08:00
parent f78d13398e
commit d62421619c
25 changed files with 141 additions and 149 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/api-guides/linker-script-generation.rst
+6 -5
View File
@@ -7,13 +7,14 @@ Overview
There are several :ref:`memory regions<memory-layout>` where code and data can be placed. Code and read-only data are placed by default in flash, writable data in RAM, etc. However, it is sometimes necessary to change these default placements.
.. only:: SOC_ULP_SUPPORTED
For example, it may be necessary to place:
For example, it may be necessary to place critical code in RAM for performance reasons or to place code in RTC memory for use in a wake stub or the ULP coprocessor.
.. list::
.. only:: not SOC_ULP_SUPPORTED
For example, it may be necessary to place critical code in RAM for performance reasons or to place code in RTC memory for use in a wake stub.
* critical code in RAM for performance reasons.
* executable code in IRAM so that it can be ran while cache is disabled.
:SOC_RTC_MEM_SUPPORTED: * code in RTC memory for use in a wake stub or the ULP coprocessor.
:SOC_ULP_SUPPORTED: * code in RTC memory for use by the ULP coprocessor.
With the linker script generation mechanism, it is possible to specify these placements at the component level within ESP-IDF. The component presents information on how it would like to place its symbols, objects or the entire archive. During build, the information presented by the components are collected, parsed and processed; and the placement rules generated is used to link the app.