Compiler/MSP430FR2433: Boot Hook Functions for System Pre-Initialization

My copy of the CC User Guide (SLAU132S) Sec 6.9.1 says "_system_post_cinit(): [...]This function should not return a value." If you don't have any constructors, putting something here is probably not much different from putting it at the top of main.

_system_pre_init has value if you have large globals that take so long to initialize that the WDT goes off. There have also been a couple of different people here recently who were using it for SRAM research.

While section 6.9.1 mentions _c_int00, it doesn't cite it as a Boot Hook Function. This is the function (pointer) that is put into the reset vector. In practice, CCS chooses one of a few different "_c_int00"-s to use, depending on CCS options. Unless you're planning to craft your executable image by hand, you probably shouldn't mess with this. If you want to see the source, the simplest way is to do a "Hard Reset" in the debugger, which will take you right there.

Bruce:

Why are you working during Saturday evening? You should be outside having a cocktail with friends and neighbors.

You mostly, but not completely, confirmed how I was perceiving these three functions, especially about _c_int00. However, I want to make sure I've got this right.

As for the _system_post_cinit() function, you don't think it returns any value. It's sounds like you are not one hundred percent sure about whether it returns a value or not. This might clarify the topic, or make it more complicated. Just now, I decided to look into the boot_hooks.h file, and it declares both init() functions as being void of returns and are both void of taking any parameters, but in reality,  _system_pre_init() does return a 0 or 1. What do you think? What's going on here?

As for the _c_int00 function, I saw that the boot.c file appends that name in several different ways, depending on...well, I've read that file over and over again, I can't comprehend it. It appears to depend on something which is complicated. That all doesn't seem to matter anyways, since _c_int00 is something that we cannot use like the first two boot hook functions, and that its real purpose is act as vector. Section 6.9.1 should probably be rewritten to reflect that.

-Thomas

P.S. Do you know where the MAP file is located? I've forgotten.

Thanks for pointing out that the return type for _system_pre_init(void) is an integer. I over looked that. You've answered all my questions.

Just as a reference to everybody, a code example of _system_pre_init(void) can be found in section 6.2, "Program Development," in the Code Composer Studio™ IDE v8.x for MSP430™ MCUs" (SLAU157). Here it is for those who might be interested.

int _system_pre_init(void)
{
/* Insert your low-level initializations here */
WDTCTL = WDTPW + WDTHOLD; // Stop Watchdog timer
/*==================================*/
/* Choose if segment initialization */
/* should be done or not. */
/* Return: 0 to omit initialization */
/* 1 to run initialization */
/*==================================*/
return (1);
}