Dear YK,

yes, I can recover the device, but after cover, it is no more secure element status, check the picture below, and What is the signed image?

Is the signed image "railtest_efr32mg21a010f1024im32.s37" or "bootloader-storage-spiflash-single.s37" or something else?

am I flashing the wrong signed image?

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!

pitcure1

picture 2

Dear Jim and YK,

now I can recover the bricked device, but when configer the security setting, it shows DCI commander failed, how to solve this, thanks again!

Dear Engineer,

I'm facing the similar problem, my board is BRD4001, I want this board to connect EFR32MG21A101F1024IM32 for debug, can you show me how to update the firmware? or this problem can't be solved so far?

Thanks

Wang

Thank you YK, 

I connetced EFR32MG21 with BRD4001A board, the SWDIO, SWCLK, SWO, RESET are connected, but still shows error "DP Write Failed"

Below is the Jlink I'm using, I can download and debug EFR32MG13 serials with this jlink, but problems come when down load EFR32MG21 serials.

Dear Engineer,

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,

Thank you for raising this issue. The wrong Profile ID is an known issue that we have been working on fixing. Currently, you can create a ZigBee Custom device type in the Appbuilder for the ZLL profile to workaround this issue.