alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2025-11-02 13:45:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc/ulp(esp32c3): Excludes ulp and some RTC features from ESP32C3 doc

Browse Source
This commit is contained in:
KonstantinKondrashov
2021-02-10 00:05:54 +08:00
parent 0bbc721a63
commit 33820657c5
3 changed files with 109 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/en/api-guides/linker-script-generation.rst
View File

@@ -6,8 +6,15 @@ 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. 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.
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 critical code in RAM for performance reasons or to place code in RTC memory for use in a wake stub or the ULP coprocessor.
.. 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.
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,