STM342WB55 after load last BLE stack (1.8.0) I can`t erase fw with STM32CubeProgrammer

[Vyacheslav]

Hi.

Using STM32CubeProgrammer I load last stm32wb5x_BLE_Stack_light_fw.bin, but when after that I try to run command -fwdelete, I get an error : "FUS_NOT_RUNNING".

I attach log file becose Idont understand whot is this.

But me application work fine and I see that stack is a last version.

Please help whot may bee .

I send call:

STM32_Programmer_CLI.exe -c port=usb1 -fwdelete -vb 3

[Vyacheslav]

Hi, Remi.

Yes, my custom application and bootloader uses BLE stack and no any problems.

Application and bootloader can advertise and connect, transfer any data by custom characteristics.

How ti correct write data to address ?

I use:

STM32_Programmer_CLI.exe -c port=usb1 -w32 0x5800040C 0x00008000

but get error:

[Remi QUINTIN]

​Could you download all the sections of the options bytes or call the command STM32_Programmer_CLI.exe -c port=usb1 -ob displ and give me the log?

[Vyacheslav]

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

            STM32CubeProgrammer v2.5.0          

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

USB speed  : Full Speed (12MBit/s)

Manuf. ID  : STMicroelectronics

Product ID : DFU in FS Mode

SN     : 2058387A3036

FW version : 0x011a

Device ID  : 0x0495

Device name : STM32WBxx

Flash size : 1 MBytes

Device type : MCU

Device CPU : Cortex-M0+/M4

UPLOADING OPTION BYTES DATA ...

 Bank     : 0x00

 Address    : 0x1fff8000

 Size     : 128 Bytes

▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 0%

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

OPTION BYTES BANK: 0

  Read Out Protection:

   RDP     : 0xAA (Level 0, no protection) 

  BOR Level:

   BOR_LEV   : 0x0 (BOR Level 0 reset level threshold is around 1.7 V) 

  User Configuration:

   nBOOT0    : 0x1 (nBOOT0=1 Boot from main Flash) 

   nBOOT1    : 0x1 (Boot from Flash if nBoot0=0 otherwise system memory) 

   nSWBOOT0   : 0x1 (BOOT0 taken from PH3/BOOT0 pin) 

   SRAM2RST   : 0x1 (SRAM2 is not erased when a system reset occurs) 

   SRAM2PE   : 0x1 (SRAM2 parity check disable) 

   nRST_STOP  : 0x1 (No reset generated when entering the Stop mode) 

   nRST_STDBY  : 0x1 (No reset generated when entering the Standby mode) 

   nRSTSHDW   : 0x1 (No reset generated when entering the Shutdown mode) 

   WWDGSW    : 0x1 (Software window watchdog) 

   IWGDSTDBY  : 0x1 (Independent watchdog counter running in Standby mode) 

   IWDGSTOP   : 0x1 (Independent watchdog counter running in Stop mode) 

   IWDGSW    : 0x1 (Software independent watchdog) 

   IPCCDBA   : 0x0 (0x0) 

  Security Configuration Option bytes:

   ESE     : 0x0 (Security disabled) 

   SFSA     : 0xD6 (0xD6) 

   FSD     : 0x0 (System and Flash secure) 

   DDS     : 0x1 (CPU2 debug access disabled) 

   C2OPT    : 0x1 (SBRV will address Flash) 

   NBRSD    : 0x0 (SRAM2b is secure) 

   SNBRSA    : 0xF (0xF) 

   BRSD     : 0x0 (SRAM2a is secure) 

   SBRSA    : 0xA (0xA) 

   SBRV     : 0x35800 (0x35800) 

  PCROP Protection:

   PCROP1A_STRT : 0x1FF (0x80FF800) 

   PCROP1A_END : 0x0 (0x8000800) 

   PCROP_RDP  : 0x0 (PCROP zone is kept when RDP is decreased) 

   PCROP1B_STRT : 0x1FF (0x80FF800) 

   PCROP1B_END : 0x0 (0x8000800) 

  Write Protection:

   WRP1A_STRT  : 0xFF (0x80FF000) 

   WRP1A_END  : 0x0 (0x8000000) 

   WRP1B_STRT  : 0xFF (0x80FF000) 

   WRP1B_END  : 0x0 (0x8000000) 

[Vyacheslav]

Remi, tell me please, we have a many chips WB55 with REV6.

Our chips marking:

ST (e3)

STM32WB55

REV6

7B A6G 9R Y

PHL GQ 945

ARM 31

It is a normal chip ? (we haven't used it yet)

And what a last revision of chip ?

[Remi QUINTIN]

​Ok nothing wrong regarding the option bytes except this puzzling ESE set to 0.

Regarding the marking, I would be interested in the one on the failed chip.

I'll come back to you with information on the one above.

[Vyacheslav]

Marking of failed chip:

STM32WB55

RGV6U

78 A4L 9R Y

PHL 3R 8 44

ARM 64

[Remi QUINTIN]

​Both markings show valid secured devices.

So I would consider this failed part as not usable anymore.

Could you send this chip back to us? We will perform further analysis.

[Vyacheslav]

Hi, Remi.

This chip is sealed from the nucleo board and soldered to our custom board.

I can unsolder it, but tell me where to send it? Please write the complete address for sending it.

Thanks.

[Remi QUINTIN]

​Remi QUINTIN

STMicroelectronics Grenoble2 SAS

12 Rue Jules Horowitz 38019 Grenoble FRANCE

We can send you a STM32WB55 Nucleo pack as an exchange if you want.

[Vyacheslav]

Ok, thanks, Remi.

On Monday I will do the same research with other chips.

Maybe it will be the same with them.

Then I'll send you the problem chip.