STM32CubeProgrammer, STM32G031K8 option bytes problem

[pawcuq]

Hello,

I have NUCLEO-G031K8 and want to change nBOOT0 using STM32CubeProgrammer (v2.12.0) but I'm unable to do so.

I get four message boxes from STM32CubeProgrammer:

• "Warning: Option Byte: nSwap_BANK, does not exist",
• "Warning: Option Byte: DUAL_BANK, does not exist",
• "Warning: option Byte: DUAL_BANK, is not programmable",
• "Option Bytes successfully programmed".
•  

Even though the fourth message box says that option bytes were successfully programmed - nBOOT0 value is unchanged.

Here's log from STM32CubeProgrammer:

  09:41:13 : Option byte command : -ob  DUAL_BANK=1  nSWAP_BANK=1  IRHEN=1  nBOOT1=1  nBOOT_SEL=1  RAM_PARITY_CHECK=1  WWDG_SW=1  IWDG_STDBY=1  IWDG_STOP=1  IWDG_SW=1  nRST_SHDW=1  nBOOT0=1 
  09:41:13 : PROGRAMMING OPTION BYTES AREA ...
  09:41:13 : Warning: Option Byte: DUAL_BANK, is not programmable
  09:41:13 : Warning: Option Byte: DUAL_BANK, does not exist
  09:41:13 : Warning: Option Byte: nSWAP_BANK, does not exist
  09:41:13 :   Bank          : 0x00
  09:41:13 :   Address       : 0x40022020
  09:41:13 :   Size          : 108 Bytes
  09:41:13 : Reconnecting...
  09:41:14 : Reconnected !
  09:41:14 : UPLOADING OPTION BYTES DATA ...
  09:41:14 :   Bank          : 0x00
  09:41:14 :   Address       : 0x40022020
  09:41:14 :   Size          : 108 Bytes
  09:41:14 :   Bank          : 0x01
  09:41:14 :   Address       : 0x40022080
  09:41:14 :   Size          : 4 Bytes
  09:41:14 : OPTION BYTE PROGRAMMING VERIFICATION:
  09:41:14 : Option Bytes successfully programmed
  09:41:14 : Time elapsed during option Bytes configuration: 00:00:01.199

What's strange I can change nBOOT0 using old, depreciated STM32 ST-LINK Utility (v.4.6.0).

Does anyone have a clue what I'm doing wrong?

Thanks!

[Aziz BRIGUI · Accepted solution]

Hello @Community member​,

Thank you for posting,

You are doing nothing wrong, this is a bug in the latest release of STM32CubeProgrammer and is internally reported.

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

I apologize for the inconvenience. While programming your STM32G031 option bytes, I suggest using CLI or STM32CubeProgrammer v2.11.0.

Aziz

[Houda GHABRI]

Hi @Community member​ ,

As said by @Aziz BRIGUI​ this issue is already raised and will be fixed in next CubeProgrammer release.

Meanwhile you can use the CLI, it works fine or 2.11.0 version.

Hope this helps you.

Houda

[pawcuq]

@Aziz BRIGUI​ @Houda GHABRI​ - thank you for quick and solid answer, I tried previous STM32CubeProgrammer version (v2.11.0) and everything works as expected 🙂

PS Is there any document in public which lists/describes known bugs in STM32CubeProgrammer?

[Aziz BRIGUI]

For known limitations, you can check the release notes for STM32CubeProgrammer available under this link. However since this bug is new, you won't be able to find it in that document.

I hope this helps,

Aziz

[pawcuq]

Thank you - that's exactly what I was looking for 🙂

[Aziz BRIGUI]

Hello @Community member​,

Issue is resolved in latest STM32CubeProgrammer version (v2.13.0) available under this link.

Aziz

[pawcuq]

Thanks 🙂 I'll check that out.