RTX stack size

Did you real what i wrote?
Have you looked at the actual API?
If you use user-supplied stacks when you start a thread, then you can see the stack as just any buffer. So if you know that the thread has ended, then you can start a new thread and supply the exact same stack.

And if you have multiple threads that needs same-size stacks, then RTX have memory functions supporting allocation/release of these memory blocks similar to how you multiple times assigns data to specific indices of an array.

Start experimenting with the API instead of just asking questions. We just can't answer your questions without you understanding the API. And if you understand the API, then the reasons for most of your questions will go a way.

Programming is about combining LEGO pieces in different patterns. No one can describe all possible patterns which means that developers needs to be creative. The RTX manual do describe the individual LEGO pieces you have available.

Did you real what i wrote?
Have you looked at the actual API?
If you use user-supplied stacks when you start a thread, then you can see the stack as just any buffer. So if you know that the thread has ended, then you can start a new thread and supply the exact same stack.

And if you have multiple threads that needs same-size stacks, then RTX have memory functions supporting allocation/release of these memory blocks similar to how you multiple times assigns data to specific indices of an array.

Start experimenting with the API instead of just asking questions. We just can't answer your questions without you understanding the API. And if you understand the API, then the reasons for most of your questions will go a way.

Programming is about combining LEGO pieces in different patterns. No one can describe all possible patterns which means that developers needs to be creative. The RTX manual do describe the individual LEGO pieces you have available.

Thanks for your patience.
However my questions don't touch stack space in general, as you answered.
I'm only concerned about initial stack defined in startup.s:
Stack_Size EQU 0x0000100

AREA STACK, NOINIT, READWRITE, ALIGN=3
Stack_Mem SPACE Stack_Size

Where is Stack_Mem located?
Could You please point me a reference to the manual, where API explains
how to get the address (from C/C++ perspective) to assembly allocated initial stack ( in startup.s)?
All other questions which I've asked are side effects of this main issue.
donald

I haven't seen any feedback to my comment earlier that the normal way is to make the initial stack very small, and perform the majority of initialization within an RTX thread. Do you really need to reclaim these 128 bytes?

Well I have 8kB RAM part and my code need app. 800 bytes more.
I'm looking anywhere for savings, but this seems to be painless.
However looks impossible.
donald

Make your own symbol in the startup file, representing the C variable name you want to use to reclaim stack space.