• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 1406 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TI hercules launchpad programming error; unresolved symbols plus error in sys_link.cmd

Anurag Meena1
Prodigy 65 points
Other Parts Discussed in Thread: HALCOGEN

I am programming the TI hercules launchpad spi feature and am unable to overcome the following highlighted errors:

Below is the content from output window

'Invoking: ARM Linker'
"C:/ti/ccsv5/tools/compiler/arm_5.1.1/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me -g --diag_warning=225 --display_error_number --diag_wrap=off --enum_type=packed -z -m"freya.map" --heap_size=0x800 --stack_size=0x800 -i"C:/ti/ccsv5/tools/compiler/arm_5.1.1/lib" -i"C:/ti/ccsv5/tools/compiler/arm_5.1.1/include" --reread_libs --warn_sections --display_error_number --diag_wrap=off --xml_link_info="freya_linkInfo.xml" --rom_model -o "freya.out" "./source/system.obj" "./source/sys_vim.obj" "./source/sys_startup.obj" "./source/sys_selftest.obj" "./source/sys_pmu.obj" "./source/sys_phantom.obj" "./source/sys_pcr.obj" "./source/sys_mpu.obj" "./source/sys_intvecs.obj" "./source/sys_core.obj" "./source/sci.obj" "./source/pinmux.obj" "./source/notification.obj" "./source/esm.obj" "./source/dabort.obj" "./main.obj" "../RM42L432FlashLnk.cmd" "../source/sys_link.cmd" -l"libc.a"
<Linking>
"../source/sys_link.cmd", line 24: error #10263: VECTORS memory range has
already been specified
"../source/sys_link.cmd", line 24: error #10264: VECTORS memory range overlaps
existing memory range VECTORS
"../source/sys_link.cmd", line 25: error #10263: FLASH0 memory range has
already been specified
"../source/sys_link.cmd", line 25: error #10264: FLASH0 memory range overlaps
existing memory range FLASH0
"../source/sys_link.cmd", line 26: error #10263: STACKS memory range has
already been specified
"../source/sys_link.cmd", line 26: error #10264: STACKS memory range overlaps
existing memory range STACKS
"../source/sys_link.cmd", line 26: error #10264: STACKS memory range overlaps
existing memory range RAM
"../source/sys_link.cmd", line 27: error #10263: RAM memory range has already
been specified
"../source/sys_link.cmd", line 27: error #10264: RAM memory range overlaps
existing memory range RAM
warning #10366-D: automatic library build: using library "C:\ti\ccsv5\tools\compiler\arm_5.1.1\lib\rtsv7R4_A_le_eabi.lib" for the first time, so it must be built. This may take a few minutes.
0 [main] sh 10180 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
C:/Users/Anurag/AppData/Local/Temp/make13440-1.sh: line 1: 10180 Segmentation fault (core dumped) c:/ti/ccsv5/tools/compiler/arm_51~1.1/bin/armar -qa c:/users/anurag/appdata/local/temp/ti5ed1~1/rtsv7r4_a_le_eabi.lib *.obj
gmake.exe[1]: *** [library] Error 139
>> ERROR: mklib: gmake error during rtsv7R4_A_le_eabi.lib build
warning #10207-D: automatic RTS selection: resolving index library "libc.a" to "C:\ti\ccsv5\tools\compiler\arm_5.1.1\lib\rtsv7R4_A_le_eabi.lib", but "C:\ti\ccsv5\tools\compiler\arm_5.1.1\lib\rtsv7R4_A_le_eabi.lib" was not found

undefined first referenced
symbol in file
--------- ----------------
__TI_auto_init ./source/sys_startup.obj
__TI_decompress_none
__TI_decompress_rle24
__TI_zero_init

>> Compilation failure
__aeabi_d2uiz ./source/sci.obj
__aeabi_ddiv ./source/sci.obj
__aeabi_ui2d ./source/sci.obj
exit ./source/sys_startup.obj

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "freya.out" not built
gmake: *** [freya.out] Error 1

  • 0
    TI__Guru 68930 points

    Hi Anurag [hope I got that right and it's not Meena].

    I think you have two linker command files in your build which is unusual.

    One looks like it came with HalCoGen, I'm not sure where the other came from except maybe from CCS.

    How did you create your project?  That's probably where we need to start.

     

  • 0 in reply to Anthony F. Seely
    Prodigy 65 points

    Hi Anthony,

    I created the file according to a training video using halcogen and then used ccs to build the project.

    CCS wasn't generating the .out file by default so I went to the project properties and included the command file in linker option which made the .out file appear.

  • 0 in reply to Anurag Meena1
    TI__Guru 68930 points

    Hi, I think something went wrong, because you shouldn't have two linker command files this way.

    HalCoGen creates a linker command file for you and you should only need this .cmd file.

    I'd just try again with a clean project file.   If you want me to check the video please shoot me a link to the one you were looking at.