Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STM32F411 mbed blinky build failed in EmBitz #4096

Closed
vargham opened this issue Mar 31, 2017 · 7 comments
Closed

STM32F411 mbed blinky build failed in EmBitz #4096

vargham opened this issue Mar 31, 2017 · 7 comments
Assignees

Comments

@vargham
Copy link

vargham commented Mar 31, 2017

Description

Exported mbed blinky for NUCLEO-F411RE (STM32F411RET6) to EmBitz. Build failed. Same project export works fine with STM32F103. The online compilation is fine. Plain mbed lib, no OS.
Note: Have to manually copy mbed_config.h as described here: #4075

  • Type: Bug
  • Priority: Major
-------------- Build: mbed_blinky in mbed_blinky ---------------
Compiling: main.cpp
Linking executable: .\build\mbed_blinky.elf
mbed\TARGET_NUCLEO_F411RE\TOOLCHAIN_GCC_ARM\libmbed.a(mbed_wait_api_no_rtos.o): In function `wait':
mbed_wait_api_no_rtos.c:(.text.wait+0x0): multiple definition of `wait'
c:/program files (x86)/embitz/1.11/share/em_armgcc/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/lib/armv7e-m/softfp\libc.a(lib_a-syswait.o):syswait.c:(.text.wait+0x0): first defined here
collect2.exe: error: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 3 seconds)
0 errors, 0 warnings (0 minutes, 3 seconds)

Bug

Target
STM32F411

Toolchain:
Online IDE exporter, EmBitz, GCC_ARM

Expected behavior
Exported project should be built as-is.

Actual behavior
BUild failes with error.

Steps to reproduce
Create mbed blinky example for STM32F411 target, export to EmBitz and try to build.

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 3, 2017

cc @EmBitz @theotherjimmy

@theotherjimmy
Copy link
Contributor

theotherjimmy commented Apr 3, 2017

This might be a targets.json mis-configuration. Does it mbed compile correctly?

@theotherjimmy
Copy link
Contributor

theotherjimmy commented Apr 3, 2017

Also, I can't find the target STM32F411 could you include your target in the description or post it in a comment below? You used a NUCLEO_F411RE.

@theotherjimmy
Copy link
Contributor

@EmBitz I don't think you need to worry about this one. I'll let you know if I need your help after I root-cause it.

@vargham
Copy link
Author

vargham commented Apr 3, 2017

Yes, I used this board https://developer.mbed.org/platforms/ST-Nucleo-F411RE/
The online compilation is fine.

@theotherjimmy
Copy link
Contributor

Thanks for the clarification @vargham I'm going to do this export myself and see what's what.

@ciarmcom
Copy link
Member

ARM Internal Ref: IOTMORF-1833

@ghost ghost closed this as completed Mar 28, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants