From c367a223c50fe4c2e89b787f6f4f8c25f316faba Mon Sep 17 00:00:00 2001
From: Gregory Nutt <gnutt@nuttx.org>
Date: Tue, 9 Jan 2018 07:20:39 -0600
Subject: [PATCH] Update README

---
 configs/flipnclick-pic32mz/README.txt | 29 ++++++++++++++++++++++-----
 configs/flipnclick-sam3x/README.txt   |  4 +++-
 2 files changed, 27 insertions(+), 6 deletions(-)

diff --git a/configs/flipnclick-pic32mz/README.txt b/configs/flipnclick-pic32mz/README.txt
index e4db15edd7..000cda2fcc 100644
--- a/configs/flipnclick-pic32mz/README.txt
+++ b/configs/flipnclick-pic32mz/README.txt
@@ -1,8 +1,10 @@
 configs/flipnclick-pic32mz README
 ===============================
 
-This README file discusses the port of NuttX to the Mikroe Flip&Click PIC32MZ
-board.  That board features the PIC32MZ2048EFH100 MCU.
+  This README file discusses the port of NuttX to the Mikroe Flip&Click
+  PIC32MZ board.  That board features the PIC32MZ2048EFH100 MCU.
+
+  Thanks to John Legg for contributing the Flip&Click PIC32MZ board!
 
 Contents
 ========
@@ -21,28 +23,45 @@ Port Status
   2018-01-07:  Added architecture support for the PIC32MZ2048EFH100 used on
     the Flip&Click PIC32MZ board.
   2018-01-08:  Created the basic board configuration for the Mikroe
-    Flip&Click PIC32MZ board.  No testing has yet been performed.  I need
-    understand how the memory map is set up when used with the mikroBootloader.
+    Flip&Click PIC32MZ board.  No testing has yet been performed.  At this
+    point, I have not even figured out how I am going to load and debug
+    new firmware.  I need understand how the memory map is set up when used
+    with the mikroBootloader.
 
 On Board Debug Support
 ======================
 
   There are several debug options:
 
-  1. Using the Aduino IDE (chipKIT core).  This is available on the USB-UART
+  1. Using the Arduino IDE (chipKIT core).  This is available on the USB-UART
      port between the C and D MikroBUS sockets.  Usage is described in the
      Flip&Click User Manual.
 
+     I don't think trying to use the Arduino IDE is a good option.
+
   2. Using the mikroC USB HID bootloader.  This is is available on the USB
      port between the A and B MikroBUS sockets.  Usage is described in the
      Flip&Click User Manual.
 
+     There is a simple application available at Mikroe that will allow you
+     to write .hex files via the USB HID bootloader.  However, in order to
+     use the bootloader, you will have to control the memory map so that the
+     downloaded code does not clobber the bootloader.
+
+     At this point, I have found no documentation describing how to build
+     the code outside of the Mikroe toolchain for use with the Mikroe
+     bootloader.
+
   3. There is an undocumented and unpopulated PICKit3 connector between the
      B and C mikroBUS sockets.
 
   4. There is an undocumented and unpopulated mikroProg connector between
      the A and D mikroBUS sockets.
 
+     Since 3) and 4) are undocumented, this would require some research and
+     would, most likely, clobber the USB HID bootloader (and possibly the
+     Arduino support as well).
+
 Creating Compatible NuttX HEX files
 ===================================
 
diff --git a/configs/flipnclick-sam3x/README.txt b/configs/flipnclick-sam3x/README.txt
index 2f3f8a5e84..38c319414f 100644
--- a/configs/flipnclick-sam3x/README.txt
+++ b/configs/flipnclick-sam3x/README.txt
@@ -2,10 +2,12 @@ README
 ======
 
   This README discusses issues unique to NuttX configurations for the
-  Mikroe Flip&Click STM32X board.  This board is an Arduino-Due work-alike
+  Mikroe Flip&Click SAM3X board.  This board is an Arduino-Due work-alike
   with four Mikroe Click bus interfaces.  Like the Arduino-Due, this board
   features the Atmel ATSAM3X8E MCU running at 84 MHz.
 
+  Thanks to John Legg for contributing the Flip&Click SAM3X board!
+
 Contents
 ========