MSP430FR2676: How to set a proper stack size

Cherry Zhou

Mastermind 22235 points

Part Number: MSP430FR2676

Hi team,

The above figure shows a stack space usage for customer application engineering, in the above figure:

1. The main function main occupies 126 bytes of space;

2. ADC_ISR is an ADC interrupt that requires 28 bytes of space to execute;

3. __TI_auto_init_noinit_nopinit_hold_wdt occupies 20 bytes;

4. __TI_decompress_none occupies 20 bytes;

5. __TI_decompress_lzss occupies 32 bytes; Abort occupies 4 bytes;

Where ADC_ISR may trigger an interrupt to main at any time, so the minimum stack space should be greater than 126+28=154 bytes.

So the customer has 2 questions may need your help:

1. What do the __TI_auto_init_noinit_nopinion_hold_wdt, __TI_decompress_none, __TI_decompress_lzss, abort respectively do? When will they run? Is it necessary to calculate them to calculate the minimum stack usage?

2. If 2 interrupts are enabled, is the minimum stack plus the sum of 2 interrupt functions, or is it the larger of 2 interrupt functions?

Could you help check this case? Thanks.

Best Regards,

Cherry

over 3 years ago

0 David Schultz over 3 years ago

Guru 24625 points

The init routines run before the call to main so should not add to the required stack size.

Interrupt service routines start with interrupts disabled so there is zero chance of nested interrupts unless you explicitly enable interrupts within an ISR. So the answer to (2) depends on your code.

0 Cherry Zhou over 3 years ago in reply to David Schultz

TI__Mastermind 22235 points

Hi David,

Thanks for your support.

Cherry Zhou said:
__TI_decompress_none, __TI_decompress_lzss, abort

Are these 3 also call at init routine?

Thanks and Best Regards,

Cherry

0 Chester Gillon over 3 years ago in reply to Cherry Zhou

Guru 92251 points

Cherry Zhou said:
Are these 3 also call at init routine?

__TI_decompress_none and __TI_decompress_lzss are called at initialisation by the compiler run-time library start up code to initialise global variables.

abort handles abnormal program termination, and just spins in a loop it if is called. abort can be called if either:

The main() function returns. If main() returns exit() is called when then calls abort(). In an embedded application main() is not expected to return, although a unit test program might.
At runtime exit() or abort() is called, either directly by the application or if an an error occurs in a run-time library function called by the application.

0 Eason Zhou over 3 years ago in reply to Chester Gillon

TI__Mastermind 39775 points

Hi Chester,

Thank you for answering the questions!

Eason

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP430FR2676: How to set a proper stack size