Minor update to Shenzhou README files

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5119 42af7a65-404d-4744-a932-0658087f49c3

10 files changed, 162 insertions, 256 deletions

diff --git a/nuttx/configs/ea3131/tools/usb-driver.txt b/nuttx/configs/ea3131/tools/usb-driver.txt
index 2a649dfb8..83d7598a5 100644
--- a/nuttx/configs/ea3131/tools/usb-driver.txt
+++ b/nuttx/configs/ea3131/tools/usb-driver.txt
@@ -2,15 +2,24 @@ https://www.olimex.com/dev/pdf/ARM/JTAG/Repair%20Procedure%20for%20OpenOcd-Rev.%
 
 Repair procedure for ARM-USB-OCD drivers
 
-1. Uninstalling ARM-USB-OCD drivers.
-1.1. Connect your programmer/debugger to your computer, open Device Manager and uninstall the drivers for ARM-USB-OCD.
-1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager, disconnect the programmer from your computer.
-1.3. Now you should download FTClean.exe from here: http://www.ftdichip.com/Support/Utilities/FTClean.zip.
-1.4. After download is complete extract the “*.zip” file, open folder FTClean,  and run FTClean.exe
-1.5. Ror VID (Hex) select “Other”. And after that fill the first box with 15ba and “PID (Hex)” with 0004.
-1.6. Press “Clean System” button.  Make sure that all FTDI devices are disconnected. (My require administrator privileges).
+1.   Uninstalling ARM-USB-OCD drivers
+-------------------------------------
+1.1. Connect your programmer/debugger to your computer, open Device Manager
+     and uninstall the drivers for ARM-USB-OCD.
+1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager,
+     disconnect the programmer from your computer.
+1.3. Now you should download FTClean.exe from here:
+     http://www.ftdichip.com/Support/Utilities/FTClean.zip.
+1.4. After download is complete extract the "*.zip" file, open folder FTClean,
+     and run FTClean.exe
+1.5. Ror VID (Hex) select "Other". And after that fill the first box with 15ba
+     and "PID (Hex)" with 0004.
+1.6. Press "Clean System" button.  Make sure that all FTDI devices are
+     disconnected. (My require administrator privileges).
 
-2. Re-install ARM-USB-OCD driver
+2. Re-installing the ARM-USB-OCD driver
+---------------------------------------
 2.1 Connect the programmer/debugger to the computer.
-2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER directory and install.
-
+2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER
+    directory and install. (A different driver is required for OpenOCD
+    0.4.0.  That driver is available from the olimex.com web site).
diff --git a/nuttx/configs/ea3152/tools/usb-driver.txt b/nuttx/configs/ea3152/tools/usb-driver.txt
index 2a649dfb8..83d7598a5 100644
--- a/nuttx/configs/ea3152/tools/usb-driver.txt
+++ b/nuttx/configs/ea3152/tools/usb-driver.txt
@@ -2,15 +2,24 @@ https://www.olimex.com/dev/pdf/ARM/JTAG/Repair%20Procedure%20for%20OpenOcd-Rev.%
 
 Repair procedure for ARM-USB-OCD drivers
 
-1. Uninstalling ARM-USB-OCD drivers.
-1.1. Connect your programmer/debugger to your computer, open Device Manager and uninstall the drivers for ARM-USB-OCD.
-1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager, disconnect the programmer from your computer.
-1.3. Now you should download FTClean.exe from here: http://www.ftdichip.com/Support/Utilities/FTClean.zip.
-1.4. After download is complete extract the “*.zip” file, open folder FTClean,  and run FTClean.exe
-1.5. Ror VID (Hex) select “Other”. And after that fill the first box with 15ba and “PID (Hex)” with 0004.
-1.6. Press “Clean System” button.  Make sure that all FTDI devices are disconnected. (My require administrator privileges).
+1.   Uninstalling ARM-USB-OCD drivers
+-------------------------------------
+1.1. Connect your programmer/debugger to your computer, open Device Manager
+     and uninstall the drivers for ARM-USB-OCD.
+1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager,
+     disconnect the programmer from your computer.
+1.3. Now you should download FTClean.exe from here:
+     http://www.ftdichip.com/Support/Utilities/FTClean.zip.
+1.4. After download is complete extract the "*.zip" file, open folder FTClean,
+     and run FTClean.exe
+1.5. Ror VID (Hex) select "Other". And after that fill the first box with 15ba
+     and "PID (Hex)" with 0004.
+1.6. Press "Clean System" button.  Make sure that all FTDI devices are
+     disconnected. (My require administrator privileges).
 
