Memory Overwritten

Dustin Lane

Other Parts Discussed in Thread: MSP430F2132

I'm using the MSP430F2132 and have been coming across a consistent issue. The point where my code gets stuck is soon after a return from a timer interrupt I copy the data from one unsigned array[16] to another.

for(i = 0;i<16;i++)
{
adctosd[i] = adc[i]; //copy buffer
adc[i] = 0; //clear buffer

}

Not always the first time, but eventually the data that is being copied in this transfer, some of it gets written outside of the memory allocated for adctosd and into the memory addresses just after it. Thus, those variables that are getting trashed with this overwritten data causes my code to crash.

My question is, is this a common issue with stack overflow? Or is it something else? I've set my stack to a relatively high point (as high as memory will allow), so it seems like that might not be the issue.

Any help would be greatly appreciated!

Dustin

over 15 years ago

0 AartiG over 15 years ago

TI__Guru**** 173310 points

The problem could be due to stack overflow but that may not necessarily be the only reason for such symptoms. The suggestions made in your other post of using the "Break on Stack overflow" feature in CCS4 should help determine if the stack is overflowing: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/88600.aspx

0 Dustin Lane over 15 years ago in reply to AartiG

Intellectual 610 points

Thanks for your help Aarti,

I followed the advice laid out in those articles you referred me to, however, after setting the appropriate stack overflow breakpoint, the same problem still occurs with out setting off the breakpoint. So, it appears a stack overflow is not the issue.

Do you have any thoughts on what else it maybe? I can provide any info you may need.

Thanks!

0 AartiG over 15 years ago in reply to Dustin Lane

TI__Guru**** 173310 points

Have you been able to step through your code to debug further where exactly the stack variables are getting over-written? The advanced debug features such as data breakpoints as described in http://www.ti.com/lit/slaa393 might also be helpful in narrowing down the location of the problem. As another reference, this post contains some good tips on debugging such issues.

0 Dustin Lane over 15 years ago in reply to AartiG

Intellectual 610 points

Yes, I have narrowed down where in the stack the variables are getting overwritten, it's pretty much the same place every time. The post you provided has some good information, I'll continue to look into that and let you know if it solves anything. Thanks for your help, if you think of any other possibilities, feel free to pass them along.

Code Composer Studio™︎

Code Composer Studio forum

Memory Overwritten