Index: README.md
===================================================================
diff -u
--- README.md	(revision 0)
+++ README.md	(revision e7305461f1339505ebab83a08130a55b564face8)
@@ -0,0 +1,84 @@
+# Instructions for Flasing the Development Board
+## Connecting to the Development Board Serial Console
+### In Linux:
+1. Open a terminal on the Linux VM and connect to the serial console.  
+    ```# sudo minicom -s ```
+2. Select ***Serial port setup*** and change the following settings:  
+(**note:** most likely the serial console will be connected on ttyUSB0, but it may not be)
+    ```
+    Serial Device: /dev/ttyUSB0
+    Hardware Flow Control: No
+    ```
+    (**note:** the default configuration (8N1) does not need to be changed)  
+3. Press *<Enter>* to save the setup changes, then press *<Esc>* to exit the menu.
+4. Press *<Enter>* and the prompt should appear.
+
+### In Windows (**requires PuTTY**):
+1. Start PuTTy.
+2. Change the ***Connectin type:*** to **Serial**.
+3. Enter the appropriate COM port in the ***Serial line*** field (e.g. COM1, COM2, etc).
+4. Change the ***Speed*** to **115200**.
+5. Under the ***Category:*** pane, select ***Serial*** under ***Connection***.
+6. Change ***Flow control*** to **None**.
+7. Clicked the ***Open*** button.
+
+## Flashing the Development Board
+1. Connect to the development board serial console (see above).
+2. Connect to the Recovery port on the development board.
+3. If the development board is not at the U-Boot prompt (i.e. "==>"), reset the board and immediately press any key.
+4. Put the developement board into fastboot mode:  
+    ```==> fastboot 0```
+### In Linux: 
+5. Open another terminal on the Linux VM and switch to root:  
+    ```# sudo su - ```
+6. Ensure the uuu executable is in the path:  
+    ```# export PATH=$PATH:<directory with uuu>```
+7. Flash the devleopment board:  
+    ```# sh ./install_linux_fw_uuu.sh```
+8. Go back to the terminal connected to the serial console and observe that the development board is being flashed.  
+At the completion of being flashed the development board will restart and should be at a login prompt.
+9. (*optional*) If the development board is showing a kernel panic in the serial console, flash the rootfs onto the development board.  
+(note: since the install_rootfs_uuu.sh is being run as root, edit the script and remove 'sudo' on the line running the uuu command)  
+Go back to the Linux VM terminal and run:  
+    ```# sh ./install_rootfs_uuu.sh```
+10. Disconnect the Recovery port.
+### In Windows (**requires Git Bash**):
+5. Open a Git Bash shell.
+6. Navigate to the directory with the image files, uuu.exe tool, and install scripts.
+7. Ensure the uuu.exe executable is in the path:  
+    ```# export PATH=$PATH:<directory with uuu.exe>```
+8.  Flash the devleopment board:  
+    ```# sh ./install_linux_fw_uuu_w.sh```
+9. Go back to the terminal connected to the serial console and observe that the development board is being flashed.  
+At the completion of being flashed the development board will restart and should be at a login prompt.
+10. (*optional*) If the development board is showing a kernel panic in the serial console, flash the rootfs onto the development board.  
+    ```# sh ./install_rootfs_uuu_w.sh```
+11. Disconnect the Recovery port.
+
+## Setup the Development Board Display
+1. Connect to the development board serial console (see above).
+2. If the development board is not at the U-Boot prompt (i.e. "==>"), reset the board and immediately press any key.
+3. Update the U-Boot environment variables:  
+    ```
+    ==> setenv overlays _ov_board_user-leds_ccimx8m-dvk.dtbo,_ov_som_mca-keypad_ccimx8m.dtbo
+    ==> setenv som_overlays _ov_som_wifi_ccimx8m.dtbo,_ov_som_bt_ccimx8m.dtbo
+    ```
+4. Verify the U-Boot environment variables have been set:  
+    ```==> printenv```
+5. Save the updated enivronment variables.  
+    ```==> saveenv```
+6. Boot the development board.  
+    ```==> boot```
+7. The development board should now boot and the leahi application should appear on the screen.
+
+## Connect the Development Board to the Network
+1. Connect to the development board serial console (see above).
+2. At the login prompt, Log in as **root**.
+3. Start the WiFi network:  
+    (**note:** yes, the SSID is intentionally spelled incorrectly below)  
+    ```# nmcli dev wifi connect DilaityIoT password "<password>"```
+4. Verify the WiFi is active, and interface wlan0 has an IP address:  
+    ```# ip a```
+5. Connect your development machine to the DilaityIoT network.  
+    Open a terminal on your Linux VM.  
+    ```# ssh root@<development board IP address from above>```