Can't flash STM32H735IG discovery kit using S32CubeIDE

[Elimathew72]

Hello all,

We are trying to evaluate the STM32H735IG for our product. We bought the off-the-shelf dev kit and tried flashing it using S32CubeIDE, but encountered an error. The weird thing is, I can use S32 programmer to read flash, so the ST-Link seems to be up-to-date. I feel there is something wrong with S32CubeIDE. Can you please help.

All the versions are below and also some screenshots to assist help debugging

STM32CubeIDE

Version: 1.14.0
Build: 19471_20231121_1200 (UTC)
OS: Linux, v.6.5.0-27-generic, x86_64 / gtk 3.24.33
Java vendor: Eclipse Adoptium
Java runtime version: 17.0.8.1+1
Java version: 17.0.8.1

Logs in the error window

Error in final launch sequence:

Failed to execute MI command:
load /home/STM32CubeIDE/workspace_1.14.0/BSP/STM32CubeIDE/Debug/BSP.elf

Error message from debugger back end:
Load failed
Failed to execute MI command:
load /home/STM32CubeIDE/workspace_1.14.0/BSP/STM32CubeIDE/Debug/BSP.elf

Error message from debugger back end:
Load failed
Failed to execute MI command:
load /home/STM32CubeIDE/workspace_1.14.0/BSP/STM32CubeIDE/Debug/BSP.elf

Error message from debugger back end:
Load failed
Load failed

 

Logs in the console 

 

STMicroelectronics ST-LINK GDB server. Version 7.5.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

InitWhile : Enabled

 

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

Shutting down...

Exit.

 

 

 

[STTwo-32]

Hello @Elimathew72  and welcome to the ST Community :smiling_face_with_smiling_eyes:.

Could you try this using the last version of STM32CubeIDE (V 1.15.1).

Best Regards.

STTwo-32 

[Elimathew72]

Still the same. I upgraded Stlink to the latest version too  

STM32CubeIDE
Version: 1.15.1
Build: 21094_20240412_1041 (UTC)
OS: Linux, v.6.5.0-27-generic, x86_64 / gtk 3.24.33, WebKit 2.44.0
Java vendor: Eclipse Adoptium
Java runtime version: 17.0.8.1+1
Java version: 17.0.8.1

 

STMicroelectronics ST-LINK GDB server. Version 7.7.0

Copyright (c) 2024, 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

InitWhile : Enabled

 

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

Shutting down...

Exit.

 

[Elimathew72]

Can still erase via stm32cubeprogrammer attaching a screenshot

[LCE]

Working here...

As long as my source code uses the SMPS:

HAL_PWREx_ConfigSupply(PWR_DIRECT_SMPS_SUPPLY);

[Elimathew72]

Hello We are trying the flash the sample off the example called BSP which blinks led.I don't see why this would affect connecting to stlink. Also many folks have experienced this problem but there is not concrete solutions.

[Elimathew72]

Also tried @mattias norlander  solution in https://community.st.com/t5/stm32cubeide-mcus/how-can-i-remove-error-like-waiting-for-debugger-connection/td-p/250559 to include  debug configuration > Startup tab > Initialization commands > Add: monitor flash mass_erase in the startup script. The Mass erase is successful then it shuts down connection 

 

STMicroelectronics ST-LINK GDB server. Version 7.7.0

Copyright (c) 2024, 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

InitWhile : Enabled

 

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

-------------------------------------------------------------------

STM32CubeProgrammer v2.16.0

-------------------------------------------------------------------

 

 

 

Log output file: /tmp/STM32CubeProgrammer_5yyIDP.log

ST-LINK SN : 0037002A3137511433333639

ST-LINK FW : V3J15M6

Board : STM32H750B-DK

Voltage : 3.27V

SWD freq : 8000 KHz

Connect mode: Under Reset

Reset mode : Hardware reset

Device ID : 0x450

Revision ID : Rev V

Device name : STM32H7xx

Flash size : 128 KBytes

Start Address : 8000000

Device type : MCU

Device CPU : Cortex-M7

BL Version : 0x90

 

 

Mass erase ...

 

Mass erase successfully achieved

Shutting down...

Exit.

[Elimathew72]

The difference between  STM32F429I discovery kit and STM32H750B-DK discovery kit is the stlink. Former has STLINK-V2 and the latter has STLINK-V3. Folks it'll be really helpful if anyone can assist me.

[Elimathew72]

Attaching the full stlink server logs 

[Elimathew72]

Also tried it on MAC OS still the same any opinions @Rim LANDOLSI  , I saw your post https://community.st.com/t5/stm32cubeide-mcus/why-does-elf-load-fails-when-using-stm32cubeide/td-p/77016 

I see the gdbserver has the same error, also I am not modifying anything from the sample BSP example which comes out of the box.

[2.277] write(): <11> Tx: $E31#a9
[2.277] read(): <11> Rx: $vKill;a410#33
[2.277] handlePacket(): Hidden/Unsupported v-command 'vKill', see RSP for details
[2.277] write(): <11> Tx: $#00
[2.278] read(): <11> Rx: $k#6b