-2. Re-install ARM-USB-OCD driver
+2. Re-installing the ARM-USB-OCD driver
+---------------------------------------
 2.1 Connect the programmer/debugger to the computer.
-2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER directory and install.
-
+2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER
+    directory and install. (A different driver is required for OpenOCD
+    0.4.0.  That driver is available from the olimex.com web site).
diff --git a/nuttx/configs/nucleus2g/tools/usb-driver.txt b/nuttx/configs/nucleus2g/tools/usb-driver.txt
index 2a649dfb8..83d7598a5 100644
--- a/nuttx/configs/nucleus2g/tools/usb-driver.txt
+++ b/nuttx/configs/nucleus2g/tools/usb-driver.txt
@@ -2,15 +2,24 @@ https://www.olimex.com/dev/pdf/ARM/JTAG/Repair%20Procedure%20for%20OpenOcd-Rev.%
 
 Repair procedure for ARM-USB-OCD drivers
 
-1. Uninstalling ARM-USB-OCD drivers.
-1.1. Connect your programmer/debugger to your computer, open Device Manager and uninstall the drivers for ARM-USB-OCD.
-1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager, disconnect the programmer from your computer.
-1.3. Now you should download FTClean.exe from here: http://www.ftdichip.com/Support/Utilities/FTClean.zip.
-1.4. After download is complete extract the “*.zip” file, open folder FTClean,  and run FTClean.exe
-1.5. Ror VID (Hex) select “Other”. And after that fill the first box with 15ba and “PID (Hex)” with 0004.
-1.6. Press “Clean System” button.  Make sure that all FTDI devices are disconnected. (My require administrator privileges).
+1.   Uninstalling ARM-USB-OCD drivers
+-------------------------------------
+1.1. Connect your programmer/debugger to your computer, open Device Manager
+     and uninstall the drivers for ARM-USB-OCD.
+1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager,
+     disconnect the programmer from your computer.
+1.3. Now you should download FTClean.exe from here:
+     http://www.ftdichip.com/Support/Utilities/FTClean.zip.
+1.4. After download is complete extract the "*.zip" file, open folder FTClean,
+     and run FTClean.exe
+1.5. Ror VID (Hex) select "Other". And after that fill the first box with 15ba
+     and "PID (Hex)" with 0004.
+1.6. Press "Clean System" button.  Make sure that all FTDI devices are
+     disconnected. (My require administrator privileges).
 
-2. Re-install ARM-USB-OCD driver
+2. Re-installing the ARM-USB-OCD driver
+---------------------------------------
 2.1 Connect the programmer/debugger to the computer.
-2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER directory and install.
-
+2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER
+    directory and install. (A different driver is required for OpenOCD
+    0.4.0.  That driver is available from the olimex.com web site).
diff --git a/nuttx/configs/olimex-lpc1766stk/tools/usb-driver.txt b/nuttx/configs/olimex-lpc1766stk/tools/usb-driver.txt
index 2a649dfb8..83d7598a5 100644
--- a/nuttx/configs/olimex-lpc1766stk/tools/usb-driver.txt
+++ b/nuttx/configs/olimex-lpc1766stk/tools/usb-driver.txt
@@ -2,15 +2,24 @@ https://www.olimex.com/dev/pdf/ARM/JTAG/Repair%20Procedure%20for%20OpenOcd-Rev.%
 
 Repair procedure for ARM-USB-OCD drivers
 
