Browse Source
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@5118 7fd9a85b-ad96-42d3-883c-3090e2eb8679sbg
49 changed files with 391 additions and 21 deletions
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
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-install 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. |
||||
|
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
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-install 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. |
||||
|
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
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-install 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. |
||||
|
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
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-install 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. |
||||
|
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
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-install 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. |
||||
|
@ -0,0 +1,13 @@
@@ -0,0 +1,13 @@
|
||||
# |
||||
# Olimex ARM-USB-OCD |
||||
# |
||||
# http://www.olimex.com/dev/arm-usb-ocd.html |
||||
# |
||||
|
||||
interface ft2232 |
||||
ft2232_device_desc "Olimex OpenOCD JTAG" |
||||
ft2232_layout olimex-jtag |
||||
ft2232_vid_pid 0x15ba 0x0003 |
||||
|
||||
#jtag_khz 600 |
||||
|
@ -0,0 +1,92 @@
@@ -0,0 +1,92 @@
|
||||
#!/bin/sh |
||||
|
||||
# Get command line parameters |
||||
|
||||
USAGE="USAGE: $0 [-dh] <TOPDIR>" |
||||
ADVICE="Try '$0 -h' for more information" |
||||
|
||||
unset DEBUG |
||||
|
||||
while [ ! -z "$1" ]; do |
||||
case $1 in |
||||
-d ) |
||||
set -x |
||||
DEBUG=-d3 |
||||
;; |
||||
-h ) |
||||
echo "$0 is a tool for generation of proper version files for the NuttX build" |
||||
echo "" |
||||
echo $USAGE |
||||
echo "" |
||||
echo "Where:" |
||||
echo " -d" |
||||
echo " Enable script debug" |
||||
echo " -h" |
||||
echo " show this help message and exit" |
||||
echo " Use the OpenOCD 0.4.0" |
||||
echo " <TOPDIR>" |
||||
echo " The full path to the top-level NuttX directory" |
||||
exit 0 |
||||
;; |
||||
* ) |
||||
break; |
||||
;; |
||||
esac |
||||
shift |
||||
done |
||||
|
||||
TOPDIR=$1 |
||||
if [ -z "${TOPDIR}" ]; then |
||||
echo "Missing argument" |
||||
echo $USAGE |
||||
echo $ADVICE |
||||
exit 1 |
||||
fi |
||||
|
||||
# This script *probably* only works with the following versions of OpenOCD: |
||||
|
||||
# Local search directory and configurations |
||||
|
||||
OPENOCD_SEARCHDIR="${TOPDIR}/configs/shenzhou/tools" |
||||
OPENOCD_WSEARCHDIR="`cygpath -w ${OPENOCD_SEARCHDIR}`" |
||||
|
||||
OPENOCD_PATH="/cygdrive/c/Program Files (x86)/OpenOCD/0.4.0/bin" |
||||
OPENOCD_EXE=openocd.exe |
||||
OPENOCD_INTERFACE="olimex-arm-usb-ocd.cfg" |
||||
|
||||
|
||||
OPENOCD_TARGET="stm32.cfg" |
||||
OPENOCD_ARGS="${DEBUG} -s ${OPENOCD_WSEARCHDIR} -f ${OPENOCD_INTERFACE} -f ${OPENOCD_TARGET}" |
||||
|
||||
echo "Trying OpenOCD 0.4.0 path: ${OPENOCD_PATH}/${OPENOCD_EXE}" |
||||
|
||||
# Verify that everything is what it claims it is and is located where it claims it is. |
||||
|
||||
if [ ! -x "${OPENOCD_PATH}/${OPENOCD_EXE}" ]; then |
||||
echo "OpenOCD executable does not exist: ${OPENOCD_PATH}/${OPENOCD_EXE}" |
||||
exit 1 |
||||
fi |
||||
if [ ! -f "${OPENOCD_SEARCHDIR}/${OPENOCD_TARGET}" ]; then |
||||
echo "OpenOCD target config file does not exist: ${OPENOCD_SEARCHDIR}/${OPENOCD_TARGET}" |
||||
exit 1 |
||||
fi |
||||
if [ ! -f "${OPENOCD_SEARCHDIR}/${OPENOCD_INTERFACE}" ]; then |
||||
echo "OpenOCD interface config file does not exist: ${OPENOCD_SEARCHDIR}/${OPENOCD_INTERFACE}" |
||||
exit 1 |
||||
fi |
||||
|
||||
# Enable debug if so requested |
||||
|
||||
if [ "X$2" = "X-d" ]; then |
||||
OPENOCD_ARGS=$OPENOCD_ARGS" -d3" |
||||
set -x |
||||
fi |
||||
|
||||
# Okay... do it! |
||||
|
||||
echo "Starting OpenOCD" |
||||
"${OPENOCD_PATH}/${OPENOCD_EXE}" ${OPENOCD_ARGS} & |
||||
echo "OpenOCD daemon started" |
||||
ps -ef | grep openocd |
||||
echo "In GDB: target remote localhost:3333" |
||||
|
@ -0,0 +1,69 @@
@@ -0,0 +1,69 @@
|
||||
# script for stm32 |
||||
|
||||
if { [info exists CHIPNAME] } { |
||||
set _CHIPNAME $CHIPNAME |
||||
} else { |
||||
set _CHIPNAME stm32 |
||||
} |
||||
|
||||
if { [info exists ENDIAN] } { |
||||
set _ENDIAN $ENDIAN |
||||
} else { |
||||
set _ENDIAN little |
||||
} |
||||
|
||||
# Work-area is a space in RAM used for flash programming |
||||
# By default use 16kB |
||||
if { [info exists WORKAREASIZE] } { |
||||
set _WORKAREASIZE $WORKAREASIZE |
||||
} else { |
||||
set _WORKAREASIZE 0x4000 |
||||
} |
||||
|
||||
# JTAG speed should be <= F_CPU/6. F_CPU after reset is 8MHz, so use F_JTAG = 1MHz |
||||
jtag_khz 1000 |
||||
|
||||
jtag_nsrst_delay 100 |
||||
jtag_ntrst_delay 100 |
||||
|
||||
#jtag scan chain |
||||
if { [info exists CPUTAPID ] } { |
||||
set _CPUTAPID $CPUTAPID |
||||
} else { |
||||
# See STM Document RM0008 |
||||
# Section 26.6.3 |
||||
set _CPUTAPID 0x3ba00477 |
||||
} |
||||
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID |
||||
|
||||
if { [info exists BSTAPID ] } { |
||||
# FIXME this never gets used to override defaults... |
||||
set _BSTAPID $BSTAPID |
||||
} else { |
||||
# See STM Document RM0008 |
||||
# Section 29.6.2 |
||||
# Low density devices, Rev A |
||||
set _BSTAPID1 0x06412041 |
||||
# Medium density devices, Rev A |
||||
set _BSTAPID2 0x06410041 |
||||
# Medium density devices, Rev B and Rev Z |
||||
set _BSTAPID3 0x16410041 |
||||
# High density devices, Rev A |
||||
set _BSTAPID4 0x06414041 |
||||
# Connectivity line devices, Rev A and Rev Z |
||||
set _BSTAPID5 0x06418041 |
||||
} |
||||
jtag newtap $_CHIPNAME bs -irlen 5 -expected-id $_BSTAPID1 \ |
||||
-expected-id $_BSTAPID2 -expected-id $_BSTAPID3 \ |
||||
-expected-id $_BSTAPID4 -expected-id $_BSTAPID5 |
||||
|
||||
set _TARGETNAME $_CHIPNAME.cpu |
||||
target create $_TARGETNAME cortex_m3 -endian $_ENDIAN -chain-position $_TARGETNAME |
||||
|
||||
$_TARGETNAME configure -work-area-phys 0x20000000 -work-area-size $_WORKAREASIZE -work-area-backup 0 |
||||
|
||||
set _FLASHNAME $_CHIPNAME.flash |
||||
flash bank $_FLASHNAME stm32x 0 0 0 0 $_TARGETNAME |
||||
|
||||
# For more information about the configuration files, take a look at: |
||||
# openocd.texi |
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
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-install 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. |
||||
|
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
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-install 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. |
||||
|
Loading…
Reference in new issue