MSP432P401R: program will not fit into available memory, or the section contains a call site that requires a trampoline that can't be generated for this section.

Keshav Aggarwal

Part Number: MSP432P401R

Hello There,

I've written my OTA application. Getting below error while building the project.

<a href="file:/C:/ti/ccs1010/ccs/tools/compiler/dmed/HTML/10099.html">#10099-D</a> program will not fit into available memory, or the section contains a call site that requires a trampoline that can't be generated for this section. placement with alignment fails for section ".resetVecs" size 0x3c, overlaps with ".TI.bound:flashBuf0", size 0x3000 (page 0).

1. Linker File

--retain=interruptVectors

--stack_size=1024   /* C stack is also used for ISR stack */

HEAPSIZE = 0x8000;  /* Size of heap buffer used by HeapMem */

MEMORY
{
    MAIN       (RX) : origin = 0x00008000, length = 0x00040000
    INFO       (RX) : origin = 0x00200000, length = 0x00004000
    ALIAS
    {
    SRAM_CODE  (RWX): origin = 0x01000000
    SRAM_DATA  (RW) : origin = 0x20000000
    } length = 0x00010000
}

/* Section allocation in memory */

SECTIONS
{
    .text   :   > MAIN
    .TI.ramfunc : {} load=MAIN, run=SRAM_CODE, table(BINIT)
    .const  :   > MAIN
    .cinit  :   > MAIN
    .pinit  :   > MAIN
    .init_array : > MAIN

    .data   :   > SRAM_DATA
    .bss    :   > SRAM_DATA
    .sysmem :   > SRAM_DATA

    /* Heap buffer used by HeapMem */
    .priheap   : {
        __primary_heap_start__ = .;
        . += HEAPSIZE;
        __primary_heap_end__ = .;
    } > SRAM_DATA align 8

    .stack  :   > SRAM_DATA (HIGH)
}

/* Symbolic definition of the WDTCTL register for RTS */
WDTCTL_SYM = 0x4000480C;

2. TIRTOS build configs.

/* ================ Reset configuration ================ */
var Reset = xdc.useModule("xdc.runtime.Reset");
/*
 * This function is used when a boot loader is used
 */
Reset.fxns[Reset.fxns.length++] = "&otaResetFunction";

/* ================ Vector Table re-location ================ */
var m3Hwi = xdc.useModule('ti.sysbios.family.arm.m3.Hwi');
m3Hwi.resetVectorAddress = 0x8000; /* App base */

3. otaResetFunction defined in main

#if defined(__TI_COMPILER_VERSION__) || defined(__GNUC__)
extern uint32_t ti_sysbios_family_arm_m3_Hwi_resetVectors;
int otaResetFunction(void)
#elif defined(__IAR_SYSTEMS_ICC__)
extern uint32_t __intvec_start__;
__interwork int __low_level_init(void)
#endif
{
    /* Use Application the interrupt vector */
#if defined(__TI_COMPILER_VERSION__) || defined(__GNUC__)
    SCB->VTOR = (uint32_t) &ti_sysbios_family_arm_m3_Hwi_resetVectors;
#elif defined(__IAR_SYSTEMS_ICC__)
    SCB->VTOR = (uint32_t) &__intvec_start__;
#endif
    return(1);
}

It builds fine when reset and vector configuration from tirtos builds config is removed and keeping the starting main address to 0x00000000 from 0x00008000.

Any help would be highly appreciated.

Regards,

Keshav Aggarwal

over 3 years ago

0 Xiaodong LI over 3 years ago

TI__Mastermind 20025 points

Hi Keshav, Thanks for your post! we will look in the detailed and reply to you later!

0 Lixin Chen1 over 3 years ago

TI__Expert 7015 points

Hi, Keshav,

Why to assign the resetVectorAddress to 0x8000? Reset vector address is fixed. You can input the value to the reset vector address, and the code will jump to the assigned address for execution.

Thanks,

Lixin

0 Keshav Aggarwal over 3 years ago in reply to Lixin Chen1

Expert 1730 points

Hello Lixin,

Actually I'm following Cloud OTA example in Simplelink Wi-Fi plugin for MSP432. There I had checked the reset vector address of the main application is set 0x8000.

Although, My custom bootloader lies from 0x00000000 while main application lies from 0x00008000.

Regards,

Keshav Aggarwal

0 Lixin Chen1 over 3 years ago in reply to Keshav Aggarwal

TI__Expert 7015 points

Hi, Keshav,

Are you referring to this Cloud OTA example in Simplelink Wi-Fi plugin for MSP432: https://dev.ti.com/tirex/explore/node?node=ABcd3tIkTEyB-4cx9ZIVxA__s6qGmnm__LATEST

In the document, application code should be loaded from 0x00000000. 0x8000 is APP software start address (APP_SW_START_ADDRESS). We can find the description in the link:

"When compiling a firmware image to be included in an OTA firmware update package, it is important to not include the bootloader in the generated binary image. The absolute address of where to program the firmware image is specified by the APP_SW_START_ADDRESS define in the ota_extended.h file included in the OTA code examples"

The concern is how to define the APP software start address.

m3Hwi.resetVectorAddress = 0x8000; /* App base */

I am not familiar with TIRTOS. I will let the TI-RTOS experts comment in regards to this.

Thanks,

Lixin

0 Keshav Aggarwal over 3 years ago in reply to Lixin Chen1

Expert 1730 points

Hello Lixin,

Are you referring to this Cloud OTA example in Simplelink Wi-Fi plugin for MSP432: https://dev.ti.com/tirex/explore/node?node=ABcd3tIkTEyB-4cx9ZIVxA__s6qGmnm__LATEST

Yes.

Also, I'm loading my custom bootloader from 0x00000000 and main App from 0x00008000

Regards,

Keshav Aggarwal

0 Alan DeMars over 3 years ago in reply to Keshav Aggarwal

TI__Mastermind 30830 points

The link error indicates that the reset vector table placement is overlapping with the placement of the "flashBuf0" object.

If memory serves me correctly, the "flashBuf0" object is an internal flash memory region managed by the NVS driver which has been explicitly placed somewhere by the board.c file. Apparently, the placement of "flashBuf0" (which is 0x3000 bytes in length) overlaps with address 0x8000.

Can you share the Board.c file you're using with this application?

Alan

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP432P401R: program will not fit into available memory, or the section contains a call site that requires a trampoline that can't be generated for this section.