We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hello,My Company currently uses the GNU Arm Toolchain 10.3 to compile our project based on S32K3xx MCU from NXP (cortex-M7)We uses Clion IDE to develop our code, cmake method to prepare the compilation and make the link to the compiler then make to execute the compilation.I know we could pass to GNU Arm Toolchain 14.2
But we just saw that a new compiler is being developped : Arm Toolchain for embedded (https://developer.arm.com/Tools%20and%20Software/Arm%20Toolchain%20for%20Embedded#Technical-Specifications)It will be free and compatible with GNU commands.We are evaluating the possibility of switching to this new compiler in future.One of the main interest is that a paid FUSA version would be available (in 2026) if we need to support this standard.So I downloaded the Beta(clang version 20.0.0) version of Arm Toolchain for embeded.First step was fine and the integration is easy with our environnement.But our architecture seems not to be supported.Endeed when I type command : clang.exe --print-supported-cpusI see the list of supported cpu but there are no cortex-M7
Do you know if Arm Toolchain for embeded will support Cortex-M7 in future ?if yes, is there a time map about the supported cpu ?
Note : We also check the possibility to pass to Arm compiler for embedded (which already has a FUSA version).But I am not sure it will easy fit in our cmake environnement.More over it's no more supported since march 2025.So we have preference for Arm Toolchain for embedded even if we have to wait for it.
Thanks,Mathieu
Hi Mathieu,Arm Toolchain for Embedded does support the Cortex-M7, however, due to how the "clang" driver works, you must also use the --target command-line option:
clang --target=arm-none-eabi --print-supported-cpus
Note that the library used by ATfE 20 (Picolib) isn't a drop-in replacement for the GNU Toolchain's Newlib, and you might have to make some changes to your linker script and startup code.I hope this helps,Stam
Hello Stam,Thanks for response.Indeed by using target_compile_options(${PROJECT_NAME} PRIVATE --target=arm-none-eabi)in my cmake configuration, I was able allow to correctly use arm-none-eabi.I was able to execute the cmake pre-compilation and also most of the compilation step.I have some error about link to library as gcc, c, ... but it's normal.I will check how to use the Picolib.Thanks for your help,Mathieu