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

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 ?

​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.

​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.

​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.

​Yes please check if this issue is occuring with other devices and let me know.

Reviewing the full thread, an idea came to my mind.

Fwdelete not completed with an error : "FUS_NOT_RUNNING" => This means the FUS is not active. This could be the case when the previous load of the RF stack was successful. In that case the wireless stack is active, not the FUS. To activate the FUS, you should issue a Fus get state command. and then try the fwdelete command again.

Hi, Remi.

We are tested one more chip with marking:

STM32WB55

RGV7

7B A7P 9R Y

PHL GQ 9 16

ARM 34

Its a same situation.

Our steps:

- we have a chip whith FUS 0.5.3

- we upgrade FUS to 1.0.1

- then upgrade FUS to 1.1.0

- then we load BLE stack light ver 1.6.0 - all ok. We can delete FW and reload FW.

- then we load BLE stack light ver 1.8.0 - process was ok, but now we can`t delete any FW and reload it (FUS or stack). But ESE bit now checked.

I can send you this chip to.

We are tested third chip with marking:

STM32WB55

RGV7

7B A7P 9R Y

PHL GQ 9 16

ARM 24

Its a same situation.

Our steps:

- we have a chip whith FUS 0.5.3

- we upgrade FUS to 1.0.1

- then upgrade FUS to 1.1.0

- then we immediately load last BLE stack light ver 1.8.0 - process was ok, but now we can`t delete any FW and reload it (FUS or stack). But ESE bit now checked.

Now we have 3 chips with which we can do nothing.

:)

We are tested fourth chip with marking:

this chip is 512kB flash

STM32WB55

REV6

7B A6G 9R Y

PHL GQ 9 44

ARM 31

FUS and stack we was load on correct addresses. 

Its a same situation.

Our steps:

- we have a chip whith FUS 0.5.3

- we upgrade FUS to 1.0.2

- then upgrade FUS to 1.1.0

- then we immediately load last BLE stack light ver 1.8.0 - process was ok, but now we can`t delete any FW and reload it (FUS or stack). But ESE bit now checked.

Now we have 4 chips with which we can do nothing.

And in all tooday tested chips after that steps

calling command:

STM32_Programmer_CLI.exe -c port=usb1 -r32 0x20030030 1

we have FUS version : 00000000.