After flashing an SB-format encrypted and signed file with the Secure Provisioning tool, debugging via MCU-Link is no longer possible.
when I use mcuexpress debug my code , error happended:
Can my this board recover to it's old state to use zhe debug function?
> So, can I use the Secure Provising tool to make a new lisence, to cmobine a new signed and encrypted sb format file to write to the chip?
Yes, Secure Provisioning tool is designed to provision chip, i.e. install secure assets (keys), build signed or encrypted application bootable image and install into the flash.
@liborukropec Thanks a lot. I have resolve my question。
I have another question :
As above picture, This erase operation has erased ful of the memory chip .
So, can I use the Secure Provising tool to make a new lisence, to cmobine a new signed and encrypted sb format file to write to the chip?
Hi,
if you configure ROM to execute only signed images and then you write application from VSCode (or other IDE) unsigned image, ROM refuses from running.
Also, if you advance the Life Cycle, then the debugger can be opened only via Debug Authentication (see documentation).
In case you did not advance life cycle (on the tool bar), you should be able to erase CMPA. Simplest should be using debug probe and on the Write tab use the "Erase whole chip..." button.
After power cycle you should be able to debug again.
Regards,
Libor