I would like to store some frequently-used global variables in the highly performant TCM region (0x20000000). There is a section of this allocated for the user stack, but I don't know the bounds. I can estimate them by getting the address of a variable in eventHandler and subtracting 10*-ish* kilobytes.
It should be safe(-ish) to use the low-address portion of the stack for such variables, but I don't know exactly where to place them, especially as these may change from firmware update to firmware update. It would be very helpful if there were a function for returning the bounds of the stack (at least, the lowest address that is dedicated to the stack.)
I don't need an API function to reserve part of this space for memory; I just need to know the bounds and I can do the rest myself.
Note that the high-address part of the stack, where one would traditionally store this kind of long-lifespan stack variable, is out of the question since I don't control main().