steve scutt

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

11 years ago.

compiling the test programs using GCC_ARM...error 2 problem.

Hi all. I thought I'd attempt to try mbed offline so have successfully built the library for the NUCLEO_L152_re board. However, when I attempt to compile the tests using make.py I get the following error: Windowserror: [Error2] the system cannot find the file specified.

Verbose it looks like this:

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\user>cd \mbed/wo*

C:\mbed\workspace_tools>make.py -m NUCLEO_L152RE -t GCC_ARM -p 0 -d f:\

BUILD PROJECT: BASIC (NUCLEO_L152RE, GCC_ARM)

Link: basic [ERROR] [Error 2] The system cannot find the file specified

C:\mbed\workspace_tools>dir Volume in drive C has no label. Volume Serial Number is EC54-E0F4

Directory of C:\mbed\workspace_tools

03/03/2014 20:28 <DIR> . 03/03/2014 20:28 <DIR> .. 03/03/2014 18:24 5,902 autotest.py 03/03/2014 18:24 4,768 build.py 03/03/2014 18:24 <DIR> buildbot 03/03/2014 18:24 7,640 build_api.py 03/03/2014 18:34 5,443 build_api.pyc 03/03/2014 18:24 2,487 build_release.py 03/03/2014 18:24 1,284 build_travis.py 03/03/2014 18:24 2,058 client.py 03/03/2014 18:34 <DIR> data 03/03/2014 18:24 <DIR> dev 03/03/2014 18:25 <DIR> export 03/03/2014 18:24 3,640 export_test.py 03/03/2014 18:24 4,593 hooks.py 03/03/2014 18:34 4,460 hooks.pyc 03/03/2014 18:25 <DIR> host_tests 03/03/2014 18:24 2,712 libraries.py 03/03/2014 18:34 2,535 libraries.pyc 03/03/2014 18:24 7,958 make.py 03/03/2014 18:24 1,501 options.py 03/03/2014 18:34 1,747 options.pyc 03/03/2014 18:24 1,942 patch.py 03/03/2014 18:34 2,203 patch.pyc 03/03/2014 18:24 2,446 paths.py 03/03/2014 18:34 2,576 paths.pyc 03/03/2014 20:28 48 private_settings.py 03/03/2014 20:28 187 private_settings.pyc 03/03/2014 18:24 2,679 project.py 03/03/2014 18:24 5,741 server.py 03/03/2014 18:24 3,696 settings.py 03/03/2014 18:34 2,879 settings.pyc 03/03/2014 18:24 14,239 singletest.py 03/03/2014 18:24 4,211 size.py 03/03/2014 18:24 2,246 syms.py 03/03/2014 18:24 10,845 synch.py 03/03/2014 18:24 11,988 targets.py 03/03/2014 18:34 15,967 targets.pyc 03/03/2014 18:24 27,063 tests.py 03/03/2014 18:40 15,487 tests.pyc 03/03/2014 18:34 <DIR> toolchains 03/03/2014 18:24 2,238 utils.py 03/03/2014 18:34 3,806 utils.pyc 03/03/2014 18:24 578 init.py 03/03/2014 18:34 716 init.pyc 37 File(s) 192,509 bytes 8 Dir(s) 20,408,938,496 bytes free

C:\mbed\workspace_tools>make.py -m NUCLEO_L152RE -t GCC_ARM -p 0

BUILD PROJECT: BASIC (NUCLEO_L152RE, GCC_ARM)

Link: basic [ERROR] [Error 2] The system cannot find the file specified

C:\mbed\workspace_tools>make.py -m NUCLEO_L152RE -t GCC_ARM -p 0 -v

BUILD PROJECT: BASIC (NUCLEO_L152RE, GCC_ARM)

