forked from zephyrproject-rtos/openocd
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- prepare OpenOCD for branching, created ./trunk/
git-svn-id: svn://svn.berlios.de/openocd/trunk@64 b42882b7-edfa-0310-969c-e2dbd0fdcd60
- Loading branch information
drath
committed
Jun 2, 2006
0 parents
commit 8b4e882
Showing
93 changed files
with
25,116 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Dominic Rath <[email protected]> |
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
2005-07-03 Dominic Rath <[email protected]> | ||
|
||
* First public release | ||
|
||
2005-10-27 Dominic Rath <[email protected]> | ||
|
||
* First release of new codebase |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,194 @@ | ||
Prerequisites | ||
============= | ||
|
||
When building with support for FTDI FT2232 based devices, you need at least | ||
one of the following libraries: | ||
|
||
- libftdi (http://www.intra2net.com/opensource/ftdi/) | ||
- libftd2xx (http://www.ftdichip.com/Drivers/D2XX.htm) | ||
|
||
Basic Installation | ||
================== | ||
|
||
OpenOCD is distributed without autotools generated files, i.e. without a | ||
configure script. Run ./bootstrap in the openocd directory to have all | ||
necessary files generated. | ||
|
||
You have to explicitly enable desired JTAG interfaces during configure: | ||
|
||
./configure --enable-parport --enable-ftdi2232 --enable-ftd2xx \ | ||
--enable-amtjtagaccel | ||
|
||
Under Windows/Cygwin, only the ftd2xx driver is supported for FT2232 based | ||
devices. You have to specify the location of the FTDI driver package with the | ||
--with-ftd2xx=/full/path/name option. | ||
|
||
Under Linux you can choose to build the parport driver with support for | ||
/dev/parportN instead of the default access with direct port I/O using | ||
--enable-parport_ppdev. This has the advantage of running OpenOCD without root | ||
privileges at the expense of a slight performance decrease. | ||
|
||
These are generic installation instructions. | ||
|
||
The `configure' shell script attempts to guess correct values for | ||
various system-dependent variables used during compilation. It uses | ||
those values to create a `Makefile' in each directory of the package. | ||
It may also create one or more `.h' files containing system-dependent | ||
definitions. Finally, it creates a shell script `config.status' that | ||
you can run in the future to recreate the current configuration, a file | ||
`config.cache' that saves the results of its tests to speed up | ||
reconfiguring, and a file `config.log' containing compiler output | ||
(useful mainly for debugging `configure'). | ||
|
||
If you need to do unusual things to compile the package, please try | ||
to figure out how `configure' could check whether to do them, and mail | ||
diffs or instructions to the address given in the `README' so they can | ||
be considered for the next release. If at some point `config.cache' | ||
contains results you don't want to keep, you may remove or edit it. | ||
|
||
The file `configure.in' is used to create `configure' by a program | ||
called `autoconf'. You only need `configure.in' if you want to change | ||
it or regenerate `configure' using a newer version of `autoconf'. | ||
|
||
The simplest way to compile this package is: | ||
|
||
1. `cd' to the directory containing the package's source code and type | ||
`./configure' to configure the package for your system. If you're | ||
using `csh' on an old version of System V, you might need to type | ||
`sh ./configure' instead to prevent `csh' from trying to execute | ||
`configure' itself. | ||
|
||
Running `configure' takes a while. While running, it prints some | ||
messages telling which features it is checking for. | ||
|
||
2. Type `make' to compile the package. | ||
|
||
3. Type `make install' to install the programs and any data files and | ||
documentation. | ||
|
||
4. You can remove the program binaries and object files from the | ||
source code directory by typing `make clean'. | ||
|
||
Compilers and Options | ||
===================== | ||
|
||
Some systems require unusual options for compilation or linking that | ||
the `configure' script does not know about. You can give `configure' | ||
initial values for variables by setting them in the environment. Using | ||
a Bourne-compatible shell, you can do that on the command line like | ||
this: | ||
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure | ||
|
||
Or on systems that have the `env' program, you can do it like this: | ||
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure | ||
|
||
Compiling For Multiple Architectures | ||
==================================== | ||
|
||
You can compile the package for more than one kind of computer at the | ||
same time, by placing the object files for each architecture in their | ||
own directory. To do this, you must use a version of `make' that | ||
supports the `VPATH' variable, such as GNU `make'. `cd' to the | ||
directory where you want the object files and executables to go and run | ||
the `configure' script. `configure' automatically checks for the | ||
source code in the directory that `configure' is in and in `..'. | ||
|
||
If you have to use a `make' that does not supports the `VPATH' | ||
variable, you have to compile the package for one architecture at a time | ||
in the source code directory. After you have installed the package for | ||
one architecture, use `make distclean' before reconfiguring for another | ||
architecture. | ||
|
||
Installation Names | ||
================== | ||
|
||
By default, `make install' will install the package's files in | ||
`/usr/local/bin', `/usr/local/man', etc. You can specify an | ||
installation prefix other than `/usr/local' by giving `configure' the | ||
option `--prefix=PATH'. | ||
|
||
You can specify separate installation prefixes for | ||
architecture-specific files and architecture-independent files. If you | ||
give `configure' the option `--exec-prefix=PATH', the package will use | ||
PATH as the prefix for installing programs and libraries. | ||
Documentation and other data files will still use the regular prefix. | ||
|
||
If the package supports it, you can cause programs to be installed | ||
with an extra prefix or suffix on their names by giving `configure' the | ||
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. | ||
|
||
Optional Features | ||
================= | ||
|
||
Some packages pay attention to `--enable-FEATURE' options to | ||
`configure', where FEATURE indicates an optional part of the package. | ||
They may also pay attention to `--with-PACKAGE' options, where PACKAGE | ||
is something like `gnu-as' or `x' (for the X Window System). The | ||
`README' should mention any `--enable-' and `--with-' options that the | ||
package recognizes. | ||
|
||
For packages that use the X Window System, `configure' can usually | ||
find the X include and library files automatically, but if it doesn't, | ||
you can use the `configure' options `--x-includes=DIR' and | ||
`--x-libraries=DIR' to specify their locations. | ||
|
||
Specifying the System Type | ||
========================== | ||
|
||
There may be some features `configure' can not figure out | ||
automatically, but needs to determine by the type of host the package | ||
will run on. Usually `configure' can figure that out, but if it prints | ||
a message saying it can not guess the host type, give it the | ||
`--host=TYPE' option. TYPE can either be a short name for the system | ||
type, such as `sun4', or a canonical name with three fields: | ||
CPU-COMPANY-SYSTEM | ||
|
||
See the file `config.sub' for the possible values of each field. If | ||
`config.sub' isn't included in this package, then this package doesn't | ||
need to know the host type. | ||
|
||
If you are building compiler tools for cross-compiling, you can also | ||
use the `--target=TYPE' option to select the type of system they will | ||
produce code for and the `--build=TYPE' option to select the type of | ||
system on which you are compiling the package. | ||
|
||
Sharing Defaults | ||
================ | ||
|
||
If you want to set default values for `configure' scripts to share, | ||
you can create a site shell script called `config.site' that gives | ||
default values for variables like `CC', `cache_file', and `prefix'. | ||
`configure' looks for `PREFIX/share/config.site' if it exists, then | ||
`PREFIX/etc/config.site' if it exists. Or, you can set the | ||
`CONFIG_SITE' environment variable to the location of the site script. | ||
A warning: not all `configure' scripts look for a site script. | ||
|
||
Operation Controls | ||
================== | ||
|
||
`configure' recognizes the following options to control how it | ||
operates. | ||
|
||
`--cache-file=FILE' | ||
Use and save the results of the tests in FILE instead of | ||
`./config.cache'. Set FILE to `/dev/null' to disable caching, for | ||
debugging `configure'. | ||
|
||
`--help' | ||
Print a summary of the options to `configure', and exit. | ||
|
||
`--quiet' | ||
`--silent' | ||
`-q' | ||
Do not print messages saying which checks are being made. | ||
|
||
`--srcdir=DIR' | ||
Look for the package's source code in directory DIR. Usually | ||
`configure' can determine that directory automatically. | ||
|
||
`--version' | ||
Print the version of Autoconf used to generate the `configure' | ||
script, and exit. | ||
|
||
`configure' also accepts some other, not widely useful, options. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# not a GNU package. You can remove this line, if | ||
# have all needed files, that a GNU package needs | ||
AUTOMAKE_OPTIONS = foreign 1.4 | ||
|
||
SUBDIRS = src |
Empty file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
openocd | ||
|
||
Free and Open On-Chip Debugging, In-System Programming | ||
and Boundary-Scan Testing | ||
Copyright (c) 2004, 2005 Dominic Rath | ||
|
||
The debugger uses an IEEE 1149-1 compliant JTAG TAP bus master to access on-chip | ||
debug functionality available on ARM7 and ARM9 based microcontrollers / | ||
system-on-chip solutions. | ||
|
||
User interaction is realized through a telnet command line interface and a gdb | ||
(The GNU Debugger) remote protocol server. | ||
|
||
Initially, support for two JTAG TAP bus master interfaces with public hardware | ||
schematics will be included, but support of additional hardware is an expressed | ||
goal. | ||
|
||
1. JTAG hardware | ||
|
||
Currently, openocd contains support for Wiggler-compatible paralell port | ||
dongles and a USB interface based on the FTDI FT2232, called USBJTAG-1. | ||
A new version of the USB interface, USB-JTAG v1.2, is available with complete | ||
schematics (http://www.fh-augsburg.de/~hhoegl/proj/volksmikro/usb-jtag/050910/). | ||
|
||
It was tested using Amontec's (www.amontec.com) Chameleon POD in it's | ||
Wiggler configuration, but homemade wigglers should work just as well. | ||
In order to use the reset functionality (warm-reset, debug from reset, reset | ||
and init), the choosen Wiggler has to connect the nSRST line. | ||
|
||
USBJTAG-1 is based on a FTDI DLP2232M module and a few additional parts. | ||
Schematics are freely available. USB-JTAG v1.2 doesn't use the DLP2232M, but | ||
has the FTDI chip soldered directly on the PCB. There are two drivers for these | ||
modules implemented, one using the open source libftdi, the other using FTDI's | ||
proprietary FTD2XX library. | ||
|
||
2. Supported cores | ||
|
||
This version of openocd supports the following cores: | ||
|
||
- ARM7TDMI | ||
- ARM9TDMI | ||
|
||
Support for cores with MMUs (ARM720t, ARM920t) is currently being merged. | ||
|
||
3. Licensing | ||
|
||
openocd is licensed under the terms of the GNU General Public License, see the | ||
file COPYING for details. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
- Additional cores. ARM9E(J)-S, ARM7TDMI-S, TI925, ... | ||
- Testing. | ||
- Additional jtag interfaces. Currently, only Wiggler style interfaces and | ||
USBJTAG-1 are supported. | ||
- Testing. | ||
- Handle endianess. The configuration variable is there, but that's about it. | ||
Currently, only little-endian targets and little-endian hosts are supported. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
aclocal \ | ||
&& autoheader \ | ||
&& automake --gnu --add-missing \ | ||
&& autoconf |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,112 @@ | ||
AC_INIT(configure.in) | ||
|
||
AC_SEARCH_LIBS([ioperm], [ioperm]) | ||
|
||
AC_CANONICAL_HOST | ||
|
||
build_bitbang=no | ||
is_cygwin=no | ||
|
||
AC_ARG_ENABLE(parport, | ||
AS_HELP_STRING([--enable-parport], [Enable building the pc parallel port driver]), | ||
[build_parport=$enableval], [build_parport=no]) | ||
|
||
AC_ARG_ENABLE(parport_ppdev, | ||
AS_HELP_STRING([--enable-parport_ppdev], [Enable use of ppdev (/dev/parportN) for parport]), | ||
[parport_use_ppdev=$enableval], [parport_use_ppdev=no]) | ||
|
||
AC_ARG_ENABLE(ftdi2232, | ||
AS_HELP_STRING([--enable-ftdi2232], [Enable building the libftdi ft2232c driver]), | ||
[build_ftdi2232=$enableval], [build_ftdi2232=no]) | ||
|
||
AC_ARG_ENABLE(ftd2xx, | ||
AS_HELP_STRING([--enable-ftd2xx], [Enable building the ftd2xx ft2232c driver]), | ||
[build_ftd2xx=$enableval], [build_ftd2xx=no]) | ||
|
||
AC_ARG_ENABLE(amtjtagaccel, | ||
AS_HELP_STRING([--enable-amtjtagaccel], [Enable building the Amontec JTAG-Accelerator driver]), | ||
[build_amtjtagaccel=$enableval], [build_amtjtagaccel=no]) | ||
|
||
AC_ARG_ENABLE(ep93xx, | ||
AS_HELP_STRING([--enable-ep93xx], [Enable building support for EP93xx based SBCs]), | ||
[build_ep93xx=$enableval], [build_ep93xx=no]) | ||
|
||
AC_ARG_WITH(ftd2xx, | ||
[AS_HELP_STRING(--with-ftd2xx, | ||
[Where libftd2xx can be found <default=search>])], | ||
[], | ||
with_ftd2xx=search) | ||
|
||
if test $build_parport = yes; then | ||
build_bitbang=yes | ||
AC_DEFINE(BUILD_PARPORT, 1, [1 if you want parport.]) | ||
else | ||
AC_DEFINE(BUILD_PARPORT, 0, [0 if you don't want parport.]) | ||
fi | ||
|
||
if test $build_ep93xx = yes; then | ||
build_bitbang=yes | ||
AC_DEFINE(BUILD_EP93XX, 1, [1 if you want ep93xx.]) | ||
else | ||
AC_DEFINE(BUILD_EP93XX, 0, [0 if you don't want ep93xx.]) | ||
fi | ||
|
||
if test $parport_use_ppdev = yes; then | ||
AC_DEFINE(PARPORT_USE_PPDEV, 1, [1 if you want parport to use ppdev.]) | ||
else | ||
AC_DEFINE(PARPORT_USE_PPDEV, 0, [0 if you don't want parport to use ppdev.]) | ||
fi | ||
|
||
if test $build_bitbang = yes; then | ||
AC_DEFINE(BUILD_BITBANG, 1, [1 if you want a bitbang interface.]) | ||
else | ||
AC_DEFINE(BUILD_BITBANG, 0, [0 if you don't want a bitbang interface.]) | ||
fi | ||
|
||
if test $build_ftdi2232 = yes; then | ||
AC_DEFINE(BUILD_FTDI2232, 1, [1 if you want libftdi ft2232.]) | ||
else | ||
AC_DEFINE(BUILD_FTDI2232, 0, [0 if you don't want libftdi ft2232.]) | ||
fi | ||
|
||
if test $build_ftd2xx = yes; then | ||
AC_DEFINE(BUILD_FTD2XX, 1, [1 if you want ftd2xx ft2232.]) | ||
else | ||
AC_DEFINE(BUILD_FTD2XX, 0, [0 if you don't want ftd2xx ft2232.]) | ||
fi | ||
|
||
if test $build_amtjtagaccel = yes; then | ||
AC_DEFINE(BUILD_AMTJTAGACCEL, 1, [1 if you want the Amontec JTAG-Accelerator driver.]) | ||
else | ||
AC_DEFINE(BUILD_AMTJTAGACCEL, 0, [0 if you don't want the Amontec JTAG-Accelerator driver.]) | ||
fi | ||
|
||
case $host in | ||
*-*-cygwin*) | ||
is_cygwin=yes | ||
AC_DEFINE(IS_CYGWIN, 1, [1 if building for Cygwin.]) | ||
;; | ||
*) | ||
AC_DEFINE(IS_CYGWIN, 0, [0 if not building for Cygwin.]) | ||
;; | ||
esac | ||
|
||
AM_CONFIG_HEADER(config.h) | ||
AM_INIT_AUTOMAKE(openocd, 0.1) | ||
|
||
AM_CONDITIONAL(PARPORT, test $build_parport = yes) | ||
AM_CONDITIONAL(EP93XX, test $build_ep93xx = yes) | ||
AM_CONDITIONAL(BITBANG, test $build_bitbang = yes) | ||
AM_CONDITIONAL(FTDI2232, test $build_ftdi2232 = yes) | ||
AM_CONDITIONAL(FTD2XX, test $build_ftd2xx = yes) | ||
AM_CONDITIONAL(AMTJTAGACCEL, test $build_amtjtagaccel = yes) | ||
AM_CONDITIONAL(IS_CYGWIN, test $is_cygwin = yes) | ||
AM_CONDITIONAL(FTD2XXDIR, test $with_ftd2xx != search) | ||
|
||
AC_LANG_C | ||
AC_PROG_CC | ||
AC_PROG_RANLIB | ||
|
||
AC_SUBST(WITH_FTD2XX, $with_ftd2xx) | ||
|
||
AC_OUTPUT(Makefile src/Makefile src/helper/Makefile src/jtag/Makefile src/xsvf/Makefile src/target/Makefile src/server/Makefile src/flash/Makefile) |
Oops, something went wrong.