3 years, 1 month ago.

Having problems compiling with newly installed mbed CLI

Hello all,

I am currently trying to compile the mbed_blinky project on my newly installed mbed CLI. I just want to make sure the binary work on my FRDM-K64F. However I currently get this error message (at the bottom) also given are the version returns from the various installed support clients for mbed CLI. " C:\Users\spms0\mbed_blinky>python version Python 2.7.8

C:\Users\spms0\mbed_blinky>git version git version 2.10.0.windows.1

C:\Users\spms0\mbed_blinky>hg version Mercurial Distributed SCM (version 3.9.2) (see https://mercurial-scm.org for more information)

Copyright (C) 2005-2016 Matt Mackall and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

C:\Users\spms0\mbed_blinky>mbed version 0.9.10

C:\Users\spms0\mbed_blinky>mbed compile -m K64F -t GCC_ARM [ERROR] Attribute 'default_build' not found in target 'K64F' [mbed] ERROR: "python" returned error code 1. [mbed] ERROR: Command "python -u C:\Users\spms0\mbed_blinky\.temp\tools\make.py -t GCC_ARM -m K64F source . build .\BUILD\K64F\GCC_ARM" in "C:\Users\spms0\mbed_blinky" -"

I can see that it is a problem with finding the target K64F and that causes python to return the error but I don't understand why this is a problem as the directory mbed_blinky has a directory mbed which contains a target directory for K64F TARGET_K64F.

If anyone could help me as to why this is happening it would be very appreciated.

Sean,

Can you try update Python please, CLI was tested with 2.7.11.

Can you also tell me your version of the GCC_ARM.

arm-none-eabi-gcc version

Regards,

Andrea

posted by Andrea Corrado 02 Nov 2016

Hi Andrea,

Thanks for the reply. I updated my Python version and everything seems to have worked. Thanks for the help, I think I just accidentally overlooked the fact that the version was 2.7 in the video.

Kind Regards, Sean

posted by Sean Suttie 03 Nov 2016
Comment on this question

2 Answers

3 years, 1 month ago.

I have the same problem. With the blinky code from ARM it is working, with my blinkycode which I published for test not.

https://developer.mbed.org/users/xdeschain/code/Nucleo_blink_led/

arm-none-eabi-gcc version arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496] Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

python version Python 2.7.12

pip version pip 8.1.1 from c:\python27\lib\site-packages (python 2.7)

git version git version 2.10.1.windows.1

hg version Mercurial Distributed SCM (version 3.9.2) (see https://mercurial-scm.org for more information)

Copyright (C) 2005-2016 Matt Mackall and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

3 years ago.

I had the same problem and posted an issue on github. The problem exists in the latest revisions of the mbed library. The solution is to use an older revision

https://github.com/ARMmbed/mbed-cli/issues/391#issuecomment-259932373


You need to log in to post a question