Loading...
 
Skip to main content

System Workbench for STM32

Forum List Topic List

Forums » System Workbench for STM32 » Fresh installation --> none-eabi-g++ and arm-none-eabi-gcc not found
 
Thread actions
Print this page
  • Print all pages

    • Fresh installation --> none-eabi-g++ and arm-none-eabi-gcc not found

    Posted by h708697 on 2015-10-10 11:46

    Hi,

    I have installed Eclipse Mars C++ 32bit and then I installed openSTM32 with alle windows stuff by adding New Software Plugin.

    Then I tried to create a new project for STM32 F303RE and compile it.

    Error:
    1. arm-none-eabi-g++ not found
    2. arm-none-eabi-gcc not found


    I thought that the arm gcc is included with the package "ARM Compiler for MCU"?
    See the screenshot attached.


    Best regards!

    Eclipse New Software Installation OpenSTM32.png (47.54 Kb)
    Reads: 21620

    Posted by rkadrmas on 2015-11-18 22:21 United States

    This happend to me also. I am running Keppler on OSX. I quit Eclipse and restarted it and the problem went away.
    Check the project C/C++ Build | Settings | MCU Settings | Path . Mine is ${openstm32_compile_path}


         Posted by doctek on 2015-12-11 21:41

    While I would agree the problem is harmless if the compilation runs and you get the binaries, it doesn't seem harmless when that DOESN'T happen. I see failure on the very first build that I try. Here are the last two lines from the Console:
    arm-none-eabi-gcc: error trying to exec 'cc1': execvp: No such file or directory
    make: *** Drivers/STM32L4xx_HAL_Driver/stm32l4xx_hal.o Error 1

    When I look at my Settings, as suggested, I see the ${openstm32_compiler_path} path variable pointed to, but I have no idea what the value of it is. How would I find it out?

    I suspect there is a problem with my installation of the software, but I have no idea how to find out what that probem is.

    Thanks for any assistance.

         Posted by doctek on 2015-12-12 06:14

    So while waiting for a reply to my question, I am experimenting a little. I put the path to the arm-none-eabi version of cc1 in my path so that it is found. (I still have no idea of why I shuld have to do this for a new installation, so my previous question still stands.) But while the compiler runs, I now get this failure:
    In file included from /home/jim/workspace/stm32l476g-disco_hal_lib/CMSIS/device/stm32l476xx.h:184:0,
    from /home/jim/workspace/stm32l476g-disco_hal_lib/CMSIS/device/stm32l4xx.h:123,
    from /home/jim/workspace/stm32l476g-disco_hal_lib/HAL_Driver/Inc/stm32l4xx_hal_def.h:48,
    from /home/jim/workspace/stm32l476g-disco_hal_lib/HAL_Driver/Inc/stm32l4xx_hal_rcc.h:47,
    from /home/jim/workspace/stm32l476g-disco_hal_lib/HAL_Driver/Inc/stm32l4xx_hal_conf.h:193,
    from /home/jim/workspace/stm32l476g-disco_hal_lib/HAL_Driver/Inc/stm32l4xx_hal.h:48,
    from ../Utilities/STM32L476G-Discovery/stm32l476g_discovery.h:56,
    from ../Utilities/STM32L476G-Discovery/stm32l476g_discovery.c:40:
    /home/jim/workspace/stm32l476g-disco_hal_lib/CMSIS/core/core_cm4.h:187:95: fatal error: stdint.h: No such file or directory
    #include /* standard types definitions */

    Any suggestions on how to fix this? Adding the path to stdint.h doesn't help. I think that is because of the implied meaning of the ange brackets.


         Posted by geraldfryjr on 2015-12-12 06:52

    I had issues with Eclipse Mars too, So I switched to Luna and everything is working as it should.
    However I am using the STM32F429I-discovery board (LCD version.

    jer 😊


         Posted by doctek on 2015-12-13 03:28

    Thanks for the suggestion, Jer. However, since the AC6 site doesn't mention this as a requirement, I'll try to make the newest version of Eclipse work.

    So one thing I noticed was that the version of the arm tools that I had was 4.8.2 and that the recommended version (newest version) is 4.9.3. So I got rid of my old install of the tools and installed the newest arm tools from the Terry Guo Launchpad site. Here's what happens when I try to build now:
    arm-none-eabi-gcc: error trying to exec '/home/jim/.p2/pool/plugins/fr.ac6.mcu.externaltools.arm-none.linux64_1.3.0.201507241112/tools/compiler/bin/../lib/gcc/arm-none-eabi/4.9.3/cc1': execv: No such file or directory

    Where did that path come from?? I have no idea, but one interesting thing: cc1 actually exists on the path! So why isn't it being executed??

    Again, any clues would be appreciated. The key one in my mind is exactly where are the tool paths specified that Eclipse uses? If I knew, I think I could fix them. Is AC6 doing things that are causing this mess?


         Posted by geraldfryjr on 2015-12-16 10:41

    The problem I was having with Mars were certain menu panels were hanging and etither not opening and or not functioning when they did.

    Also I had used Luna before so I am used to it.

    I was having issues of Mars not finding the complier too!!!
    And unfortunately I am to much of a noob to understand fully why this was happening.
    I think that I did finally get it to work but it wouldn't create the .bin files for me and only came up with some kind of .elf file.

    Others have reported such bugs too of trying to get Mars to work and all of the examples I had found that did work, they were using Luna.
    I had seen one suggestion with the same issues and they said to use Luna.
    This was strictly for Linux and I haven't seen any reports of troubles with windows yet.

    So I switch back to Luna and had a Blinky example working the first time around.

    Mars may be working fine in windows I only had it installed there for a brief time to just practice some simple C code.

    When I switched back to luna I was able to install the proper arm-none-eabi compiler right from the setup menus of ST Workbench and it worked exactly as it should.

    I have not tried Mars again since but now that I do know all of the proper steps to get it working I guess I should give Mars another try.

    Anyhow in case you have not seen my thread I describe each exact step in order to get it working in Luna, If a recall Mars was very similar if not the same.

    Here is that thread so that you can look through it and maybe there is something there to help you when your setting up the Mars version.

    http://www.openstm32.org/tiki-view_forum_thread.php?comments_parentId=1392&topics_offset=66

    My piont was that the First time I had tried to set it up I already had the complier in my system but the IDE was not finding it no matter what I did.

    I am not good with setting paths yet.

    By choosing the right things while setting up STW I didn't have to set any path's and it every thing was setup properly and it worked fine the First time.

    Cheers!!

    jer 😊


         Posted by doctek on 2015-12-19 20:48

    Thanks for your thorough reply, Jer. Eclipse Mars was not the problem. What finally works for me is to specify the full path to the correct tool set (/usr/bin in my case) in the project setup C/C++ section. The ST Workbecnh version of the tools most definately did not work! I saw mention that they are an older version and only for 32 Bit Linux. I'm running 64 Bit and did not want to mess with the compatibility library - especially not to run an older version!

    Note that the debugger worked just as it should without further complications.No need to pont to alternate directories, etc.

    Again, thanks for the help.


         Posted by geraldfryjr on 2015-12-20 14:04

    Cool, I am glad that you got it working!!

    I did eventually get that far but for some reason my project wasn't compling correctly.
    I will have to give Mars another try since I now have a simple project that I know will work.

    I am using a 64bit OS as well.

    Cheers!!

    jer 😊


         Posted by jainm1 on 2017-08-15 23:28
    Extract gcc-arm-none-eabi-5_4-2016q3-20160926-win32.zip file in C:\Ac6\SystemWorkbench\plugins\fr.ac6.mcu.externaltools.arm-none.win32_1.13.2.201705091103\tools\compiler folder and it will solve the issue.

     
    Collapse/expand modules below