CCS/TMS320F28335: startup hangs when Hwi_getStackInfo returns stkInfo->hwiStackBase = NULL

Hello,

I will bring this thread to the attention of the TI-RTOS experts. Note that due to the local holiday, responses may be delayed.

Thanks

ki

Hi David,

Can you attach your .cfg file? Please attach and not copy/paste to keep the thread readable.

Todd

[12/2 Update: Marking as TI Thinks Resolved due to no activity.]

3443.app.cfg Sorry about the delay in response, I just returned from the holiday.

stkInfo->hwiStackBase is set as follows:

    stkInfo->hwiStackBase = (Ptr)(Hwi_module->isrStackBase);

This is how Hwi_module->isrStackBase gets set in ti/sysbios/family/c28/Hwi.xs:

/*
* ROM
* These members of the module state are added for ROM. They are tied to
* their respective symbol name because the symbols will not be defined
* at the time the ROM assembly is made.
*/
if (Build.buildROM == false) {
    if (Program.build.target.$name.match(/elf/)) {
        mod.isrStackSize = $externPtr('__TI_STACK_SIZE');
        mod.isrStackBase = $externPtr("__stack");
    }
   else {
        mod.isrStackSize = $externPtr("_STACK_SIZE");
        mod.isrStackBase = $externPtr("_stack");
    }
}
else {
    /* If building ROM, then __stack and __STACK_SIZE is undefined */
    mod.isrStackBase = null;
    mod.isrStackSize = 0;
}

I can see from your .cfg file that you're not setting Build.buildROM to 'true', so I wouldn't expect the last "else" clause to be taking effect.

Are you building for ELF or COFF?

You say that it sometimes works but you don't know why.  Given the same input files (source code and linker command files) it will build the same way every time, so identifying why it's different sometimes would be key.

Regards,

- Rob

The problem appears to be that a bunch of initialized xcd variables are ending up in an uninitialized external memory segment.

The third function in the list called by xdc_runtime_starup_exec__F is:

ti_sysbios_hal_Hwi_initStack() which is calling Hwi_getStackInfo(), which is accessing ti_sysbios_family_c28_Hwi_Module__state__V.

ti_sysbios_family_c28_Hwi_Module__state__V is initialized in the source file app_p28FP.c, but the map file shows it is located in external .ebss (uninitialized) memory, and at this stage has not been initialized. 

As a semi-cargo-cult experiment, I tried setting the linker file with the following entry for the relevant external section (containing ti_sysbios_family_c28_Hwi_Module__state__V ) :

ZONE7DATA : LOAD = FLASHF PAGE = 0,
RUN = ZONE7B PAGE = 1,
LOAD_START(extLoadStart),
//LOAD_SIZE(extLoadSize),
LOAD_END(extLoadEnd),
RUN_START(extRunStart)

and adding the line :

memcpy(&extRunStart, &extLoadStart, &extLoadEnd - &extLoadStart); 

in knl_to_ram() (the first function in the list called by xdc_runtime_starup_exec__F).

But CCS studio ended up complaining this was an UNINITIALIZED segment and the extLoadStart... variables weren't defined.

How do I initialize the app_p28FP.o28FP external .ebss variables?