[Skabana159]

Okay, here is what our team decided about ifi_initialization does, and please anyone correct me if anything appears incorrect, because we were really just guessing.
We were under the impression that C will always start running at main(), though according to the comments, main() is called in ifi_startup.c . What we figured happened was that it DID start with main.c, when to ifi_initialization, which through it's course undefined UNCHANGABLE_DEFINITION_WHATEVER or whatever it was called, then called ifi_startup . ifi_startup did it's thing, and called main() again, which now skips ifi_init because #ifdef UNCHANGALBLE_BLAH_BLAH was false, and it then goes on with it's business.

Is this correct?

We also figured that the only reason IFI would give us a preassembled library is that it does things internally between the processors in the EDU RC, which are things we could really not change, so therefore you really do not need to know what ifi_initialization does. It would be nice, however, to know what exact flow the program follows, rather than guessing like we did.