18:53:27 **** Incremental Build of configuration Debug for project test_NUCLEO_G474RE ****
Building file: ../system/src/newlib/assert.c
Invoking: GNU Arm Cross C Compiler
arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -Og -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -ffreestanding -fno-move-loop-invariants -Wall -Wextra -g3 -DDEBUG -DTRACE -DOS_USE_TRACE_SEMIHOSTING_DEBUG -I"../include" -I"../system/include" -I"../system/include/cmsis" -I"../system/include/DEVICE" -std=gnu11 -MMD -MP -MF"system/src/newlib/assert.d" -MT"system/src/newlib/assert.o" -c -o "system/src/newlib/assert.o" "../system/src/newlib/assert.c"
make: *** [system/src/newlib/subdir.mk:39: system/src/newlib/assert.o] Error -1073741502
"make all" terminated with exit code 2. Build might be incomplete.
18:53:30 Build Failed. 1 errors, 0 warnings. (took 2s.981ms)
I installed gcc-arm-none-eabi-10-2020-q4-major-win32 and eclipse on Windows 10, and I have updated CMSIS package in eclipse, I want to make a test project for NUCLEO-G474RE board, but it couldn't even be built, and propmted:
and, the code at start was shown in console window.
The message says that the compiler itself is not working
Where is a tutorial for using GNU Tools ARM Embedded in eclipse on Windows 10 ? I tried more than a week for this, but still couldn't run a simple example on NUCLEO-G474RE board.
As you're using an ST board, why not use ST's STM32 CubeIDE? It is Eclipse-based.
mian qi said:Where is a tutorial for using GNU Tools ARM Embedded in eclipse on Windows 10 ?
I have STM32CubeIDE installed and I used it, I want try eclipse because testing for other project.
I installed "gcc-arm-none-eabi-10-2020-q4-major-win32.exe" here:https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads, anf my windows was 64-bits, is this the reason for it couldn't be started?
I tried this tutorial:
(www.digikey.com/.../Getting Started with the STM32L432 Nucleo-32 using Eclipse and the GNU ARM Toolchain)
It was said:
You should now open up the folder where you have downloaded ST’s drivers and HAL code. The first file needed is a linker script (.ld) from one of the example projects. Search *.ld in the folder and a few should come up, as of writing they are all equal. Pick your favorite and copy it to the ldscripts folder of the eclipse project.
The only reason I ever did a manual setup of Eclipse was because ST didn't have their own.
That was a long time ago - now they do have their own, I just use it.
FWIW, the reference I used was https://mcuoneclipse.com/
It was called something different back then, and things have moved on - it still seems to be active, though.
The latest version of STM32 CubeIDE - 1.6.0 - is supposed to have better handling of "plain vanilla" Eclipse projects ...
https://community.st.com/s/question/0D53W00000aqNBiSAM/cubeide-imported-eclipse-c-project-incorrectly-defines-cplusplus - see the reply by Mattias Norlander (ST Employee) of March 4, 2021 at 3:30 PM
Why I stick to use eclipse + arm-none-eabi-gcc, because the board I used came from a vendor other than ST, the recommend tools were IAR and MDK, while the two have code limits.
mian qi said:the board I used came from a vendor other than ST,
But, in the opening post:
mian qi said:I want to make a test project for NUCLEO-G474RE board
That is an ST board!
The board I used for testing the tools environment.
View all questions in GNU Toolchain forum