2013-10-03 12:20 PM
2013-10-03 12:27 PM
More likely res[] isn't defined with enough scope (ie int res[257];) or that if local the stack is inadequately large.
The selective cut-n-paste seems to have lost some important context, present as a complete subroutine if you can. The size shouldn't be an issue, might depend on tools, check .MAP for size and placement confirmation.2013-11-01 09:44 AM
Clive
Thanks for the reply - in the end we worked around the restriction as we were only using the big data arrays during algorithm testing and we validated the algorithm using an 8000 point array. I guess like you say this may be a configuration issue - however I have had to move on to other areas and this is one issue that will have to leave on the shelf as we have moved on. thanks for time, your great support and apologies for the late reply2013-11-12 12:52 AM
Hi Folks
..just come across a piece of code from ST (in the audio examples) they seem to define a large dataset as:-const uint16_t AUDIO_SAMPLE[] = {0x4952, 0x4646, 0x4f6e, 0xf, 0x4157, 0x4556, 0x6d66, 0x2074, 0x12, 0, 0x1, 0x2, 0xbb80, 0, 0xee00, 0x2, 0x4, 0x10, 0, 0x6166, 0x7463, 0x4, 0, 0xd3cf, 0x3, 0x6164, 0x6174, 0x4f3c, 0xf, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, etc...so this should work (but I've not tested it) CS