Replies: 1 comment
-
Hi @DerekSnell , as recommended here is my separate discussion. As you are working with the NXP LPC5500 have you explored allocating stacks in other SRAM regions? BTW I am using an NXP S32K1 that has two SRAM memory addresses. So far this solution works for me but wanted to know if there is a more Zephyrish way of accomplishing this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
By default I think all stacks defined by
K_THREAD_STACK_DEFINE
are allocated in the defaultRAM
section.I see in the final linker and map file that these objects are allocated in
k_stack_area
.Use case: I have some stacks which I would want to allocate in other SRAM regions as I do not have enough space in the main SRAM.
I am already using
zephyr_code_relocate
in my CMakeLists but as the stack is defined with theK_THREAD_STACK_DEFINE
macro these are treated as kernel data objects through the python/cmake scripts of Zephyr.I looked around on the header files so this is what I came up with, not sure if there is much straightforward approach in Zephyr ?
and in my extra linker script I added
Beta Was this translation helpful? Give feedback.
All reactions