Link: basic c:/C:/GNUToolsARM/arm_gcc/bin\arm-none-eabi-gcc -Wl,gc-sections -Wl,wrap,mai n -mcpu=cortex-m3 -mthumb specs=nano.specs -TNone -o C:\mbed\build\test\NUCLEO _L152RE\GCC_ARM\MBED_A1\basic.elf C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCH AIN_GCC_ARM\cmsis_nvic.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_A RM\misc.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\retarget.o C :\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_adc.o C:\mbed \build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_aes.o C:\mbed\build \mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_aes_util.o C:\mbed\build\ mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_comp.o C:\mbed\build\mbed\ TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_crc.o C:\mbed\build\mbed\TARGET _NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_dac.o C:\mbed\build\mbed\TARGET_NUCLE O_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_dbgmcu.o C:\mbed\build\mbed\TARGET_NUCLEO_L 152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_dma.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\ TOOLCHAIN_GCC_ARM\stm32l1xx_exti.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLC HAIN_GCC_ARM\stm32l1xx_flash.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN _GCC_ARM\stm32l1xx_flash_ramfunc.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLC HAIN_GCC_ARM\stm32l1xx_fsmc.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_ GCC_ARM\stm32l1xx_gpio.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_A RM\stm32l1xx_i2c.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm 32l1xx_iwdg.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1x x_lcd.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_opam p.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_pwr.o C: \mbed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_rcc.o C:\mbed\ build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_rtc.o C:\mbed\build\ mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_sdio.o C:\mbed\build\mbed\ TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_spi.o C:\mbed\build\mbed\TARGET _NUCLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_syscfg.o C:\mbed\build\mbed\TARGET_NU CLEO_L152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_tim.o C:\mbed\build\mbed\TARGET_NUCLEO_L 152RE\TOOLCHAIN_GCC_ARM\stm32l1xx_usart.o C:\mbed\build\mbed\TARGET_NUCLEO_L152R E\TOOLCHAIN_GCC_ARM\stm32l1xx_wwdg.o C:\mbed\build\mbed\TARGET_NUCLEO_L152RE\TOO LCHAIN_GCC_ARM\system_stm32l1xx.o C:\mbed\build\test\NUCLEO_L152RE\GCC_ARM\MBED_ A1\.\main.o C:\mbed\build\test\NUCLEO_L152RE\GCC_ARM\MBED_A1\.\test_env.o -LC:\m bed\build\mbed\TARGET_NUCLEO_L152RE\TOOLCHAIN_GCC_ARM -lmbed -lstdc++ -lsupc++ - lm -lc -lgcc -lnosys -lmbed -lstdc++ -lsupc++ -lm -lc -lgcc -lnosys Traceback (most recent call last): File "C:\mbed\workspace_tools\make.py", line 164, in <module> macros=options.macros) File "C:\mbed\workspace_tools\build_api.py", line 65, in build_project return toolchain.link_program(resources, build_path, name) File "C:\mbed\workspace_tools\toolchains\init.py", line 461, in link_progr am self.link(elf, r.objects, r.libraries, r.lib_dirs, r.linker_script) File "C:\mbed\workspace_tools\toolchains\gcc.py", line 159, in link objects + ["-L%s" % L for L in lib_dirs] + libs)) File "C:\mbed\workspace_tools\toolchains\init.py", line 482, in default_cm d stdout, stderr, rc = run_cmd(command) File "C:\mbed\workspace_tools\utils.py", line 35, in run_cmd p = Popen(command, stdout=PIPE, stderr=STDOUT if redirect else PIPE, cwd=wd)

File "C:\Python27\lib\subprocess.py", line 672, in init errread, errwrite) File "C:\Python27\lib\subprocess.py", line 882, in _execute_child startupinfo) WindowsError: [Error 2] The system cannot find the file specified

C:\mbed\workspace_tools>

Would anyone be able to help me fix this problem? Any help appreciated. Thanks, Steve.

2 Answers

steve scutt
poster
11 years ago.

OK I re-built the library and now it looks like it starts to compile but then I get error 1 and it says it can't find the linker script calle "none"... In the make.py there is this line:

make.py linker line ???

 # Specify a different linker script
    parser.add_option("-l", "--linker", dest="linker_script",
                      default=None, help="use the specified linker script")

Do I need to add a path to the NUCLEO linker script?? If so, is there one and where is it? Please someone help ??

Martin Kojtal
11 years ago.

Hello steve scutt,

the error comes because NUCLEO boards are not supported by ARM GCC, not yet. Don't see any files in cmsis folder (linker plus startup).

I wonder why in targets.py GCC ARM is defined.. Going to check it and correct it. Thanks!

Regards,
0xc0170