I'm using the EFR32MG21A101F1024IM32 chip, but the download shows the error, can you show me how to solve this problem step by step, thanks.
Hi wang chaoqun,
A new version of Simplicity Commander has been released that contains the fix for using external Segger J-Link debug adapters. The new version is not yet included in Simplicity Studio, but this Knowledge Base Article describes how to download it and replace the internal Simplicity Studio version: https://www.silabs.com/community/software/simplicity-studio/knowledge-base.entry.html/2020/05/21/how_to_update_thesimplicitycommanderversioninc-UkQc
The Simplicity Studio release containing the updated version of commander should be made in a few weeks if you prefer to wait for it.
If you choose to update commander based on the KBA, please let me know if:
A. There are any issues following the procedure
B. It doesn't fix the problem when using the external Segger J-Link
If you choose to use WSTK, please perform a device recover following YK's suggestion.
Dear YK and Jim,
Thank you for your continue follow up, here is the problem,
once I connected the device, the MCU information can be read, but the "secure Element Status" CAN NOT be read(picture1), and
while I recovered the bricked device, the "secure Element Status" can be read, but the MCU information CAN NOT be read,(picture2), also it indicate to flash a signed image? what is the signed image? where can I get it?
Thanks again for your support!
am I flashing the wrong signed image?