-1. Uninstalling ARM-USB-OCD drivers.
-1.1. Connect your programmer/debugger to your computer, open Device Manager and uninstall the drivers for ARM-USB-OCD.
-1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager, disconnect the programmer from your computer.
-1.3. Now you should download FTClean.exe from here: http://www.ftdichip.com/Support/Utilities/FTClean.zip.
-1.4. After download is complete extract the “*.zip” file, open folder FTClean,  and run FTClean.exe
-1.5. Ror VID (Hex) select “Other”. And after that fill the first box with 15ba and “PID (Hex)” with 0004.
-1.6. Press “Clean System” button.  Make sure that all FTDI devices are disconnected. (My require administrator privileges).
+1.   Uninstalling ARM-USB-OCD drivers
+-------------------------------------
+1.1. Connect your programmer/debugger to your computer, open Device Manager
+     and uninstall the drivers for ARM-USB-OCD.
+1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager,
+     disconnect the programmer from your computer.
+1.3. Now you should download FTClean.exe from here:
+     http://www.ftdichip.com/Support/Utilities/FTClean.zip.
+1.4. After download is complete extract the "*.zip" file, open folder FTClean,
+     and run FTClean.exe
+1.5. Ror VID (Hex) select "Other". And after that fill the first box with 15ba
+     and "PID (Hex)" with 0004.
+1.6. Press "Clean System" button.  Make sure that all FTDI devices are
+     disconnected. (My require administrator privileges).
 
-2. Re-install ARM-USB-OCD driver
+2. Re-installing the ARM-USB-OCD driver
+---------------------------------------
 2.1 Connect the programmer/debugger to the computer.
-2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER directory and install.
-
+2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER
+    directory and install. (A different driver is required for OpenOCD
+    0.4.0.  That driver is available from the olimex.com web site).
diff --git a/nuttx/configs/olimex-strp711/scripts/usb-driver.txt b/nuttx/configs/olimex-strp711/scripts/usb-driver.txt
index 2a649dfb8..83d7598a5 100644
--- a/nuttx/configs/olimex-strp711/scripts/usb-driver.txt
+++ b/nuttx/configs/olimex-strp711/scripts/usb-driver.txt
@@ -2,15 +2,24 @@ https://www.olimex.com/dev/pdf/ARM/JTAG/Repair%20Procedure%20for%20OpenOcd-Rev.%
 
 Repair procedure for ARM-USB-OCD drivers
 
-1. Uninstalling ARM-USB-OCD drivers.
-1.1. Connect your programmer/debugger to your computer, open Device Manager and uninstall the drivers for ARM-USB-OCD.
-1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager, disconnect the programmer from your computer.
-1.3. Now you should download FTClean.exe from here: http://www.ftdichip.com/Support/Utilities/FTClean.zip.
-1.4. After download is complete extract the “*.zip” file, open folder FTClean,  and run FTClean.exe
-1.5. Ror VID (Hex) select “Other”. And after that fill the first box with 15ba and “PID (Hex)” with 0004.
-1.6. Press “Clean System” button.  Make sure that all FTDI devices are disconnected. (My require administrator privileges).
+1.   Uninstalling ARM-USB-OCD drivers
+-------------------------------------
+1.1. Connect your programmer/debugger to your computer, open Device Manager
+     and uninstall the drivers for ARM-USB-OCD.
+1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager,
+     disconnect the programmer from your computer.
+1.3. Now you should download FTClean.exe from here:
+     http://www.ftdichip.com/Support/Utilities/FTClean.zip.
+1.4. After download is complete extract the "*.zip" file, open folder FTClean,
+     and run FTClean.exe
+1.5. Ror VID (Hex) select "Other". And after that fill the first box with 15ba
+     and "PID (Hex)" with 0004.
+1.6. Press "Clean System" button.  Make sure that all FTDI devices are
+     disconnected. (My require administrator privileges).
 
-2. Re-install ARM-USB-OCD driver
+2. Re-installing the ARM-USB-OCD driver
+---------------------------------------
 2.1 Connect the programmer/debugger to the computer.
-2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER directory and install.
-
+2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER
+    directory and install. (A different driver is required for OpenOCD
+    0.4.0.  That driver is available from the olimex.com web site).
diff --git a/nuttx/configs/shenzhou/README.txt b/nuttx/configs/shenzhou/README.txt
index 3508bbefe..ca9fdafdb 100755
--- a/nuttx/configs/shenzhou/README.txt
+++ b/nuttx/configs/shenzhou/README.txt
@@ -677,8 +677,8 @@ Where <subdir> is one of the following:
 
     CONFIG_STM32_CODESOURCERYW=y              : CodeSourcery under Windows
     CONFIG_NSH_DHCPC=n                        : DHCP is disabled
