This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
We configured the ccs project to do unit test (using parasoft).
while generating the test suits and test cases .
/resized-image/__size/1200x426/__key/communityserver-discussions-components-files/908/2273.ERROR.png
bellow is the linker script:-
/* * Copyright (c) 2013, Texas Instruments Incorporated * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * * Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * * Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * * * Neither the name of Texas Instruments Incorporated nor the names of * its contributors may be used to endorse or promote products derived * from this software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; * OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */ /* * ======== DK_TM4C129X.cmd ======== * Define the memory block start/length for the TM4C129XNCZAD */ /* The starting address of the application. Normally the interrupt vectors */ /* must be located at the beginning of the application. */ #define APP_BASE 0x00004000 #define RAM_BASE 0x20000000 #define SDRAM_BASE 0x60100000 MEMORY { FLASH (RX) : origin = APP_BASE, length = 0x000FC000 /* For EVT Board */ SRAM (RWX) : origin = 0x20000000, length = 0x00040000 /* For EDT Board comment above line and uncomment below line */ //SRAM (RWX) : origin = 0x20000000, length = 0x00020000 SDRAM (RW): origin = SDRAM_BASE, length = 0x100000 } /* The following command line options are set as part of the CCS project. */ /* If you are building using the command line, or for some reason want to */ /* define them here, you can uncomment and modify these lines as needed. */ /* If you are using CCS for building, it is probably better to make any such */ /* modifications in your CCS project and leave this file alone. */ /* */ /* --heap_size=0 */ /* --stack_size=256 */ /* --library=rtsv7M4_T_le_eabi.lib */ /* Section allocation in memory */ SECTIONS { .intvecs: > APP_BASE .text : > FLASH .const : > FLASH .cinit : > FLASH .pinit : > FLASH .init_array : > FLASH .vtable : > RAM_BASE .data : > SRAM .bss : > SRAM .sysmem : > SRAM .stack : > SRAM .sdram : > SDRAM .sdram{ // rechargeIcons.obj(.const) // disinfectionIcons.obj(.const) } > SDRAM } __STACK_TOP = __stack + 512;
Hi,
From the linker file perspective, the only thing I see missing er file is the --retain=g_pfnVectors. Other than that I don't notice an issue with the linker file. I think the issue is related to your application as the error complains about the .const needing 0x2c12b bytes while there is only 0x281b8 bytes of flash left in the memory. Your .text (your application) is too big and hence there is no space left for the .const. Please note there is only 1MB flash in the device.