Updated Flashing SiLabs based M3 Newton Displays (markdown)

Flashing-SiLabs-based-M3-Newton-Displays.md

@@ -37,8 +37,6 @@ Of course Silicon Labs [Simplicity Studio](https://www.silabs.com/developers/sim
 >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.  
@@ -91,6 +89,30 @@ Unlocking is best done using Simplicity Commander (works with any J-Link based p
 Use 'unlock debug access' in the 'flash' tab in the GUI, or issue the command
 `commander device unlock`.
 
+## User Data
+
+The *user data* portion of flash contains tag configuration information that is used by the universal software to determine how to drive the display.  
+If the doesn't work the contents of the *user data* is needed to add support.  For this reason it is recommended that *user data* be read and saved when a new tag is flashed.
+
+This script can be used on Linux to automate the complete flashing process for a fresh tag, including dumping the *user data*.
+
+```bash
+#!/bin/bash
+
+log=flash.log
+device=EFR32BG22C222F352GM40
+commander=~/.local/bin/commander/commander
+version=41
+image=full_binaries/v${version}/SOLUM_AUTODETECT_FULL_v${version}.s37
+
+echo "----" >> ${log}
+${commander} device unlock -d ${device} 2>&1 | tee -a ${log}
+${commander} device info -d ${device} 2>&1 | tee -a ${log}
+${commander} readmem -d ${device} --region "@userdata" 2>&1 | tee -a ${log}
+${commander} flash -d ${device} ${image} 2>&1 | tee -a ${log}
+
+```
+
 ## Universal M2/M3 Pad Layout for ZBS/nRF/EFR32  
 
 | ZBS2 | nRF | EFR32 |  Note |