diff --git a/Flashing-SiLabs-based-M3-Newton-Displays.md b/Flashing-SiLabs-based-M3-Newton-Displays.md index 64a35df..de734c3 100644 --- a/Flashing-SiLabs-based-M3-Newton-Displays.md +++ b/Flashing-SiLabs-based-M3-Newton-Displays.md @@ -26,6 +26,19 @@ reality they are ST-Link clones and will thus only work with ST parts. If you feel confident that you've found an actual J-Link clone and want to give that a shot, feel free to report back with your experience. +## Software for flashing + +- [Simplicity Commander](https://www.silabs.com/developers/simplicity-studio/simplicity-commander) +- [JFlash](https://www.segger.com/products/debug-probes/j-link/technology/flash-download/) + +Of course Silicon Labs [Simplicity Studio](https://www.silabs.com/developers/simplicity-studio) or Segger's [Ozone](https://www.segger.com/products/development-tools/ozone-j-link-debugger/) debugger can also be used to flash tags. + +>[!Note] +>Neither Simplicity Studio nor Ozone are lightweight installs. Only install them if you are planning on doing development. + + + + ## Debugger connections The programming test point layout on M3 Displays are the same for ZBS, NRF and EFR32xG22 based displays so the same you can 3D print a universal pogo pin jig. @@ -49,8 +62,6 @@ Pinout connections for Silicon Labs debugger, see sections [2.3.2/2.3.3 in the u image - - ## Connections for Segger J-Link with 20 Pin Header image @@ -65,4 +76,17 @@ Pinout connections for Silicon Labs debugger, see sections [2.3.2/2.3.3 in the u |SWDCLK | 9| Blue | |nRESET | 15 | Green | +## Debug-locked devices + +Some EFR32xG22 devices are debug-locked by their manufacturer to prevent unauthorised +reading of their (trade secret) firmware. As long as 'unauthenticated debug unlock' is +not disabled on the chip, it is possible to unlock the chip for reflashing. The side- +effect of this is that the original firmware is erased before gaining access to the +chip (as this function intended). + +Unlocking is best done using Simplicity Commander (works with any J-Link based probe). +Use 'unlock debug access' in the 'flash' tab in the GUI, or issue the command +`commander device unlock`. + +