Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32

Forum List Topic List

[ prev topic | next topic ]  

undefined reference to `_exit'

Posted by OpenJitendra on 2015-08-03 14:13

I’ve transferred IAR code to system workbench for STM32 but getting the folloing error while building:

arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -Wl,-Map=output.map -Wl,

c:/ac6/systemworkbench/plugins/fr.ac6.mcu.externaltools.arm-none.win32_1.0.0.201410081102/tools/compiler/bin/../lib/gcc/arm-none-eabi/4.8.4/../../../../arm-none-eabi/lib/armv7e-m\libc.a(lib_a-exit.o): In function `exit’:
exit.c:(.text.exit+0x16): undefined reference to `_exit’
collect2.exe: error: ld returned 1 exit status


Can anyone help.

Thanks
Jitendra

Reads: 15029
Link
Posted by dautrevaux on 2015-08-04 09:19 France

Hi Jitendra,

If you transfer code from IAR, the problem is related to the different standard C libraries used (IAR has its own C library and System Workbench uses a newlib-based library provided by linaro).

The best way to import from another tool is to create a standard System Workbench project, selecting the board and firmware library you want to use (StdPeriph or HAL) then copy just your application code and header files in the src and inc folders of the newly created project; do not copy any of the IAR-provided files, only your own source code and it should work without problem.

Bernard

Link
Posted by OpenJitendra on 2015-08-05 12:12

Hello Bernard,

It worked. Thanks...

Jitendra

Link