cancel
Showing results for 
Search instead for 
Did you mean: 

Compiler errors with STMCubeIDE 1.13.2 on project for STM32469I-DISCO / 32F469IDISCOVERY

testcode99
Associate II

Using the latest STM32CubeIDE 1.13.2, it's giving errors compiling a STM32469I-DISCO 32F469IDISCOVERY project, i.e. GPIO_EXT example. This project was imported by STM32CubeIDE from STM32Cube_FW_F4_V1.27.1\Projects\STM32469I-Discovery\Examples\GPIO\GPIO_EXTI\SW4STM32.

The 4 errors are like below. Is this a problem with the project or with STM32CubeIDE? Thanks

C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeIDE_1.13.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.1.202309131626\tools\arm-none-eabi\bin\ld.exe: C:/Program Files/STMicroelectronics/STM32Cube/STM32CubeIDE_1.13.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.1.202309131626/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-closer.o): in function `_close_r':

(.text._close_r+0xc): warning: _close is not implemented and will always fail

C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeIDE_1.13.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.1.202309131626\tools\arm-none-eabi\bin\ld.exe: C:/Program Files/STMicroelectronics/STM32Cube/STM32CubeIDE_1.13.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.1.202309131626/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-lseekr.o): in function `_lseek_r':

(.text._lseek_r+0x10): warning: _lseek is not implemented and will always fail

C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeIDE_1.13.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.1.202309131626\tools\arm-none-eabi\bin\ld.exe: C:/Program Files/STMicroelectronics/STM32Cube/STM32CubeIDE_1.13.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.1.202309131626/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-readr.o): in function `_read_r':

(.text._read_r+0x10): warning: _read is not implemented and will always fail

C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeIDE_1.13.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.1.202309131626\tools\arm-none-eabi\bin\ld.exe: C:/Program Files/STMicroelectronics/STM32Cube/STM32CubeIDE_1.13.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.1.202309131626/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-writer.o): in function `_write_r':

(.text._write_r+0x10): warning: _write is not implemented and will always fail

Finished building target: STM32469I_DISCOVERY.elf

18:56:16 Build Failed. 4 errors, 4 warnings. (took 4s.765ms)

 

2 REPLIES 2
TDK
Guru

There was an upgrade to the toolchain with the recent version which is causing these warnings. See here for some good answers on why exactly this is happening:

https://stackoverflow.com/questions/73742774/gcc-arm-none-eabi-11-3-is-not-implemented-and-will-always-fail

 

At its core, this is probably something that will get resolved in the next STM32CubeIDE version.

 

> Finished building target: STM32469I_DISCOVERY.elf

As you can see, these are warning, not errors, and the code compiles. You can ignore them if you want.

If you feel a post has answered your question, please click "Accept as Solution".
KDJEM.1
ST Employee

Hello @testcode99 ,

I confirm the issue and I reported internally.

Internal ticket number: 161907 (This is an internal tracking number and is not accessible or usable by customers).

Sorry for any inconvenience and thank you for your contribution in STCommunity 🙂.

Kaouthar

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.