TMDSCNCD28388D: SYS/BIOS Compilation error at changing the list of functions called before module startup

Andrii,

In the Getting Startup Guide section 6.5 it says

The Startup module manages the very early startup initialization that occurs before C's main() function is invoked. This initialization typically consists of setting hardware specific registers that control watchdog timers, access to memory, cache settings, clock speeds, etc. In addition to configuration parameters that allow the user to add custom startup functions, this module also provides services that allow modules to automatically add initialization functions to the startup sequence. Configuration files (*.cfg) that configure the Startup module should enable this module as follows: var BIOS = xdc.useModule('xdc.runtime.Startup'); See Section 3.1 for an overview of the startup process, including the sequence in which functions configured for the Startup module are run and an example configuration script excerpt that installs a usersupplied startup function at every possible control point in the startup sequence.

You've already highlighted Section 3.1 the SYSBIOS Startup Sequence.

I'm not sure what drop list you are referring to but any function that is already plugged in to the 'Reset.fxns' or the 'Startup.firstFxns' is because SYSBIOS plugged those in because you need them.  If you have some of your own functions that need to be plugged in, you can do that via your .cfg file.
If you do not, then no other function or functions should be plugged in.  There is no list of available function to be plugged in.

Again, I ask what you are trying to do with Startup.firstFxns?  Ideally, don't touch it.  Whatever is in there is because SYSBIOS thinks you need it and you should not be adding to it unless you know what you are trying to do.  No SYSBIOS kernel functions should be called from there...for examples task, semaphore, clock, Hwi, etc...should never be called because those modules have not been initialized yet.  You might find Boot calls because Boot module needs to happen very early.

In the getting started guide section 3.1, it has an example of how to add your own function (I'll post it for your benefit):
/* get handle to xdc Startup module */
var Startup = xdc.useModule('xdc.runtime.Startup');

/* install a "first function" */
Startup.firstFxns[Startup.firstFxns.length++] = '&myFirst';

Hope that helps

Judah

Andrii,

Like I said, It all depends on what you are trying to do.  Adding a function is easy to do but is it the right thing to do is the real question.

Judah