Forums

Undefined behaviour(getting reset) of msp430f5324

This question is not answered

Posted by Ars

on Apr 27 2012 23:26 PM

Hello,

I have started using msp430f5324 device for one of my project and i am facing strange behaviour of reset when code crosses certain limits.Even i have put ISR routines to catch the cause.Plz find attached .map files generated .

STACK size : 512 bytes and

compiler : IAR 5.40.3 30 days Evaluation version

Optimization : None

memory model : small

The behaviour corresponds to map file ( File_1 with reset problem) :

· The device gets reset ( power on and off automatically).

I have checked the RESET Pin. It remains HIGH.

· Suspecting software reset(NMI).

· I tried to catch it with SYSNMI and UNMI ISRs. But not able to catch.

· Even I experimented with STACK size : 1024 bytes.

The behaviour corresponds to map file ( File_2 without reset problem) :

· I have commented few functions which are straight forward and those functions don’t deal with device Hardware registers too.

· The device is found to be working normally.

· Even keeping those function working, if I comment some other functions then too the device works.

7142.File_1_With Reset Problem.txt

0042.File_2Without Problem.txt

what could be wrong ? what would be the debugging & precaution points.Your valuable comments will be helpful.

Thanks & regards,

Ars

All Replies

Posted by TonyKao

on Apr 27 2012 23:42 PM

Genius3770 points

Hi Ars,

I noticed that your code size is ~44kb, which means you need to use the 20-bit CPUX extensions to access the additional flash. Try setting the "data model" and "code model" to "large".

Tony

Posted by Ars

on Apr 28 2012 06:09 AM

Prodigy190 points

Hello,

I have selected the option data model to “large” .But didn’t find anything called “code model’ selection. But problem remains same.

Posted by Jeff Tenney

on Apr 28 2012 10:53 AM

Guru10795 points

Hello Ars,

Two separate questions for you.

Do you have any assembly language in your project?

Can you have the compiler generate a listing with assembly mnemonics included for one of your source code files. Like this:

Project Options -> C/C++ Compiler -> List -> Output List File (Yes) -> Assembler mnemonics (Yes)

Review the listing file (*.lst) generated by the compiler and see if function calls are made with "CALLA" or "CALL" and see if functions end with "RETA" or "RET". If you have the project configured correctly, you will see CALLA / RETA.

Jeff

Posted by Ars

on Apr 30 2012 03:51 AM

Prodigy190 points

Hello jeff,

thanks for suggestions.I have done this.And functions are being called thru' "CALLA" and end with "RETA"

And i don't have any assembly file include in my project.

thanks

Posted by TonyKao

on Apr 30 2012 13:00 PM

Genius3770 points

Hi Ars,

After you have changed the data model and recompiled, does it still say this in the linker map?

__data_model = small

Also, try enabling "20-bit context save on interrupt" in Compiler->Code.

Tony

Posted by Jeff Tenney

on May 01 2012 00:58 AM

Guru10795 points

Hi again Ars,

A few more ideas for you:

The 30-day evaluation version may not actually be fully functional.
Do you use function pointers in your code? If so, how do you declare them? More generally speaking, are you reviewing all the IAR "remarks" and "warnings" from your build process?
After a reset you can read the SYSRSTIV register to determine the highest-priority cause of the most-recent reset. After you read it, be sure to write to it to clear all other causes of the most-recent reset(s). That way when the next reset comes, you'll see what really caused it. Seeing the detailed cause of the reset could be a valuable clue.

Jeff