One, find one of those memory map charts -- per core stack space is limited. Big data structures should be in the heap area. But I don't think you have a stack problem.
Second, if you don't use pointers for structs, I think there are cases in C where the struct is copied for example when C sets up a call frame and the struct is a parameter. It's worse in C++, an innocent-looking assignment can lead to all sorts of things. So certain styles of coding doing data abstraction can be banana skins...
If a smaller struct array size glitches maybe it's not due to the location of the thing. Maybe C is using something different to copy the struct array based on block size. But we don't know how the thing is coded...
Without seeing your code, or parts of your code, and what you are doing to the struct arrays, it's impossible to say anything definitive.
[Edit] I assume the audio output is using DMA or else that will be a problem too.
Second, if you don't use pointers for structs, I think there are cases in C where the struct is copied for example when C sets up a call frame and the struct is a parameter. It's worse in C++, an innocent-looking assignment can lead to all sorts of things. So certain styles of coding doing data abstraction can be banana skins...
If a smaller struct array size glitches maybe it's not due to the location of the thing. Maybe C is using something different to copy the struct array based on block size. But we don't know how the thing is coded...
Without seeing your code, or parts of your code, and what you are doing to the struct arrays, it's impossible to say anything definitive.
[Edit] I assume the audio output is using DMA or else that will be a problem too.
Statistics: Posted by katak255 — Tue Dec 31, 2024 12:41 am