-    CONFIG_NSH_IPADDR=(10<<24|0<<16|0<<8|2)   : Target IP address 10.0.0.2
-    CONFIG_NSH_DRIPADDR=(10<<24|0<<16|0<<8|1) : Host IP address 10.0.0.1
+    CONFIG_NSH_IPADDR=0x0a000002              : Target IP address 10.0.0.2
+    CONFIG_NSH_DRIPADDR=0x0a000001            : Host IP address 10.0.0.1
 
     NOTES:
     1. This example assumes that a network is connected.  During its
@@ -687,183 +687,3 @@ Where <subdir> is one of the following:
        delay (maybe 30 seconds?) before anything happens.  That is the timeout
        before the networking finally gives up and decides that no network is
        available.
-
-    2. This example supports the ADC test (apps/examples/adc) but this must
-       be manually enabled by selecting:
-
-       CONFIG_ADC=y             : Enable the generic ADC infrastructure
-       CONFIG_STM32_ADC3=y      : Enable ADC3
-       CONFIG_STM32_TIM1=y      : Enable Timer 1
-       CONFIG_STM32_TIM1_ADC=y  : Indicate that timer 1 will be used to trigger an ADC
-       CONFIG_STM32_TIM1_ADC3=y : Assign timer 1 to drive ADC3 sampling
-       CONFIG_STM32_ADC3_SAMPLE_FREQUENCY=100 : Select a sampling frequency
-
-       See also apps/examples/README.txt
-
-       General debug for analog devices (ADC/DAC):
-
-       CONFIG_DEBUG_ANALOG
-
-    3. This example supports the PWM test (apps/examples/pwm) but this must
-       be manually enabled by selecting eeither
-
-       CONFIG_PWM=y                : Enable the generic PWM infrastructure
-       CONFIG_PWM_PULSECOUNT=n     : Disable to support for TIM1/8 pulse counts
-       CONFIG_STM32_TIM4=y         : Enable TIM4
-       CONFIG_STM32_TIM4_PWM=y     : Use TIM4 to generate PWM output
-       CONFIG_STM32_TIM4_CHANNEL=2 : Select output on TIM4, channel 2
-
-       If CONFIG_STM32_FSMC is disabled, output will appear on CN3, pin 32.
-       Ground is available on CN3, pin1.
-
-       Or..
-
-       CONFIG_PWM=y                : Enable the generic PWM infrastructure
-       CONFIG_PWM_PULSECOUNT=y     : Enable to support for TIM1/8 pulse counts
-       CONFIG_STM32_TIM8=y         : Enable TIM8
-       CONFIG_STM32_TIM8_PWM=y     : Use TIM8 to generate PWM output
-       CONFIG_STM32_TIM8_CHANNEL=4 : Select output on TIM8, channel 4
-
-       If CONFIG_STM32_FSMC is disabled, output will appear on CN3, pin 17
-       Ground is available on CN23 pin1.
-
-       See also include/board.h and apps/examples/README.txt
-
-       Special PWM-only debug options:
-
-       CONFIG_DEBUG_PWM
-
-    4. This example supports the CAN loopback test (apps/examples/can) but this
-       must be manually enabled by selecting:
-
-       CONFIG_CAN=y             : Enable the generic CAN infrastructure
-       CONFIG_CAN_EXID=y or n   : Enable to support extended ID frames
-       CONFIG_STM32_CAN1=y      : Enable CAN1
-       CONFIG_CAN_LOOPBACK=y    : Enable CAN loopback mode
-
-       See also apps/examples/README.txt
-
-       Special CAN-only debug options:
-
-       CONFIG_DEBUG_CAN
-       CONFIG_CAN_REGDEBUG
-
-    5. This example can support an FTP client.  In order to build in FTP client
-       support simply uncomment the following lines in the appconfig file (before
-       configuring) or in the apps/.config file (after configuring):
-
-       #CONFIGURED_APPS += netutils/ftpc
-       #CONFIGURED_APPS += examples/ftpc
-
-    6. This example can support an FTP server.  In order to build in FTP server
-       support simply uncomment the following lines in the appconfig file (before
-       configuring) or in the apps/.config file (after configuring):
-
-       #CONFIGURED_APPS += netutils/ftpd
-       #CONFIGURED_APPS += examples/ftpd
-
-       And enable poll() support in the NuttX configuration file:
-
-       CONFIG_DISABLE_POLL=n
-
-    7. This example supports the watchdog timer test (apps/examples/watchdog)
-       but this must be manually enabled by selecting:
-
-       CONFIG_WATCHDOG=y         : Enables watchdog timer driver support
-       CONFIG_STM32_WWDG=y       : Enables the WWDG timer facility, OR
-       CONFIG_STM32_IWDG=y       : Enables the IWDG timer facility (but not both)
-
-       The WWDG watchdog is driven off the (fast) 42MHz PCLK1 and, as result,
-       has a maximum timeout value of 49 milliseconds.  For WWDG watchdog, you
-       should also add the fillowing to the configuration file:
-
-       CONFIG_EXAMPLES_WATCHDOG_PINGDELAY=20
-       CONFIG_EXAMPLES_WATCHDOG_TIMEOUT=49
-
-       The IWDG timer has a range of about 35 seconds and should not be an issue.
-
-    7. Adding LCD and graphics support:
-
-       appconfig (apps/.config):  Enable the application configurations that you
-       want to use.  Asexamples:
-
-       CONFIGURED_APPS += examples/nx       : Pick one or more
-       CONFIGURED_APPS += examples/nxhello  :
-       CONFIGURED_APPS += examples/nximage  :
-       CONFIGURED_APPS += examples/nxlines  :
-
-       defconfig (nuttx/.config):
-
-       CONFIG_STM32_FSMC=y                  : FSMC support is required for the LCD
-       CONFIG_NX=y                          : Enable graphics suppport
-       CONFIG_MM_REGIONS=3                  : When FSMC is enabled, so is the on-board SRAM memory region
-
-    8. USB OTG FS Device or Host Support
- 
-       CONFIG_USBDEV          - Enable USB device support, OR
-       CONFIG_USBHOST         - Enable USB host support
-       CONFIG_STM32_OTGFS     - Enable the STM32 USB OTG FS block
-       CONFIG_STM32_SYSCFG    - Needed
-       CONFIG_SCHED_WORKQUEUE - Worker thread support is required
-
-    9. USB OTG FS Host Support.  The following changes will enable support for
-       a USB host on the STM32F4Discovery, including support for a mass storage
-       class driver:
-
-       CONFIG_USBDEV=n          - Make sure tht USB device support is disabled
-       CONFIG_USBHOST=y         - Enable USB host support
-       CONFIG_STM32_OTGFS=y     - Enable the STM32 USB OTG FS block
-       CONFIG_STM32_SYSCFG=y    - Needed for all USB OTF FS support
-       CONFIG_SCHED_WORKQUEUE=y - Worker thread support is required for the mass
-                                  storage class driver.
-       CONFIG_NSH_ARCHINIT=y    - Architecture specific USB initialization
-                                  is needed for NSH
-       CONFIG_FS_FAT=y          - Needed by the USB host mass storage class.
-
-       With those changes, you can use NSH with a FLASH pen driver as shown
-       belong.  Here NSH is started with nothing in the USB host slot:
-
-       NuttShell (NSH) NuttX-x.yy
-       nsh> ls /dev
-       /dev:
-        console
-        null
-        ttyS0
-
-       After inserting the FLASH drive, the /dev/sda appears and can be
-       mounted like this:
-
-       nsh> ls /dev
-       /dev:
-        console
-        null
-        sda
-        ttyS0
-       nsh> mount -t vfat /dev/sda /mnt/stuff
-       nsh> ls /mnt/stuff
-       /mnt/stuff:
-        -rw-rw-rw-   16236 filea.c
-
-       And files on the FLASH can be manipulated to standard interfaces:
-
-       nsh> echo "This is a test" >/mnt/stuff/atest.txt
-       nsh> ls /mnt/stuff
-       /mnt/stuff:
-        -rw-rw-rw-   16236 filea.c
-        -rw-rw-rw-      16 atest.txt
-       nsh> cat /mnt/stuff/atest.txt
-       This is a test
-       nsh> cp /mnt/stuff/filea.c fileb.c
-       nsh> ls /mnt/stuff
-       /mnt/stuff:
-        -rw-rw-rw-   16236 filea.c
-        -rw-rw-rw-      16 atest.txt
-        -rw-rw-rw-   16236 fileb.c
-
-       To prevent data loss, don't forget to un-mount the FLASH drive
-       before removing it:
-
-       nsh> umount /mnt/stuff
-
-    11. This configuration requires that jumper JP22 be set to enable RS-232
-       operation.
diff --git a/nuttx/configs/shenzhou/tools/olimex-arm-usb-ocd.cfg b/nuttx/configs/shenzhou/tools/olimex-arm-usb-ocd.cfg
index 9752dd418..d9ff2e515 100644
--- a/nuttx/configs/shenzhou/tools/olimex-arm-usb-ocd.cfg
+++ b/nuttx/configs/shenzhou/tools/olimex-arm-usb-ocd.cfg
@@ -6,8 +6,6 @@
 
 interface ft2232
 ft2232_device_desc "Olimex OpenOCD JTAG"
