Browse Source

docs: update OpenOCD url's to openocd.org domain

Change-Id: I8b55c8d12773a1c36f2fd2afeecf20a74e890064
Signed-off-by: Spencer Oliver <spen@spen-soft.co.uk>
Reviewed-on: http://openocd.zylin.com/2698
Tested-by: jenkins
tags/v0.9.0-rc1
Spencer Oliver Paul Fertser 5 years ago
parent
commit
8d86633eb7
5 changed files with 14 additions and 14 deletions
  1. +2
    -2
      BUGS
  2. +2
    -2
      README
  3. +6
    -6
      doc/openocd.texi
  4. +1
    -1
      src/openocd.c
  5. +3
    -3
      tcl/target/amdm37x.cfg

+ 2
- 2
BUGS View File

@@ -6,11 +6,11 @@ posting a message with your report:

openocd-devel@lists.sourceforge.net

Also, please check the Trac bug database to see if a ticket for
Also, please check the bug database to see if a ticket for
the bug has already been opened. You might be asked to open
such a ticket, or to update an existing ticket with more data.

https://sourceforge.net/apps/trac/openocd/
http://bugs.openocd.org/

To minimize work for OpenOCD developers, you should try to include
all of the information listed below. If you feel that some of the


+ 2
- 2
README View File

@@ -61,10 +61,10 @@ In addition to the in-tree documentation, the latest manuals may be
viewed online at the following URLs:

OpenOCD User's Guide:
http://openocd.sourceforge.net/doc/html/index.html
http://openocd.org/doc/html/index.html

OpenOCD Developer's Manual:
http://openocd.sourceforge.net/doc/doxygen/html/index.html
http://openocd.org/doc/doxygen/html/index.html

These reflect the latest development versions, so the following section
introduces how to build the complete documentation from the package.


+ 6
- 6
doc/openocd.texi View File

@@ -170,7 +170,7 @@ controllers (LPC3180, Orion, S3C24xx, more) is included.

The OpenOCD web site provides the latest public news from the community:

@uref{http://openocd.sourceforge.net/}
@uref{http://openocd.org/}

@section Latest User's Guide:

@@ -178,11 +178,11 @@ The user's guide you are now reading may not be the latest one
available. A version for more recent code may be available.
Its HTML form is published regularly at:

@uref{http://openocd.sourceforge.net/doc/html/index.html}
@uref{http://openocd.org/doc/html/index.html}

PDF form is likewise published at:

@uref{http://openocd.sourceforge.net/doc/pdf/openocd.pdf}
@uref{http://openocd.org/doc/pdf/openocd.pdf}

@section OpenOCD User's Forum

@@ -256,7 +256,7 @@ providing a Doxygen reference manual. This document contains more
technical information about the software internals, development
processes, and similar documentation:

@uref{http://openocd.sourceforge.net/doc/doxygen/html/index.html}
@uref{http://openocd.org/doc/doxygen/html/index.html}

This document is a work-in-progress, but contributions would be welcome
to fill in the gaps. All of the source files are provided in-tree,
@@ -292,7 +292,7 @@ communication between developers:

The OpenOCD Bug Tracker is hosted on SourceForge:

@uref{https://sourceforge.net/p/openocd/tickets/}
@uref{http://bugs.openocd.org/}


@node Debug Adapter Hardware
@@ -735,7 +735,7 @@ If all goes well you'll see output something like
@example
Open On-Chip Debugger 0.4.0 (2010-01-14-15:06)
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
http://openocd.org/doc/doxygen/bugs.html
Info : JTAG tap: lm3s.cpu tap/device found: 0x3ba00477
(mfg: 0x23b, part: 0xba00, ver: 0x3)
@end example


+ 1
- 1
src/openocd.c View File

@@ -328,7 +328,7 @@ int openocd_main(int argc, char *argv[])
return EXIT_FAILURE;

LOG_OUTPUT("For bug reports, read\n\t"
"http://openocd.sourceforge.net/doc/doxygen/bugs.html"
"http://openocd.org/doc/doxygen/bugs.html"
"\n");

command_context_mode(cmd_ctx, COMMAND_CONFIG);


+ 3
- 3
tcl/target/amdm37x.cfg View File

@@ -50,7 +50,7 @@ adapter_khz 10
###############################################################################
# JTAG setup
# The OpenOCD commands are described in the TAP Declaration section
# http://openocd.sourceforge.net/doc/html/TAP-Declaration.html
# http://openocd.org/doc/html/TAP-Declaration.html
###############################################################################

# The AM/DM37x has an ICEPick module in it like many of TI's other devices. More
@@ -61,7 +61,7 @@ source [find target/icepick.cfg]

# The TAP order should be described from the TDO connection in OpenOCD to the
# TDI pin. The OpenOCD FAQ describes this in more detail:
# http://openocd.sourceforge.net/doc/html/FAQ.html
# http://openocd.org/doc/html/FAQ.html

# From SPRUGN4R CH27 the available secondary TAPs are in this order from TDO:
#
@@ -136,7 +136,7 @@ jtag configure $_CHIPNAME.jrc -event setup "jtag tapenable $_CHIPNAME.dap"
###############################################################################
# Target Setup:
# This section is described in the OpenOCD documentation under CPU Configuration
# http://openocd.sourceforge.net/doc/html/CPU-Configuration.html
# http://openocd.org/doc/html/CPU-Configuration.html
###############################################################################

# Create the CPU target to be used with GDB: Cortex-A8, using DAP


Loading…
Cancel
Save