Skip to main content
Graduate II
September 14, 2023
Solved

Can not build "FatFs_uSD_RTOS" for STM32F746G-Disco board?

  • September 14, 2023
  • 3 replies
  • 1594 views

Can not build "FatFs_uSD_RTOS" for STM32F746G-Disco board?

Hi all,

I got this example "FatFs_uSD_RTOS" from the STM32cubeIDE "Example Selector" after selecting the STM32F746G-Disco board. I haven't change anything in it and tried to build it but I get these errors (below). The instructions don't say that I have to do anything just to build the project. What Am I missing? Thanks.


C:/ST/STM32CubeIDE_1.12.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/ST/STM32CubeIDE_1.12.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/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:/ST/STM32CubeIDE_1.12.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/ST/STM32CubeIDE_1.12.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/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:/ST/STM32CubeIDE_1.12.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/ST/STM32CubeIDE_1.12.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/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:/ST/STM32CubeIDE_1.12.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/ST/STM32CubeIDE_1.12.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/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: FatFs_uSD_RTOS.elf

arm-none-eabi-size FatFs_uSD_RTOS.elf
arm-none-eabi-objdump -h -S FatFs_uSD_RTOS.elf > "FatFs_uSD_RTOS.list"
arm-none-eabi-objcopy -O binary FatFs_uSD_RTOS.elf "FatFs_uSD_RTOS.bin"
text data bss dec hex filename
27948 28 11948 39924 9bf4 FatFs_uSD_RTOS.elf
Finished building: default.size.stdout

Finished building: FatFs_uSD_RTOS.bin

Finished building: FatFs_uSD_RTOS.list

19:15:17 Build Failed. 4 errors, 4 warnings. (took 1s.698ms)

    This topic has been closed for replies.
    Best answer by KDJEM.1

    Hello @Rodo ,

    Thank you for bringing the issue to your attention.

    I confirm the issue and I reported internally.

    Sorry for any inconvenience.

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

    Thank you.

    Kaouthar

    3 replies

    Technical Moderator
    September 14, 2023

    Hello @Rodo ,

    Could you please try this workaround :

     Go to Windows > Preferences
    Open the tab Error Parsers into C/C++ > Build > Settings
    Select GNU Linker Error Parser, double click on the pattern for the 1st severity Ignore
    Changer :
    (.*?):?(\(\.[^\s+]+\+.*\))?:\s*(In function [`'"](.*)['"]:)
    to :
    (.*?):?(\(\.[^\s+]+\+.*\))?:\s*([Ii]n function [`'"](.*)['"]:)

    I advise you to consult this Post to get more information related to this issue.

    Please let me know if the issue is solved.

    Thank you for your contribution in the community.

    Kaouthar

    RodoAuthor
    Graduate II
    September 15, 2023

    The errors went away, the warnings remain.

    KDJEM.1Answer
    Technical Moderator
    September 15, 2023

    Hello @Rodo ,

    Thank you for bringing the issue to your attention.

    I confirm the issue and I reported internally.

    Sorry for any inconvenience.

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

    Thank you.

    Kaouthar