cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeIDE 1.14.1 released

Semer CHERNI
ST Employee

Hello,

Since the STM32CubeIDE 1.14.0 release, some issues was faced when executing shell script in the pre/post build command.

This issue was faced with the Windows version of the STM32CubeDE 1.14.0.

Therefore, a patch is now available on ST site which fix this problem.

KR,
Semer.

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.

4 REPLIES 4
vt23
Associate

Hello,

I updated to 1.14.1 (on Win10) and my Debug is messed up now - my ST-link V2 cannot start the session. Differences which I have found are that Debug script is very different (proj Debug.cfg) and also my named board (Target_board) from MCU Settings is now "genericBoard" (but I suppose that target board name does not matter in my case).

For example Debug.cfg contains:

 

source [find interface/stlink-dap.cfg]
set WORKAREASIZE 0x8000
transport select "dapdirect_swd"
set CHIPNAME STM32F412RGTx
set BOARDNAME genericBoard
# Enable debug when in low power modes
set ENABLE_LOW_POWER 1
# Stop Watchdog counters when halt
set STOP_WATCHDOG 1
# STlink Debug clock frequency
set CLOCK_FREQ 8000
# Reset configuration
# use hardware reset, connect under reset
# connect_assert_srst needed if low power mode application running (WFI...)
reset_config srst_only srst_nogate connect_assert_srst
set CONNECT_UNDER_RESET 1
set CORE_RESET 0
# ACCESS PORT NUMBER
set AP_NUM 0
# GDB PORT
set GDB_PORT 3333

 

instead of sooner used configuration (with 1.14.0)

 

source [find interface/stlink.cfg]
transport select "hla_swd"

This doesn't work now.

 

After many experiments with settings (or after restarting IDE) the Debug started working - but only using "ST-Link (GDB server)" setting.

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
        InitWhile                  : Enabled

"ST-Link (OpenOCD)" setting does not work now for me. Error appears there:

Error message from debugger back end:
Error erasing flash with vFlashErase packet
Failed to execute MI command:
load U:\\projFiles\\SWgit\\Prod_v03\\Prod_v03\\Debug\\Prod_v03.elf

I don't know why something has changed in the new version v1.14.1.

vt

dambo
Associate II

I have one question - which genius came up with the idea that you need to log in to download libraries in CubeIDE?

Simon Sq
Associate III

Hello,

 

I am still facing issues with post build script not working using STM32CubeIDE v1.14.1 under Windows 11. 

My post build step invokes a batch file in the project root folder, however even when this bat file does nothing the build will fail. I've attached a screen shot showing the error.

This post_build.bat file works fine on earlier versions of STM32CubeIDE (although I never tried on v1.14.0) - but I have an earlier version on my work laptop and that works without issue.

Is there any solution?

Thanks,

Simon

I have exactly the same problem.
Post build batch file working on pre 1.14.0, not working on 1.14.1
Any clues as to what was changed in 1.14.0 and 1.14.1?

*** update ***
I resolved my issue by enclosing my batch command in double-quotation marks.
It seems the post-build command is now intolerant of spaces in the project path.