Link problem with KDS300

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Link problem with KDS300

476件の閲覧回数
dafodil
Contributor III

I just start to work with KDS300, I tried with a project that works fine (without PE or KSDK) with K64F

 

I got this error, I don't know how to solve that.

 

arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -O1 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Wall  -g -T ../../config_files/MK64FN1M0xxx12_flash.ld -Xlinker --gc-sections -Wl,-Map,"frdmk64f_boot.map" -Xlinker --defsym=__stack_size__=0x2000  -Xlinker --defsym=__heap_size__=0x2000 -o "frdmk64f_boot.elf" -Xlinker --start-group  ./startup/MK64F12/gcc/startup_MK64F12.o  ./startup/MK64F12/system_MK64F12.o  ./startup/startup.o  ./fnet_stack/stack/fnet_arp.o ./fnet_stack/stack/fnet_checksum.o  ./fnet_application/fapp_fs_image.o ./fnet_application/fapp_fs_image_http09.o ./fnet_application/fapp_http.o ./fnet_application/fapp_llmnr.o ./fnet_application/fapp_mem.o ./fnet_application/fapp_params.o ./fnet_application/fapp_ping.o ./fnet_application/fapp_setget.o ./fnet_application/fapp_telnet.o ./fnet_application/fapp_tftp.o  ./main.o-Xlinker --end-group

c:/freescale/kds_3.0.0/toolchain/bin/../lib/gcc/arm-none-eabi/4.8.4/../../../../arm-none-eabi/lib/armv7e-m/fpu\libg.a(lib_a-exit.o): In function `exit':

exit.c:(.text.exit+0x16): undefined reference to `_exit'

ラベル(1)
タグ(1)
0 件の賞賛
1 返信

309件の閲覧回数
marek_neuzil
NXP Employee
NXP Employee

Hello Bernard,

I suppose you have used (imported) an existing project in KDS 3.0.0 and you executed the Build operation.

In the main menu, open Project > KDS Upgrade Assistant, select the project and click on the Next.

The following options with descriptions are displayed in the KDS Upgrade Assistant for updating of your project:

pastedImage_0.png

You need to add the implementation of exit.c function.

Best Regards,

Marek Neuzil