STM32CUBEIDE UPDATE 1.13.0 causing failures - JULY 10, 2023 update

[Robmar]

After the July 10 STM32CUBEIDE update our STM32F407VG boards are no longer being detected, with the error "STM Error: No STM target found"

I've tried all the usual settings to recover, STM32CubeProgrammer, Mode under reset, powerdown, nothing lets me connect.

I can update the ST-Link firmware, but that's it.

The board continues to run any software previously installed, and have tried updating several boards that updated perfectly yesterday, but any updating of the ST-LINK firmware now causes the connection to be lost.

One strange thing, with the updated STM32CubeIDE, it request to update the link firmware if the Programmer updated previously, seems they are both using different versions.  I did update the programmer too.

Any ideas how to fix?

STM32Programmer log:

20:16:25 : Board : STM32F4DISCOVERY
20:16:25 : Voltage : 2.93V
20:16:25 : Error: No STM32 target found!
20:19:11 : ST-LINK SN : 0667FF495277504867232552
20:19:11 : ST-LINK FW : V2J42M27
20:19:11 : Board : STM32F4DISCOVERY
20:19:11 : Voltage : 2.93V
20:19:11 : Error: No STM32 target found!

STM32CubeIDE log:

STMicroelectronics ST-LINK GDB server. Version 7.4.0

Copyright (c) 2023, STMicroelectronics. All rights reserved.

Starting server with the following options:

Persistent Mode : Disabled

Logging Level : 1

Listen Port Number : 61234

Status Refresh Delay : 15s

Verbose Mode : Disabled

SWD Debug : Enabled

Target no device found

Error in initializing ST-LINK device.

Reason: No device found on target.

[Robmar]

Also getting link failures after the update but only in release code:-

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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-fstatr.o): in function `_fstat_r':

(.text._fstat_r+0xe): warning: _fstat is not implemented and will always fail

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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-signalr.o): in function `_getpid_r':

(.text._getpid_r+0x0): warning: _getpid is not implemented and will always fail

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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-isattyr.o): in function `_isatty_r':

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

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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-signalr.o): in function `_kill_r':

(.text._kill_r+0xe): warning: _kill is not implemented and will always fail

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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-openr.o): in function `_open_r':

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

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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

D:/ST/STM32CubeIDE_1.10.1/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: D:/ST/STM32CubeIDE_1.10.1/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

[Robmar · Accepted solution]

So manually updating the toolchain in settings has fixed the Release compile errors, and after several reboots STM32CubeProgrammer is working again. Quite a lot of stress to say the least but we're back in business.

Hope this is useful to someone else.

[ASalc.1]

Please, Could you elaborate more on this?

[Robmar]

It is simple, following the last firmware update to the CubeIDE, now when I build our application the first time it lists those 9 errors, if I click build again, it builds without errors, and if I click it again, it lists 9 errors,... and so on.

The STM link error is another issue, on some boards after the first programming

attempt we get the link failure message and the file Fail.txt appears with the message: The interface firmware FAILED to reset/halt the target MCU.

Tried the suggested methods to connect, reset down, BOOT0 to VDD, to no avail.

Read the post about voltage levels, so if it's useful: from the Debug USB connection it gives 2.96V on VDD, and 4.66V on VCC.

[Robmar]

Okay, it helped but we are back to 9 link errors appearing every other build.  Those same errors disappear when we build once more after the failures, and then reappear on the next build!

I have to say that STM IDE is a rough piece of software with numerous odd bugs, and STM should get to grip with these limitations as it wastes a lot of our time, IMHO.

[Robmar]

UPDATE: The STM link failure that causes the "FILE.TXT" message to be created on the USB Debug folder seems to have been caused not by the IDE update (which causes the intermittent link errors), but by a component fault on the STM32F407G-DISC1 boards.  SB9 has a 0 ohm resistor chip, the components look different to its neighbours and is open circuit. Soldering it and closing the link fixes the Link failure.