-ft2232_layout olimex-jtag
-ft2232_vid_pid 0x15ba 0x0003
-
-#jtag_khz 600
+ft2232_layout "olimex-jtag"
+ft2232_vid_pid 0x15BA 0x0003
 
diff --git a/nuttx/configs/shenzhou/tools/usb-driver.txt b/nuttx/configs/shenzhou/tools/usb-driver.txt
index 2a649dfb8..83d7598a5 100644
--- a/nuttx/configs/shenzhou/tools/usb-driver.txt
+++ b/nuttx/configs/shenzhou/tools/usb-driver.txt
@@ -2,15 +2,24 @@ https://www.olimex.com/dev/pdf/ARM/JTAG/Repair%20Procedure%20for%20OpenOcd-Rev.%
 
 Repair procedure for ARM-USB-OCD drivers
 
-1. Uninstalling ARM-USB-OCD drivers.
-1.1. Connect your programmer/debugger to your computer, open Device Manager and uninstall the drivers for ARM-USB-OCD.
-1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager, disconnect the programmer from your computer.
-1.3. Now you should download FTClean.exe from here: http://www.ftdichip.com/Support/Utilities/FTClean.zip.
-1.4. After download is complete extract the “*.zip” file, open folder FTClean,  and run FTClean.exe
-1.5. Ror VID (Hex) select “Other”. And after that fill the first box with 15ba and “PID (Hex)” with 0004.
-1.6. Press “Clean System” button.  Make sure that all FTDI devices are disconnected. (My require administrator privileges).
+1.   Uninstalling ARM-USB-OCD drivers
+-------------------------------------
+1.1. Connect your programmer/debugger to your computer, open Device Manager
+     and uninstall the drivers for ARM-USB-OCD.
+1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager,
+     disconnect the programmer from your computer.
+1.3. Now you should download FTClean.exe from here:
+     http://www.ftdichip.com/Support/Utilities/FTClean.zip.
+1.4. After download is complete extract the "*.zip" file, open folder FTClean,
+     and run FTClean.exe
+1.5. Ror VID (Hex) select "Other". And after that fill the first box with 15ba
+     and "PID (Hex)" with 0004.
+1.6. Press "Clean System" button.  Make sure that all FTDI devices are
+     disconnected. (My require administrator privileges).
 
