WL55 Option Byte Programming Failed

[ZSvet.1]

Dear Community,

I have exhausted all possibilities to find the reason to successfully configure Option Bytes on STM32WL55.
With the process I am using CubeProgrammer v2.13 and I can say that
for STM32WLE5 the programming of OB was successful every-time!

The things that I have checked and tested for STM32WL55:
- tried on different 15 devices (same model)
- lowered the MSI to 4000000Hz (erratum workaround)
- used unlock-chip in the CubeProg
- tried different ST-Link frequencies
- have upgraded ST-Link (V2J40M27)

The only OB that I can program is the BOR Level.

1. Do you have any idea or advice what should I do?

13:06:48 : STM32CubeProgrammer API v2.13.0 | Linux-64Bits
13:07:07 : Start STLinkUpgrade...
13:07:21 : UR connection mode is defined with the HWrst reset mode
13:07:21 : ST-LINK SN : 0670FF485550755187043646
13:07:21 : ST-LINK FW : V2J40M27
13:07:21 : Board : NUCLEO-F401RE
13:07:21 : Voltage : 0,01V
13:07:21 : SWD freq : 4000 KHz
13:07:21 : Connect mode: Under Reset
13:07:21 : Reset mode : Hardware reset
13:07:21 : Device ID : 0x497
13:07:21 : Revision ID : Rev Z
13:07:21 : Debug in Low Power mode is not supported for this device.
13:07:21 : UPLOADING OPTION BYTES DATA ...
13:07:21 : Bank : 0x00
13:07:21 : Address : 0x58004020
13:07:21 : Size : 96 Bytes
13:07:21 : Bank : 0x01
13:07:21 : Address : 0x58004080
13:07:21 : Size : 8 Bytes
13:07:21 : UPLOADING ...
13:07:21 : Size : 1024 Bytes
13:07:21 : Address : 0x8000000
13:07:21 : Read progress:
13:07:21 : Data read successfully
13:07:21 : Time elapsed during the read operation is: 00:00:00.007
13:07:29 : Option byte command : -ob BOR_LEV=3
13:07:29 : PROGRAMMING OPTION BYTES AREA ...
13:07:29 : Bank : 0x00
13:07:29 : Address : 0x58004020
13:07:29 : Size : 96 Bytes
13:07:29 : Reconnecting...
13:07:30 : Reconnected !
13:07:31 : UPLOADING OPTION BYTES DATA ...
13:07:31 : Bank : 0x00
13:07:31 : Address : 0x58004020
13:07:31 : Size : 96 Bytes
13:07:31 : Bank : 0x01
13:07:31 : Address : 0x58004080
13:07:31 : Size : 8 Bytes
13:07:31 : OPTION BYTE PROGRAMMING VERIFICATION:
13:07:31 : Option Bytes successfully programmed
13:07:31 : Time elapsed during option Bytes configuration: 00:00:01.201
13:07:45 : Option byte command : -ob nBOOT1=0 nSWBOOT0=0
13:07:45 : PROGRAMMING OPTION BYTES AREA ...
13:07:45 : Bank : 0x00
13:07:45 : Address : 0x58004020
13:07:45 : Size : 96 Bytes
13:07:45 : Reconnecting...
13:07:46 : Reconnected !
13:07:46 : UPLOADING OPTION BYTES DATA ...
13:07:46 : Bank : 0x00
13:07:46 : Address : 0x58004020
13:07:46 : Size : 96 Bytes
13:07:46 : Bank : 0x01
13:07:46 : Address : 0x58004080
13:07:46 : Size : 8 Bytes
13:07:46 : OPTION BYTE PROGRAMMING VERIFICATION:
13:07:46 : Error: Expected value for Option Byte "nBOOT1": 0x0, found: 0x1
13:07:46 : Error: Expected value for Option Byte "nSWBOOT0": 0x0, found: 0x1
13:07:46 : Error: Option Byte Programming failed
13:07:46 : Time elapsed during option Bytes configuration: 00:00:01.201

Thanks in advance for your answers,

BR Ziga

[IIRHO.1]

Hello @ZSvet.1 and welcome to ST Community.

I reproduced the same behavior using ST-LINK FW : V3J10M3 and it works if I just put the option byte nBOOT0 to 0 before putting nBOOT1 and nSWBOOT0 to 0. Also, I suggest you to verify the Board that u are using and the voltage.  After the data you have provided, I think there is a problem in this two parameters as you can see in this capture.

I hope this is helpful for you.

Issam.

[ZSvet.1]

Dear Issam,

Thanks you for your investigation.
Did you checked both MCUs?

You are correct to verify board,
but I am using cut-off ST-Link from F401RE board connected to own STM32WLxx PCB
(Outage of ST-LINKs in the past, so the need - produced that :) ).
Wiring and target voltage should be OK, considering everything is working normally on STM32WLE5:
- flashing
- debugging
- OptionByte programming 100%
Only with the STM32WL55 I have problems to program most of the option-bytes.

With other development machines, where I am using ST factory ST-LINKv2(latest FW)
I am facing the same symptoms with STM32WL55 not capable of programming some OBs.
(Have done double checking before asked here....)

As it seems your configuration is using ST-LINKv3 HW ... maybe that would be the trick.
Will order a few v3 ST-LINKs to try out.

Thanks a lot.

Ziga

[IIRHO.1]

Hello again and thanks for your replay. 

If your question is answered, please close this topic by choosing "Accept as Solution". This will help other users find that answer faster.

Issam