interesting
/
riscv-openocd
mirror of https://github.com/riscv/riscv-openocd.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
21 Commits 69 Branches 14 Tags 91 MiB
C 88.6%
Perl 2.4%
HTML 2%
Tcl 1.9%
Assembly 1.9%
Other 3.1%
Go to file
drath 3acb107b9a - endianess fixes everywhere but in the flash code. flashing might still be broken on big-endian targets and/or hosts 
- added access to ARM920T vector catch register (via generic register mechanism)
- don't disable linefills on ARM920T cores - this lead to lockups when accessing lines already contained in cache
- read content of ARM920T cache and tlb into file (arm920t read_flash/read_mmu commands)
- memory reading improved on ARM7/9, can be further accelerated with new "arm7_9 fast_memory_access enable" command (renamed from fast_writes)
- made in_handler independent from in field (makes the handler more flexible)
- added timeout to ft2232 when using D2XX library
- fixed STR7x protection bit handling on second bank (thanks to Bernard)
- added support for using the OpenOCD on AT91RM9200 systems (thanks to Anders Larsen)
- fixed AT91SAM7 flash handling when not running from 32kHz clock (thanks to Anders Larsen)


git-svn-id: svn://svn.berlios.de/openocd/trunk@90 b42882b7-edfa-0310-969c-e2dbd0fdcd60
 		2006-08-31 12:41:49 +00:00
doc/configs - endianess fixes everywhere but in the flash code. flashing might still be broken on big-endian targets and/or hosts 2006-08-31 12:41:49 +00:00
src - endianess fixes everywhere but in the flash code. flashing might still be broken on big-endian targets and/or hosts 2006-08-31 12:41:49 +00:00
AUTHORS - prepare OpenOCD for branching, created ./trunk/ 2006-06-02 10:36:31 +00:00
COPYING - prepare OpenOCD for branching, created ./trunk/ 2006-06-02 10:36:31 +00:00
ChangeLog - prepare OpenOCD for branching, created ./trunk/ 2006-06-02 10:36:31 +00:00
INSTALL - updated configuration examples, installation instructions and README (including list of supported JTAG interfaces) 2006-08-14 10:58:12 +00:00
Makefile.am - prepare OpenOCD for branching, created ./trunk/ 2006-06-02 10:36:31 +00:00
NEWS - prepare OpenOCD for branching, created ./trunk/ 2006-06-02 10:36:31 +00:00
README - updated configuration examples, installation instructions and README (including list of supported JTAG interfaces) 2006-08-14 10:58:12 +00:00
TODO - prepare OpenOCD for branching, created ./trunk/ 2006-06-02 10:36:31 +00:00
bootstrap - prepare OpenOCD for branching, created ./trunk/ 2006-06-02 10:36:31 +00:00
configure.in - endianess fixes everywhere but in the flash code. flashing might still be broken on big-endian targets and/or hosts 2006-08-31 12:41:49 +00:00

README 

                                    OpenOCD

			 Free and Open On-Chip Debugging, In-System Programming 
						   and Boundary-Scan Testing
				  Copyright (c) 2004, 2005, 2006 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.

1. JTAG hardware

Currently, OpenOCD supports three types of JTAG interfaces:

- Parallel port wigglers. These devices connect to a PC's parallel port,
providing direct access to the JTAG lines. The OpenOCD contains descriptions
of a few Wiggler layouts, including the original 'Wiggler' design. Other
layouts (i.e. mapping of parallel port pins to JTAG lines) can be added easily.
Typical Wiggler speeds are around 12kByte/s code download to an ARM7's RAM.

- The Amontec JTAG Accelerator. This is a configuration for Amontec's Chameleon
dongle, a parallel port interface based on a Xilinx CoolRunner CPLD. It uses
the IEEE1284 EPP parallel port specification, providing many times the
performance achievable with wiggler-style devices. Additional information is
available on www.amontec.com.
Typical JTAG Accelerator speeds are around 120-160kByte/s to an ARM7's RAM.

- FTDI FT2232 based USB devices. The FT2232 (but not FT232 or FT245) features a
multi-protocol synchronous serial engine (MPSSE) that can be used to run the
serial JTAG protocol. There are several implemenations of FT2232 based devices:

* USBJTAG: http://www.fh-augsburg.de/~hhoegl/proj/usbjtag/usbjtag.html
The USBJTAG was designed by Prof. Hubert Hoegl to provide a high-speed USB
interface for use with the OpenOCD. Schematics are available at the USBJTAG
website, and a homebrew device can easily be built using the FTDI evaluation
module DLP2232M.

* Amontec JTAGkey: www.amontec.com
The Amontec JTAGkey offers support for a wide variety of target voltages from
1.4V to 5V. It also allows the JTAG lines and reset signals to be tri-stated,
allowing easy interfacing with a wide variety of targets.

* Olimex ARM-USB-OCD: www.olimex.com
The Olimex ARM-USB-OCD offers support for a wide vriety of target voltages from
2.0V to 5V. It also allows targets to be powered from the ARM-USB-OCD and
features and additional RS232 UART.

* eVerve Signalyzer: www.signalyzer.com
The Signalyzer offers support for a wide variety of target voltages from 1.2V to
5.5V. A second connector provides access to a TTL level UART.

All FT2232 based devices may be accessed using either FTDI's proprietary FTD2XX
library (www.ftdichip.com) or using an open-source replacement from
http://www.intra2net.com/de/produkte/opensource/ftdi/index.php, also included
with many Linux distributions.

2. Supported cores

This version of openocd supports the following cores:

- ARM7TDMI(-s)
- ARM9TDMI
- ARM920t
- ARM922t
- ARM966e

Support for Intel XScale CPUs (PXA25x, PXA27x and IXP4xx) is currently being
developed.

The OpenOCD is only tested with little-endian targets, but support for
big-endian is planned. If you're interested in helping with this (and you
happen to have a big-endian ARM7/ARM9 system, feel free to contact
Dominic.Rath <at> gmx.de.

3. Host platforms

OpenOCD was originally developed on x86-Linux, but has since then been ported
to run on Windows/Cygwin, native Windows with MinGW, FreeBSD, x86-64-Linux and
(though it's not fully working yet) PowerPC OS-X.

4. Documentation

Documentation for the OpenOCD is hosted in the Berlios OpenFacts Wiki at
http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger.

5. Licensing

OpenOCD is licensed under the terms of the GNU General Public License, see the
file COPYING for details.