Article update: Enabling External PSRAM for Zephyr Applications on ESP32 SoCs #434
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sylvioalves
approved these changes
Mar 11, 2025
raffarost
reviewed
Mar 12, 2025
| in | ||
| ## Placing Task Stack in PSRAM | ||
|
|
||
| Another way to to take advantage of PSRAM is by placing Zephyr's task stacks in the `.ext_ram.bss` section via `Z_KERNEL_STACK_DEFINE_IN()` with its trhird parameter `lsect` being `__attribute__((section(".ext_ram.bss")))`. |
raffarost
reviewed
Mar 12, 2025
| $ west espressif monitor | ||
| ``` | ||
|
|
||
| Here is the log emmited by your board: |
wmrsouza
force-pushed
the
update/zephyr_how_to_use_psram
branch
from
d83d5e3 to
f5eafba
Compare
raffarost
reviewed
Mar 13, 2025
| in | ||
| ## Placing Task Stack in PSRAM | ||
|
|
||
| Another way to to take advantage of PSRAM is by placing Zephyr's task stacks in the `.ext_ram.bss` section via `Z_KERNEL_STACK_DEFINE_IN()` with its thrird parameter `lsect` being `__attribute__((section(".ext_ram.bss")))`. |
Contributor
There was a problem hiding this comment.
I think there's still an extra "r":
thrird -> third
raffarost
reviewed
Mar 13, 2025
|
|
||
| Another way to to take advantage of PSRAM is by placing Zephyr's task stacks in the `.ext_ram.bss` section via `Z_KERNEL_STACK_DEFINE_IN()` with its thrird parameter `lsect` being `__attribute__((section(".ext_ram.bss")))`. | ||
|
|
||
| >__Note:__ Be careful before deciding to put your task stacks in PSRAM: When flash cache is disabled (for example, if the flash is being written to), the external RAM also becomes inaccessible. Any read operations from or write operations to it will lead to an illegal cache access exception. You can find more restrictions regarding to the use of external RAM use [here](https://docs.espressif.com/projects/esp-idf/en/stable/esp32s3/api-guides/external-ram.html#restrictions) |
Contributor
There was a problem hiding this comment.
regarding the use (remove "to") and the last use (after), RAM (for redundancy):
"You can find more restrictions regarding the use of external RAM [here]"
This work comes to update necessary details to use PSRAM with more recent Zephyr versions. It also updates the log results to be consistent with those observed when running the samples with more recent Zephyr versions. This work also adds a session explaining how to place Zephyr's task stacks in external RAM and the associated risks. Signed-off-by: Marcio Ribeiro <[email protected]>
wmrsouza
force-pushed
the
update/zephyr_how_to_use_psram
branch
from
f5eafba to
f8cb8d6
Compare
Member
|
Hi @wmrsouza, thanks for this update. Can we merge? |
Contributor
Author
Yes, we can |
pedrominatel
added
the
GitLab-Sync-Merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR comes to update necesary details to use PSRAM with more recent Zephyr versions. It also updates the log results to be consistent with those observed when running the samples with more recent Zephyr versions.
This work also adds a session explaining how to place Zephyr's task stacks in external RAM and the associated risks.