-2. Re-install ARM-USB-OCD driver
+2. Re-installing the ARM-USB-OCD driver
+---------------------------------------
 2.1 Connect the programmer/debugger to the computer.
-2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER directory and install.
-
+2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER
+    directory and install. (A different driver is required for OpenOCD
+    0.4.0.  That driver is available from the olimex.com web site).
diff --git a/nuttx/configs/stm3210e-eval/tools/usb-driver.txt b/nuttx/configs/stm3210e-eval/tools/usb-driver.txt
index 2a649dfb8..83d7598a5 100644
--- a/nuttx/configs/stm3210e-eval/tools/usb-driver.txt
+++ b/nuttx/configs/stm3210e-eval/tools/usb-driver.txt
@@ -2,15 +2,24 @@ https://www.olimex.com/dev/pdf/ARM/JTAG/Repair%20Procedure%20for%20OpenOcd-Rev.%
 
 Repair procedure for ARM-USB-OCD drivers
 
-1. Uninstalling ARM-USB-OCD drivers.
-1.1. Connect your programmer/debugger to your computer, open Device Manager and uninstall the drivers for ARM-USB-OCD.
-1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager, disconnect the programmer from your computer.
-1.3. Now you should download FTClean.exe from here: http://www.ftdichip.com/Support/Utilities/FTClean.zip.
-1.4. After download is complete extract the “*.zip” file, open folder FTClean,  and run FTClean.exe
-1.5. Ror VID (Hex) select “Other”. And after that fill the first box with 15ba and “PID (Hex)” with 0004.
-1.6. Press “Clean System” button.  Make sure that all FTDI devices are disconnected. (My require administrator privileges).
+1.   Uninstalling ARM-USB-OCD drivers
+-------------------------------------
+1.1. Connect your programmer/debugger to your computer, open Device Manager
+     and uninstall the drivers for ARM-USB-OCD.
+1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager,
+     disconnect the programmer from your computer.
+1.3. Now you should download FTClean.exe from here:
+     http://www.ftdichip.com/Support/Utilities/FTClean.zip.
+1.4. After download is complete extract the "*.zip" file, open folder FTClean,
+     and run FTClean.exe
+1.5. Ror VID (Hex) select "Other". And after that fill the first box with 15ba
+     and "PID (Hex)" with 0004.
+1.6. Press "Clean System" button.  Make sure that all FTDI devices are
+     disconnected. (My require administrator privileges).
 
