About fronders

fronders · 2023-10-17

I have a project created with CubeMX v6.8.0 and HAL L4 v1.17.2. Using Windows 10 x64Today I wanted to update it using CubeMX v6.9.2 and HAL L4 v1.18.0, and when regenerating, CubeMX wiped the linker settings "Library search path". I remember this hap...

fronders · 2023-03-24

This is absolutely ridiculous and unacceptable. After I installed STM32CubeCLT v1.12.0 my system PATH variable has been wiped and now contains ONLY CubeCLT related paths, while all the rest are gone. This has made a bunch of installed software unusab...

fronders · 2022-12-24

I'm using SBSFU v2.6.2 on a Windows 10 x64 machine with CubeIDE v1.11.0I was recently modifying the postbuild script in an SBSFU-based project and noticed it has a bug setting the PATH variable when looking for prepareimage executable:export PATH=$ba...

fronders · 2022-06-17

Hi! I'm using STM32CubeProgrammer v2.10.0 under Windows 10 Pro 21H2 x64 (Build 19044.1766) and when starting to flash devices in automatic mode, CubeProgrammer flashes normally the 1st device with messages only in the log, but starting with 2nd and f...

fronders · 2021-12-07

When compiling UserApp from 2_Images example application for NUCLEO-L476RG linker outputs the following error: cannot use executable file '../../SBSFU/Debug/se_interface_app.o' as input to a linkarm-none-eabi-gcc -z max-page-size=1 -o "UserApp.elf" @...

fronders · 2024-03-11

@Mahmoud Ben Romdhane I still get this on CubeMX v6.10.0 with CubeG0 v1.6.2 this time with another project. The library search path had a ".." path which was removed. I normally add this path so I can include some extra linker files located at the ro...

fronders · 2024-02-19

@to everyone already subbed: i'm sorry :) @Tom_pm in fact you can, see the screenshot below. But keep in mind then you'd get notified about all the comments made. Just like I got one with yours :)

fronders · 2024-01-23

Hello @Rim LANDOLSI,this issue seems to be addressed in CubeIDE v1.14.1 patch and that indeed fixed the $PWD being empty and mv spitting out "Result too large" error. However, after updating to v1.14.1 the mv command keeps failing but with a differen...

fronders · 2023-12-04

@Peter BENSCH Hi :)I too have a similar problem with pre-build & post-build scripts, on Windows 10 x64 with the latest BusyBox v1.31.0.st_20231030-1215 & included make tools with CubeIDE v1.14.0 (plugin com.st.stm32cube.ide.mcu.externaltools.make.win...

fronders · 2023-07-27

Sorry, missed the message.I have a Windows 10 Pro 22H2 x64 machine running build 19045.3208 when I install CubeCLT it erases the PATH variable after a successful install, so after it only CLT entries are present. This happened to me twice so far (as ...

User statistics

User Activity

[BUG] CubeMX removes linker library search path on code regeneration

[BUG] Install of STM32CubeCLT has wiped my system PATH on Windows 10

SECoreBin postbuild script incorrectly updates PATH

[BUG] STM32CubeProgrammer v2.10.0 outputs a bunch of pop-up messages in automatic mode

[BUG] X-CUBE-SBSFU linker error with GNU Tools for STM32 (10.3-2021.10)

Re: [BUG] CubeMX removes linker library search path on code regeneration

Re: STM32 Technical Updates are back : 2024 Newsletter 1 !

Re: $PWD returns an empty string when called from STMCubeIDE 1.14.0

Re: $PWD returns an empty string when called from STMCubeIDE 1.14.0

Re: [BUG] Install of STM32CubeCLT has wiped my system PATH on Windows 10