Linker errors when building MLO

qxc

After a long time I modified some minor things in MLO code and tried to build it. Amazingly I stumble upon a bunch of strange linker errors:

unresolved symbol __aeabi_uidivmod, first referenced in <whole-program>
unresolved symbol __stack, first referenced in ./bl_init.obj
unresolved symbol __TI_auto_init, first referenced in ./bl_init.obj
unresolved symbol memcpy, first referenced in <whole-program>
unresolved symbol memset, first referenced in <whole-program>
unresolved symbol strcmp, first referenced in ../../../../../../../binary/armv7a/cgt_ccs/am335x/evmAM335x/platform/Debug/platform.lib<board.obj>
unresolved symbol strncmp, first referenced in ../../../../../../../binary/armv7a/cgt_ccs/am335x/evmAM335x/platform/Debug/platform.lib<board.obj>

Any idea what I'm doing wrong now?

over 9 years ago

0 Lalindra Jayatilleke over 9 years ago

TI__Mastermind 30365 points

qxc,

They are strange indeed. I assume you are trying to build the bootloader project.
pdk_am335x_1_0_2\packages\ti\starterware\bootloader\ccs\bootloader ?

Lali

0 qxc over 9 years ago in reply to Lalindra Jayatilleke

Genius 5820 points

It is the bootloader from AM335X_StarterWare_02_00_01_01/bootloader/

0 qxc over 9 years ago in reply to qxc

Genius 5820 points

OK, finally I found the reason: on compilation CCS tried to build a C-runtime library which was needed for this project. Due to an bug in CCS-Linux installer writing of this file failed resulting in the above linker errors in a next step.

Amazingly this failure can NOT be seen in the error window of CCS, one has to dig through the console output to find the related error message.

Processors

Processors forum

Linker errors when building MLO