STM32CubeProgrammer STM32G474 option bytes / IWDG

[FWege.1]

Dear all

If we clear the IWDG option (enable watchdog by hardware at bootup), we cannot undo this.

In that case we have to use the old STM32 ST-LINK Utility tool.

STM32CubeProgrammer version: v2.11.0

µC: STM32G474RBT3

The problem seems to be PC dependent!

Thanks in advance,

Franz

[Houda GHABRI]

Hi @FWege.1​ ,

I'm not able to reproduce the issue, can you please tell me more about your PC configuration where this issue occurs?

C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer-2.11.0-RC4\bin>STM32_Programmer_CLI.exe -c port=SWD -ob IWDG_SW=1

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

            STM32CubeProgrammer v2.11.0-RC4

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

ST-LINK SN : 001900303137510839383538

ST-LINK FW : V3J9M3

Board    : STM32G474E-EVAL

Voltage   : 3.28V

SWD freq  : 24000 KHz

Connect mode: Normal

Reset mode : Software reset

Device ID  : 0x469

Revision ID : Rev B

Device name : STM32G47x/G48x

Flash size : 512 KBytes

Device type : MCU

Device CPU : Cortex-M4

BL Version : --

  

UPLOADING OPTION BYTES DATA ...

 Bank     : 0x00

 Address    : 0x40022020

 Size     : 20 Bytes

██████████████████████████████████████████████████ 100%

 Bank     : 0x01

 Address    : 0x40022044

 Size     : 16 Bytes

██████████████████████████████████████████████████ 100%

 Bank     : 0x02

 Address    : 0x40022070

 Size     : 8 Bytes

██████████████████████████████████████████████████ 100%

OPTION BYTE PROGRAMMING VERIFICATION:

Option Bytes successfully programmed

Time elapsed during option Bytes configuration: 00:00:01.173

Houda

[Piranha]

Connect mode: Under Reset

Reset mode : Hardware reset

[FWege.1]

Hello together

First thanks for your answers.

The problem occurs sporadically - mostly on the Windows 7 systems.

 Betriebssystemname   Microsoft Windows 7 Professional

Version 6.1.7601 Service Pack 1 Build 7601

Systemtyp         x64-basierter PC

Maybe it has something to do with the watchdog – I’m not sure. How is the watchdog handled during programming/flashing?

The only difference in the logfiles is following line – which occurs on my windows 10 system, if everything works as expected

 16:27:13:483 : WriteOB function terminated with connection error due to OB_Launch

Thanks Piranha – but unfortunately that doesn't help