Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32


[SOLVED] _exit again - Nucleo401 + example IHM01A1

Hi everybody,

I have board - NucleoF401RE, and expansion board IHM01A1 (motor controller)

I tried load and debug some example program from ST.COM. But when try compile it, I receive error:

‘Building target: STM32F401RE-Nucleo.elf’
‘Invoking: MCU GCC Linker’
arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -Wl,-Map=output.map -Wl,--gc-sections -lm -o “STM32F401RE-Nucleo.elf” @”objects.list”
c:/ac6/systemworkbench/plugins/fr.ac6.mcu.externaltools.arm-none.win32_1.7.0.201602121829/tools/compiler/bin/../lib/gcc/arm-none-eabi/5.2.1/../../../../arm-none-eabi/lib/armv7e-m/fpu\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
make: *** STM32F401RE-Nucleo.elf Error 1


Google and other friends find some suggestion but without effect.


Any idea?

Thanks...

France

Hi,

You have obviously converted the project from C to C++ (as you are using collect2 in th elink phase). This conversion has a small bug (that will be corrected soon) where link editor options set to the C project are not transfered to the C++ project (as th elink editor is different).

You should add in project >> Properties >> C/C++ Build >> Settings >> MCU G++ Linker >> Miscellaneous in the appropriate text box the “-specs=nosys.specs -specs=nano.specs” settings that are provided in the C version of the project.

Alternatively you can also get the syscalls.c file from a System Workbench-generated project and place a copy in the source folder, near your main.c file

Bernard (Ac6)


Hi Bernard,

Now it is working,

thanks for help.

lx.