STM32CubeProgrammer v2.16 cannot program option bytes

[etamarin]

I am running into an issue with the latest release of the STM32CubeProgrammer.

It seems that, at least for STM32F030 MCUs, it is unable to program option bytes. A similar error has been reported earlier (see this topic).

The same error is present when I use STM32CubePorgrammer CLI, version 2.15.

If I downgrade to version 2.10, the error goes away and I am able to program option bytes normally.

[Amine_Jridi]

Hello @etamarin,

It's working fine on my end. Could you please specify which option bytes you're attempting to program and provide the error logs you've received?

Thanks,

Amine.

[etamarin]

Hi Amine,

This is what I get when using STM32 Programmer CLI, v2.15

PS > STM32_Programmer_CLI.exe -c port=swd -ob nwrp0=0 -vb 3
      -------------------------------------------------------------------
                       STM32CubeProgrammer v2.15.0
      -------------------------------------------------------------------

ST-LINK SN  : 0030001A3133510A36303739
ST-LINK FW  : V3J15M6B5S1
Board       : STLINK-V3SET
Voltage     : 0.00V
SWD freq    : 8000 KHz
Connect mode: Normal
Reset mode  : Software reset
Device ID   : 0x440
Revision ID : Rev 2.0
flash loader C:/ST/STM32CubeCLT/STM32CubeProgrammer/bin/FlashLoader/0x440.stldr is loaded
Device name : STM32F05x/F030x8
Reading data...
r ap 0 @0x1FFFF7CC 0x00000004 bytes Data 0xFFFF0040
Flash size  : 64 KBytes
Device type : MCU
Device CPU  : Cortex-M0
BL Version  : 0x21


UPLOADING OPTION BYTES DATA ...

  Bank          : 0x00
  Address       : 0x1ffff800
  Size          : 16 Bytes

Reading data...
r ap 0 @0x1FFFF800 0x00000010 bytes Data 0x00FF55AA



PROGRAMMING OPTION BYTES AREA ...
Warning: Option Byte: nwrp0, does not exist

Warning: Option Bytes are unchanged, Data won't be downloaded
Time elapsed during option Bytes configuration: 00:00:00.001
Disconnected

View more

The "Option Byte does not exist" happens every time I try to interact with the option bytes at all, so for example

STM32_Programmer_CLI.exe -c port=swd -rdu

will fail with the same error.

We are also seeing this on our production line where we've had to roll back to an earlier version of the programmer software. For reference, this is what we are using:

• MCU: STM32F030
• Programmer: STLINK-V3SET with firmware V3J15M6B5S1

[Amine_Jridi]

Hello @etamarin,

Thank you for providing the logs. It seems the issue occurs specifically when trying to configure the write protection section of the OB. I've submitted an internal ticket to our development team for further investigation.

Internal ticket number: 182322 (This is an internal tracking number and is not accessible or usable by customers)

I will keep you updated on any progress.

Thanks,

Amine.

[etamarin]

Hi Amine,

Is there any update from the development team on this issue? We have also encountered this in the MacOS version of the programmer (2.16), so we are hoping for a fix as this is starting to impact our operations.

Thanks in advance!

[Amine_Jridi]

Hello @etamarin 

This issue will be fixed in a future release of the Programmer software.

Thanks,

Amine.