I seem to have either destroyed or bricked the MCU on the EFM8SB2 development board. It is identified when I plug it in but I can't upload code to it.
The energy profiler still works and the debugger seems to respond. Is it possible that the MCU is just bricked and it could be revived? If so, how would I do that?
These dev boards are out of stock at DigiKey.
Thanks in advance,
how about the current the SB2 consume when the issue happen.
I guess you mean the EFM8SB2 STK by 'development board'.
what error you see?
The board is the EFM8SB2-SLSTK2011A.
It is drawing a constant 2 mA with the switch on AEM. If I switch it to BAT it shows noise < 100 nA.
When I try to start a project, it gets stuck at a dialog box "Copying C:\......hex to J-Link Silicon Labs(nnn)
Than a J-Link error message appears "Communication timed out: Requested 4 bytes, received 0 bytes!
When I click OK another message appears "Multiple problems have occurred." There are two lines Launching.... and Uploading. Clicking on either of these gives the message "Unknown error code."
Have you tried other projects and have you tried running the project in debug mode? Are you able to erase the device? If the device is bricked somehow(i.e. stuck in low energy mode), then there is not really a way to unbrick it since the device recover feature in Simplicity Commander does not support EFM8 devices. In general with EFM8 devices you want to implement a device trap function at the beginning of your main application as shown in this knowledge based article: https://www.silabs.com/community/mcu/8-bit/knowledge-base.entry.html/2015/08/20/_bricking_an_8-bit-54nh. Another knowledge based article that might be helpful is: https://www.silabs.com/community/mcu/32-bit/knowledge-base.entry.html/2014/05/14/recover_efm32_orefm-BNRV
I was able to buy another one. I was wasting too much time on it.
I am still using the non-working board with the energy profiler, which is useful.