-2. Re-install ARM-USB-OCD driver
+2. Re-installing the ARM-USB-OCD driver
+---------------------------------------
 2.1 Connect the programmer/debugger to the computer.
-2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER directory and install.
-
+2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER
+    directory and install. (A different driver is required for OpenOCD
+    0.4.0.  That driver is available from the olimex.com web site).
diff --git a/nuttx/configs/stm3220g-eval/tools/usb-driver.txt b/nuttx/configs/stm3220g-eval/tools/usb-driver.txt
new file mode 100644
index 000000000..83d7598a5
--- /dev/null
+++ b/nuttx/configs/stm3220g-eval/tools/usb-driver.txt
@@ -0,0 +1,25 @@
+https://www.olimex.com/dev/pdf/ARM/JTAG/Repair%20Procedure%20for%20OpenOcd-Rev.%20G%20drivers.pdf
+
+Repair procedure for ARM-USB-OCD drivers
+
+1.   Uninstalling ARM-USB-OCD drivers
+-------------------------------------
+1.1. Connect your programmer/debugger to your computer, open Device Manager
+     and uninstall the drivers for ARM-USB-OCD.
+1.2. After you have uninstalled ARM-USB-TINY driver from Device Manager,
+     disconnect the programmer from your computer.
+1.3. Now you should download FTClean.exe from here:
+     http://www.ftdichip.com/Support/Utilities/FTClean.zip.
+1.4. After download is complete extract the "*.zip" file, open folder FTClean,
+     and run FTClean.exe
+1.5. Ror VID (Hex) select "Other". And after that fill the first box with 15ba
+     and "PID (Hex)" with 0004.
+1.6. Press "Clean System" button.  Make sure that all FTDI devices are
+     disconnected. (My require administrator privileges).
+
+2. Re-installing the ARM-USB-OCD driver
+---------------------------------------
+2.1 Connect the programmer/debugger to the computer.
+2.2 When prompted, browse to the C:\gccfd\DRIVERS\ARM-USB-OCD-DRIVER
+    directory and install. (A different driver is required for OpenOCD
+    0.4.0.  That driver is available from the olimex.com web site).