You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2016/06/17 23:39:35 UTC
[50/63] [abbrv] [partial] incubator-mynewt-site git commit: remove
untarred files for openocd
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/BUGS
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/BUGS b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/BUGS
deleted file mode 100755
index 17a7b30..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/BUGS
+++ /dev/null
@@ -1,74 +0,0 @@
-// This file is part of the Doxygen Developer Manual
-/** @page bugs Bug Reporting
-
-Please report bugs by subscribing to the OpenOCD mailing list and
-posting a message with your report:
-
- openocd-devel@lists.sourceforge.net
-
-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.
-
- 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
-items below are unnecessary for a clear bug report, you may leave
-them out; likewise, feel free to include additional information
-that may be important.
-
-- Target PCB/board description
-- Configuration scripts
-- OpenOCD command line
-- List of commands issued or GDB operations performed
-- Expected result
-- Actual result
-- Logs using <code>debug_level 3</code> (or with '-d 3' on the command line)
-- If the report is for a regression:
- - Include logs for both working and broken versions.
- - Find the precise version that caused the regression by binary search.
- You can use "git bisect" to expedite this binary search:
- http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
-
-If possible, please develop and attach a patch that helps to expose or
-solve the reported problem. See the HACKING file for information
-about that process.
-
-Attach all files directly to your posting. The mailing list knows to
-transform attachments to links, but attachments must be less than 300KB
-in total.
-
-@section bugscrashdump Obtaining Crash Backtraces
-
-If OpenOCD is crashing, there are two very effective things you can do to
-improve your chances of getting help on the development mailing list.
-
-Try to reproduce the problem using the dummy JTAG interface to allow other developers to replicate
-your problem robustly and use GDB to get a trace:@par
-@code
-% OPENOCDSRC/configure --enable-dummy ...
-% openocd -f interface/dummy.cfg -f target/xxx.cfg
-=> SEGFAULT
-% gdb --args openocd ....
-(gdb) run
-(gdb) bt
-=> here a stack trace is dumped.
-@endcode
-
-@section bugsintreedebug Running and Debugging In-Tree
-
-To run or debug the in-tree executable (not recommended), you must
-use libtool to set up the correct shared library paths:
-@code
- libtool gdb --args openocd ....
-@endcode
-or the more pedantic (and forward-compatible):
-@code
- libtool --mode=execute gdb --args openocd ....
-@endcode
-
- */
-/** @file
-This file contains the @ref bugs page.
-*/
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/COPYING
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/COPYING b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/COPYING
deleted file mode 100755
index d159169..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/COPYING
+++ /dev/null
@@ -1,339 +0,0 @@
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Lesser General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
-
- How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License along
- with this program; if not, write to the Free Software Foundation, Inc.,
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) year name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/ChangeLog
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/ChangeLog b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/ChangeLog
deleted file mode 100755
index a8df5d0..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/ChangeLog
+++ /dev/null
@@ -1 +0,0 @@
-Retired in favor of git log.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/HACKING
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/HACKING b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/HACKING
deleted file mode 100755
index 162da86..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/HACKING
+++ /dev/null
@@ -1,185 +0,0 @@
-// This file is part of the Doxygen Developer Manual
-/** @page patchguide Patch Guidelines
-
-\attention If you're behind a corporate wall with http only access to the
-world, you can still use these instructions!
-
-\attention You can't send patches to the mailing list anymore at all. Nowadays
-you are expected to send patches to the OpenOCD Gerrit GIT server for a
-review.
-
-@section gerrit Submitting patches to the OpenOCD Gerrit server
-
-OpenOCD is to some extent a "self service" open source project, so to
-contribute, you must follow the standard procedures to have the best
-possible chance to get your changes accepted.
-
-The procedure to create a patch is essentially:
-
-- make the changes
-- create a commit
-- send the changes to the Gerrit server for review
-- correct the patch and re-send it according to review feedback
-
-Your patch (or commit) should be a "good patch": focus it on a single
-issue, and make it be easily reviewable. Don't make
-it so large that it's hard to review; split large
-patches into smaller ones. (That can also help
-track down bugs later on.) All patches should
-be "clean", which includes preserving the existing
-coding style and updating documentation as needed.
-
-Say in the commit message if it's a bugfix (describe the bug) or a new
-feature. Don't expect patches to merge immediately
-for the next release. Be ready to rework patches
-in response to feedback.
-
-Add yourself to the GPL copyright for non-trivial changes.
-
-@section stepbystep Step by step procedure
-
--# Create a Gerrit account at: http://openocd.zylin.com
- - On subsequent sign ins, use the full URL prefaced with 'http://'
- For example: http://user_identifier.open_id_provider.com
- -# Add a username to your profile.
- After creating the Gerrit account and signing in, you will need to
- add a username to your profile. To do this, go to 'Settings', and
- add a username of your choice.
- Your username will be required in step 3 and substituted wherever
- the string 'USERNAME' is found.
- -# Create an SSH public key following the directions on github:
- https://help.github.com/articles/generating-ssh-keys . You can skip step 3
- (adding key to Github account) and 4 (testing) - these are useful only if
- you actually use Github or want to test whether the new key works fine.
- -# Add this new SSH key to your Gerrit account:
- go to 'Settings' > 'SSH Public Keys', paste the contents of
- ~/.ssh/id_rsa.pub into the text field (if it's not visible click on
- 'Add Key ...' button) and confirm by clicking 'Add' button.
--# Clone the git repository, rather than just download the source:
- @code
- git clone git://git.code.sf.net/p/openocd/code openocd
- @endcode
- or if you have problems with the "git:" protocol, use
- the slower http protocol:
- @code
- git clone http://git.code.sf.net/p/openocd/code openocd
- @endcode
--# Set up Gerrit with your local repository. All this does it
-to instruct git locally how to send off the changes.
- -# Add a new remote to git using Gerrit username:
-@code
-git remote add review ssh://USERNAME@openocd.zylin.com:29418/openocd.git
-git config remote.review.push HEAD:refs/publish/master
-@endcode
- Or with http only:
-@code
-git remote add review http://USERNAME@openocd.zylin.com/p/openocd.git
-git config remote.review.push HEAD:refs/publish/master
-@endcode
- The http password is configured from your gerrit settings - http://openocd.zylin.com/#/settings/http-password.
- \note If you want to simplify http access you can also add your http password to the url as follows:
-@code
-git remote add review http://USERNAME:PASSWORD@openocd.zylin.com/p/openocd.git
-@endcode
- -# You will need to install this hook, we will look into a better solution:
-@code
-scp -p -P 29418 USERNAME@openocd.zylin.com:hooks/commit-msg .git/hooks/
-@endcode
- Or with http only:
-@code
-wget http://openocd.zylin.com/tools/hooks/commit-msg
-mv commit-msg .git/hooks
-chmod +x .git/hooks/commit-msg
-@endcode
- \note A script exists to simplify the two items above. execute:
-@code
-tools/initial.sh <username>
-@endcode
-With @<username@> being your Gerrit username.
--# Set up git with your name and email:
-@code
-git config --global user.name "John Smith"
-git config --global user.email "john@smith.org"
-@endcode
--# Work on your patches. Split the work into
- multiple small patches that can be reviewed and
- applied seperately and safely to the OpenOCD
- repository.
-@code
-while(!done) {
- work - edit files using your favorite editor.
- run "git commit -s -a" to commit all changes.
- run tools/checkpatch.sh to verify your patch style is ok.
-}
-@endcode
- \note use "git add ." before commit to add new files.
-
- Comment template, notice the short first line w/topic. The topic field
- should identify the main part or subsystem the patch touches. Check
- git log for examples.
-@code
-topic: Short comment
-<blank line>
-Longer comments over several lines, explaining (where applicable) the
-reason for the patch and the general idea the solution is based on,
-any major design decisions, etc...
-<blank line>
-Signed-off-by: ...
-@endcode
--# Next you need to make sure that your patches
- are on top of the latest stuff on the server and
- that there are no conflicts:
-@code
-git pull --rebase origin master
-@endcode
--# Send the patches to the Gerrit server for review:
-@code
-git push review
-@endcode
--# Forgot something, want to add more? Just make the changes and do:
-@code
-git commit --amend
-git push review
-@endcode
-
-Further reading: http://www.coreboot.org/Git
-
-@section timeline When can I expect my contribution to be committed?
-
-The code review is intended to take as long as a week or two to allow
-maintainers and contributors who work on OpenOCD only in their spare
-time oportunity to perform a review and raise objections.
-
-With Gerrit much of the urgency of getting things committed has been
-removed as the work in progress is safely stored in Gerrit and
-available if someone needs to build on your work before it is
-submitted to the official repository.
-
-Another factor that contributes to the desire for longer cool-off
-times (the time a patch lies around without any further changes or
-comments), it means that the chances of quality regression on the
-master branch will be much reduced.
-
-If a contributor pushes a patch, it is considered good form if another
-contributor actually approves and submits that patch.
-
-It should be noted that a negative review in Gerrit ("-1" or "-2") may (but does
-not have to) be disregarded if all conditions listed below are met:
-
-- the concerns raised in the review have been addressed (or explained),
-- reviewer does not re-examine the change in a month,
-- reviewer does not answer e-mails for another month.
-
-@section browsing Browsing Patches
-All OpenOCD patches can be reviewed <a href="http://openocd.zylin.com/">here</a>.
-
-@section reviewing Reviewing Patches
-From the main <a href="http://openocd.zylin.com/#/q/status:open,n,z">Review
-page</a> select the patch you want to review and click on that patch. On the
-appearing page select the download method (top right). Apply the
-patch. After building and testing you can leave a note with the "Reply"
-button and mark the patch with -1, 0 and +1.
-*/
-/** @file
-This file contains the @ref patchguide page.
-*/
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/Makefile.am
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/Makefile.am b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/Makefile.am
deleted file mode 100755
index 2ddc96d..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/Makefile.am
+++ /dev/null
@@ -1,112 +0,0 @@
-# not a GNU package. You can remove this line, if
-# have all needed files, that a GNU package needs
-AUTOMAKE_OPTIONS = gnu 1.6
-
-# make sure we pass the correct jimtcl flags to distcheck
-DISTCHECK_CONFIGURE_FLAGS = --disable-install-jim
-
-nobase_dist_pkgdata_DATA = \
- contrib/libdcc/dcc_stdio.c \
- contrib/libdcc/dcc_stdio.h \
- contrib/libdcc/example.c \
- contrib/libdcc/README \
- contrib/99-openocd.rules
-
-if INTERNAL_JIMTCL
-SUBDIRS = jimtcl
-else
-SUBDIRS =
-endif
-
-SUBDIRS += src doc
-
-EXTRA_DIST = \
- BUGS \
- HACKING \
- NEWTAPS \
- README.Windows \
- README.OSX \
- $(wildcard $(srcdir)/NEWS*) \
- Doxyfile.in \
- tools/logger.pl \
- tools/rlink_make_speed_table \
- tools/st7_dtc_as \
- contrib
-
-libtool: $(LIBTOOL_DEPS)
- $(SHELL) ./config.status --recheck
-
-docs: pdf html doxygen
-
-Doxyfile: $(srcdir)/Doxyfile.in
- @echo "Creating $@ from $<..."
- @( \
- echo "### @@@ -= DO NOT EDIT THIS FILE =- @@@ ###" && \
- echo "### @@@ Make changes to Doxyfile.in @@@ ###" && \
- sed -e 's,@srcdir\@,$(srcdir),' \
- -e 's,@builddir\@,$(builddir),' \
- -e 's,@doxygen_as_html\@,$(doxygen_as_html),' \
- -e 's,@doxygen_as_pdf\@,$(doxygen_as_pdf),' $< \
- ) > $@
-
-THE_MANUAL = doxygen/latex/refman.pdf
-
-doxygen::
- $(MAKE) Doxyfile
- doxygen Doxyfile 2>&1 | perl $(srcdir)/tools/logger.pl > doxygen.log
- @if [ -f doxygen/latex/refman.tex ]; then \
- echo "Creating $(THE_MANUAL)..."; \
- $(MAKE) $(THE_MANUAL); \
- else \
- echo "Skipping Doxygen PDF..."; \
- fi
-
-$(THE_MANUAL): %.pdf: %.tex
- -cd $$(dirname $*) && pdflatex $$(basename $*)
- -cd $$(dirname $*) && pdflatex $$(basename $*)
-
-TCL_PATH = tcl
-# command to find paths of script files, relative to TCL_PATH
-TCL_FILES = find $(srcdir)/$(TCL_PATH) -name '*.cfg' -o -name '*.tcl' -o -name '*.txt' | \
- sed -e 's,^$(srcdir)/$(TCL_PATH),,'
-
-dist-hook:
- if test -d $(srcdir)/.git -a \( ! -e $(distdir)/ChangeLog -o -w $(distdir)/ChangeLog \) ; then \
- git --git-dir $(srcdir)/.git log | $(srcdir)/tools/git2cl/git2cl > $(distdir)/ChangeLog ; \
- fi
- for i in $$($(TCL_FILES)); do \
- j="$(distdir)/$(TCL_PATH)/$$i" && \
- mkdir -p "$$(dirname $$j)" && \
- $(INSTALL_DATA) $(srcdir)/$(TCL_PATH)/$$i $$j; \
- done
-
-install-data-hook:
- for i in $$($(TCL_FILES)); do \
- j="$(DESTDIR)$(pkgdatadir)/scripts/$$i" && \
- mkdir -p "$$(dirname $$j)" && \
- $(INSTALL_DATA) $(srcdir)/$(TCL_PATH)/$$i $$j; \
- done
-
-uninstall-hook:
- rm -rf $(DESTDIR)$(pkgdatadir)/scripts
-
-distclean-local:
- rm -rf Doxyfile doxygen
- rm -f $(srcdir)/jimtcl/configure.gnu
-
-DISTCLEANFILES = doxygen.log
-
-MAINTAINERCLEANFILES = \
- $(srcdir)/INSTALL \
- $(srcdir)/configure \
- $(srcdir)/Makefile.in \
- $(srcdir)/depcomp \
- $(srcdir)/config.guess \
- $(srcdir)/config.sub \
- $(srcdir)/config.h.in \
- $(srcdir)/config.h.in~ \
- $(srcdir)/compile \
- $(srcdir)/ltmain.sh \
- $(srcdir)/missing \
- $(srcdir)/aclocal.m4 \
- $(srcdir)/install-sh
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS
deleted file mode 100755
index 9df1650..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS
+++ /dev/null
@@ -1,33 +0,0 @@
-This file includes highlights of the changes made in the OpenOCD
-source archive release.
-
-JTAG Layer:
-
-Boundary Scan:
-
-Target Layer:
-
-Flash Layer:
-
-Board, Target, and Interface Configuration Scripts:
-
-Server Layer:
-
-Documentation:
-
-Build and Release:
-
-
-This release also contains a number of other important functional and
-cosmetic bugfixes. For more details about what has changed since the
-last release, see the git repository history:
-
-http://sourceforge.net/p/openocd/code/ci/v0.x.0/log/?path=
-
-
-For older NEWS, see the NEWS files associated with each release
-(i.e. NEWS-<version>).
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES.txt files in the source archive).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.2.0
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.2.0 b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.2.0
deleted file mode 100755
index 7426926..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.2.0
+++ /dev/null
@@ -1,80 +0,0 @@
-The OpenOCD 0.2.0 source archive release includes numerous improvements
-that were made since the initial 0.1.0 source archive release. Many
-contributors helped make this release a great success, and the community
-of developers and maintainers look forward to any response.
-
-In addition to the list of changes below, countless bug fixing and
-cleaning was performed across the tree. Various TCL command parameters
-must past stricter value checks, and many more error conditions have
-been handled correctly. These efforts helped to make the 0.2.0 release
-more stable and robust, though some changes may expose latent bugs in
-your existing configuration scripts.
-
-This release does not maintain backward compatibility in all respects,
-so some target or configuration scripts may need to be updated. In some
-cases, you may also see warnings; resolve those, because they indicate
-commands that will be removed in the future.
-
-The following areas of OpenOCD functionality changed in this release:
-
-JTAG Layer:
-- Improves modularity: core, TCL, driver commands, and interface have
- been separated, encapsulated, and documented for developers. Mostly.
-- Improves JTAG TAP transition tables:
- * Makes TAP paths variable length, rather than being fixed at 7 steps.
- * Fixes problems with some targets that did not like longer paths.
-- Improves JTAG driver/minidriver modularity and encapsulation.
-- New drivers:
- * Adds stub minidriver for developing new embedded JTAG interfaces.
-- Improves drivers:
- * ft2232+ftd2xx:
- + Adds initial high-speed device support: --enable-ftd2xx-highspeed
- + Supports more types of FTDI-based devices.
- * jlink:
- + Works with more versions of the firmware (v3 and newer)
- + Supports dynamically detects device capabilities and limits
- * vsllink:
- + Supports very long scan chains
- * amtjtagaccel:
- + Fixes broken ID code detection problems.
-
-Target Layer:
-- New devices: AVR, FA526
-- Improved support: ARM ADI, ARM11, MIPS
-- Numerous other bug fixes and improvements
-
-Flash Layer:
-- Improved drivers: mflash
-- New drivers: AT91SAM3, AVR, Davinci NAND
-
-Board, Interface, and Target Configuration Scripts:
-- Many new and improved targets and boards are now available.
-- Better separation of "board" and "target" configuration
-- Moved all TCL files to top-level "tcl" directory in the source tree
-- Installation moved from '$pkglibdir/' to '$pkgdatadir/scripts/'.
-- Site-specific files should be installed under '$pkgdatadir/site/';
- files that exist this tree will be used in preference to default
- distribution configurations in '$pkgdatadir/scripts/'.
-
-Documentation:
-- Updated User Guide: http://openocd.berlios.de/doc/html/index.html
- * Partially re-written and re-organized.
- * Standardized presentation for all commands.
- * Covers many drivers and commands that were previously omitted.
- * New index for commands and drivers.
-- Added Developer Manual: http://openocd.berlios.de/doc/doxygen/index.html
- * Now includes architecture, technical primers, style guides, and more.
- * Available in-tree and on-line.
-
-Build and Release:
-- Increased configuration and compilation warning coverage.
- * Use --disable-werror to work around build errors caused by warnings.
-- Use libtool to produce helper libraries as a step toward "libopenocd".
-- New processes and scripting to facilitate future source releases.
-
-For more details about what has changed since 0.1.0, see the ChangeLog
-associated with this release.
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES files in the source archive).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.3.0
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.3.0 b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.3.0
deleted file mode 100755
index 80e8823..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.3.0
+++ /dev/null
@@ -1,82 +0,0 @@
-This file should include highlights of the changes made in the
-OpenOCD openocd-0.3.0 source archive release. See the repository
-history for details about what changed, including bugfixes and
-other issues not mentioned here.
-
-JTAG Layer:
- FT2232H (high speed USB) support doesn't need separate configuration
- New FT2232H JTAG adapters: Amontec, Olimex, Signalyzer
- New reset_config options for SRST gating the JTAG clock (or not)
- TAP declaration no longer requires ircapture and mask attributes
- Scan chain setup should be more robust, with better diagnostics
- New TAP events:
- "post-reset" for TAP-invariant setup code (TAPs not usable yet)
- "setup" for use once TAPs are addressable (e.g. with ICEpick)
- Overridable Tcl "init_reset" and "jtag_init" procedures
- Simple "autoprobe" mechanism to help simplify server setup
-
-Boundary Scan:
- SVF bugfixes ... parsing fixes, better STATE switch conformance
- XSVF bugfixes ... be more correct, handle Xilinx tool output
-
-Target Layer:
- Warn on use of obsolete numeric target IDs
- New commands for use with Cortex-M3 processors:
- "cortex_m3 disassemble" ... Thumb2 disassembly (UAL format)
- "cortex_m3 vector_catch" ... traps certain hardware faults
- without tying up breakpoint resources
- If you're willing to help debug it
- VERY EARLY Cortex-A8 and ARMv7A support
- Updated BeagleBoard.org hardware support
- you may need to explicitly "reset" after connect-to-Beagle
- New commands for use with XScale processors: "xscale vector_table"
- ARM
- bugfixes to single-stepping Thumb code
- ETM: unavailable registers are not listed
- ETB, ETM: report actual hardware status
- ARM9
- name change: "arm9 vector_catch" not "arm9tdmi vector_catch"
- ARM11
- single stepping support for i.MX31
- bugfix for missing "arm11" prefix on "arm11 memwrite ..."
- GDB support
- gdb_attach command is gone
-
-Flash Layer:
- The lpc2000 driver handles the new NXP LPC1700 (Cortex-M3) chips
- New drivers:
- lpc2900, for NXP LPC2900 chips (ARM968 based)
- mx3_nand, for imx31
- New "last" flag for NOR "flash erase_sector" and "flash protect"
- The "nand erase N" command now erases all of bank N
- Speed up davinci_nand by about 3x
-
-Board, Target, and Interface Configuration Scripts:
- Amontec JTAGkey2 support
- Cleanup and additions for the TI/Luminary Stellaris scripts
- LPC1768 target (and flash) support
- Keil MCB1700 eval board
- Samsung s3c2450
- Mini2440 board
- Numeric TAP and Target identifiers now trigger warnings
- PXA255 partially enumerates
-
-Documentation:
- Capture more debugging and setup advice
- Notes on target source code changes that may help debugging
-
-Build and Release:
- Repository moved from SVN at Berlios to GIT at SourceForge
- Clean builds on (32-bit) Cygwin
- Clean builds on 64-bit MinGW
-
-For more details about what has changed since the last release,
-see the git repository history. With gitweb, you can browse that
-in various levels of detail.
-
-For older NEWS, see the NEWS files associated with each release
-(i.e. NEWS-<version>).
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES files in the source archive).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.4.0
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.4.0 b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.4.0
deleted file mode 100755
index cbd5526..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.4.0
+++ /dev/null
@@ -1,98 +0,0 @@
-This file includes highlights of the changes made in the
-OpenOCD 0.4.0 source archive release. See the repository
-history for details about what changed, including bugfixes
-and other issues not mentioned here.
-
-JTAG Layer:
- Support KT-Link JTAG adapter.
- Support USB-JTAG, Altera USB-Blaster and compatibles.
-
-Boundary Scan:
-
-Target Layer:
- General
- - Removed commands which have been obsolete for at least
- a year (from both documentation and, sometimes, code).
- - new "reset-assert" event, for systems without SRST
- ARM
- - supports "reset-assert" event (except on Cortex-M3)
- - renamed "armv4_5" command prefix as "arm"
- - recognize TrustZone "Secure Monitor" mode
- - "arm regs" command output changed
- - register names use "sp" not "r13"
- - add top-level "mcr" and "mrc" commands, replacing
- various core-specific operations
- - basic semihosting support (ARM7/ARM9 only, for now)
- ARM11
- - Should act much more like other ARM cores:
- * Preliminary ETM and ETB hookup
- * accelerated "flash erase_check"
- * accelerated GDB memory checksum
- * support "arm regs" command
- * can access all core modes and registers
- * watchpoint support
- - Shares some core debug code with Cortex-A8
- Cortex-A8
- - Should act much more like other ARM cores:
- * support "arm regs" command
- * can access all core modes and registers
- * watchpoint support
- - Shares some core debug code with ARM11
- Cortex-M3
- - Exposed DWT registers like cycle counter
- - vector_catch settings not clobbered by resets
- - no longer interferes with firmware's fault handling
- ETM, ETB
- - "trigger_percent" command moved ETM --> ETB
- - "etm trigger_debug" command added
- MIPS
- - use fastdata writes
- Freescale DSP563xx cores (partial support)
-
-Flash Layer:
- 'flash bank' and 'nand device' take <bank_name> as first argument.
- With this, flash/NAND commands allow referencing banks by name:
- - <bank_name>: reference the bank with its defined name
- - <driver_name>[.N]: reference the driver's Nth bank
- New 'nand verify' command to check bank against an image file.
- The "flash erase_address" command now rejects partial sectors;
- previously it would silently erase extra data. If you
- want to erase the rest of the first and/or last sectors
- instead of failing, you must pass an explicit "pad" flag.
- New at91sam9 NAND controller driver.
- New s3c64xx NAND controller driver.
-
-Board, Target, and Interface Configuration Scripts:
- ARM9
- - ETM and ETB hookup for iMX2* targets
- Add $HOME/.openocd to the search path.
- Handle Rev C of LM3S811 eval boards.
- - use "luminary-lm3s811.cfg" for older boards
- - use "luminary.cfg" for RevC and newer
-
-Core Jim/TCL Scripting:
- New 'usage' command to provide terse command help.
- Improved command 'help' command output (sorted and indented).
- Improved command handling:
- - Most boolean settings now accept any of the following:
- on/off, enable/disable, true/false, yes/no, 1/0
- - More error checking and reporting.
-
-Documentation:
- New built-in command development documentation and primer.
-
-Build and Release:
- Use --enable-doxygen-pdf to build PDF developer documentation.
- Consider upgrading to libftdi 0.17 if you use that library; it
- includes bugfixes which improve FT2232H support.
-
-For more details about what has changed since the last release,
-see the git repository history. With gitweb, you can browse that
-in various levels of detail.
-
-For older NEWS, see the NEWS files associated with each release
-(i.e. NEWS-<version>).
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES.txt files in the source archive).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.5.0
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.5.0 b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.5.0
deleted file mode 100755
index add6c1e..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.5.0
+++ /dev/null
@@ -1,74 +0,0 @@
-This file includes highlights of the changes made in the
-OpenOCD 0.5.0 source archive release. See the repository
-history for details about what changed, including bugfixes
-and other issues not mentioned here.
-
-JTAG Layer:
- New driver for "Bus Pirate"
- Rename various commands so they're not JTAG-specific
- There are migration procedures for most of these, but you should
- convert your scripts to the new names, since those procedures
- will not be around forever.
- jtag jinterface ... is now adapter_name
- jtag_khz ... is now adapter_khz
- jtag_nsrst_delay ... is now adapter_nsrst_delay
- jtag_nsrst_assert_width ... is now adapter_nsrst_assert_width
- Support Voipac VPACLink JTAG Adapter.
-
-Boundary Scan:
-
-Transport framework core ... supporting future work for SWD, SPI, and other
-non-JTAG ways to debug targets or program flash.
-
-Target Layer:
- ARM:
- - basic semihosting support for ARMv7M.
- - renamed "armv7m" command prefix as "arm"
- MIPS:
- - "ejtag_srst" variant removed. The same functionality is
- obtained by using "reset_config none".
- - added PIC32MX software reset support, this means srst is not
- required to be connected anymore.
- OTHER:
- - preliminary AVR32 AP7000 support.
-
-Flash Layer:
- New "stellaris recover" command, implements the procedure
- to recover locked devices (restoring non-volatile
- state to the factory defaults, including erasing
- the flash and its protection bits, and possibly
- re-enabling hardware debugging).
- PIC32MX now uses algorithm for flash programming, this
- has increased the performance by approx 96%.
- New 'pic32mx unlock' cmd to remove readout protection.
- New STM32 Value Line Support.
- New 'virtual' flash driver, used to associate other addresses
- with a flash bank. See pic32mx.cfg for usage.
- New iMX27 NAND flash controller driver.
-
-Board, Target, and Interface Configuration Scripts:
- Support IAR LPC1768 kickstart board (by Olimex)
- Support Voipac PXA270/PXA270M module.
- New $PARPORTADDR tcl variable used to change default
- parallel port address used.
- Remove lm3s811.cfg; use "stellaris.cfg" instead
-
-Core Jim/TCL Scripting:
- New "add_script_search_dir" command, behaviour is the same
- as the "-s" cmd line option.
-
-Documentation:
-
-Build and Release:
-
-For more details about what has changed since the last release,
-see the git repository history. With gitweb, you can browse that
-in various levels of detail.
-
-For older NEWS, see the NEWS files associated with each release
-(i.e. NEWS-<version>).
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES.txt files in the source archive).
-
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.6.0
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.6.0 b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.6.0
deleted file mode 100755
index 0acd242..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.6.0
+++ /dev/null
@@ -1,54 +0,0 @@
-This file includes highlights of the changes made in the
-OpenOCD source archive release. See the
-repository history for details about what changed, including
-bugfixes and other issues not mentioned here.
-
-JTAG Layer:
- New STLINK V1/V2 JTAG/SWD adapter support.
- New OSJTAG adapter support.
- New Tincantools Flyswatter2 support.
- Improved ULINK driver.
- Improved RLINK driver.
- Support for adapters based on FT232H chips.
- New experimental driver for FTDI based adapters, using libusb-1.0 in asynchronous mode.
-
-Boundary Scan:
-
-Target Layer:
- New Cortex-M0 support.
- New Cortex-M4 support.
- Improved Working area algorithm.
- New RTOS support. Currently linux, FreeRTOS, ThreadX and eCos.
- Connecting under reset to Cortex-Mx and MIPS chips.
-
-Flash Layer:
- New SST39WF1601 support.
- New EN29LV800BB support.
- New async algorithm support for selected targets, stm32, stellaris and pic32.
- New Atmel SAM3S, SAM3N support.
- New ST STM32L support.
- New Microchip PIC32MX1xx/2xx support.
- New Freescale Kinetis K40 support.
-
-Board, Target, and Interface Configuration Scripts:
- Support Dangerous Prototypes Bus Blaster.
- Support ST SPEAr Family.
- Support Gumstix Verdex boards.
- Support TI Beaglebone.
-
-Documentation:
- Improved HACKING info for submitting patches.
- Fixed numerous broken links.
-
-Build and Release:
-
-For more details about what has changed since the last release,
-see the git repository history. With gitweb, you can browse that
-in various levels of detail.
-
-For older NEWS, see the NEWS files associated with each release
-(i.e. NEWS-<version>).
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES.txt files in the source archive).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.7.0
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.7.0 b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.7.0
deleted file mode 100755
index 47a8fa6..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.7.0
+++ /dev/null
@@ -1,43 +0,0 @@
-This file includes highlights of the changes made in the
-OpenOCD source archive release. See the
-repository history for details about what changed, including
-bugfixes and other issues not mentioned here.
-
-JTAG Layer:
- New TI ICDI adapter support.
- Support Latest OSBDM firmware.
- Improved MIPS EJTAG Support.
-
-Boundary Scan:
-
-Target Layer:
- New ARMv7R and Cortex-R4 support.
- Added ChibiOS/RT support.
-
-Flash Layer:
- New NXP LPC1850 support.
- New NXP LPC4300 support.
- New NXP SPIFI support.
- New Energy Micro EFM32 support.
- New ST STM32W support.
- New ST STM32f2 write protection and lock/unlock support.
- Ability to override STM32 flash bank size.
-
-Board, Target, and Interface Configuration Scripts:
- Support Freescale i.MX6 series targets.
-
-Documentation:
- New MIPS debugging info.
-
-Build and Release:
-
-For more details about what has changed since the last release,
-see the git repository history. With gitweb, you can browse that
-in various levels of detail.
-
-For older NEWS, see the NEWS files associated with each release
-(i.e. NEWS-<version>).
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES.txt files in the source archive).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.8.0
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.8.0 b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.8.0
deleted file mode 100755
index 33b3af4..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.8.0
+++ /dev/null
@@ -1,111 +0,0 @@
-This file includes highlights of the changes made in the OpenOCD
-source archive release.
-
-JTAG Layer:
- * New CMSIS-DAP driver
- * Andes AICE debug adapter support
- * New OpenJTAG driver
- * New BCM2835 (RaspberryPi) driver
- * JTAG VPI client driver (for OpenRISC Reference Platform SoC)
- * Xilinx BSCAN_* for OpenRISC support
- * ST-LINKv2-1 support
- * ST-LINKv2 SWO tracing support (UART emulation)
- * JLink-OB (onboard) support
- * Altera USB Blaster driver rewrite, initial Blaster II
- support
- * ULINK driver ported to libusb-1.0, OpenULINK build fixes
- * Support up to 64 bit IR lengths
- * SVF playback (FPGA programming) fixes
- * "ftdi" interface driver got extensive testing and is now
- recommended over the old ft2232 implementation
-
-Boundary Scan:
-
-Target Layer:
- * New target: Andes nds32
- * New target: OpenRISC OR1K
- * New target: Intel Quark X10xx
- * MIPS EJTAG 1.5/2.0 support
- * MIPS speed improvements
- * Cortex-M, Cortex-A (MEM-AP, APB-AP) targets working with BE
- hosts now
- * XScale vector_catch support, reset fixes
- * dsp563xx ad-hoc breakpoint/watchpoint support
- * RTOS support for embKernel
- * Target profiling improvements
- * Memory access functions testbench
-
-Flash Layer:
- * STM32 family sync with reference manuals, other bugfixes
- * STM32F401, STM32F07x support
- * Atmel SAM4L, SAMG5x support
- * at91sam3sd8{a,b}, at91sam3s8{a,b,c}, at91sam4s,
- at91sam3n0{a,b,0a,0b} support, bugfixes
- * Atmel SAMD support
- * Milandr 1986\u0412\u0415* support
- * Kinetis KL, K21 support
- * Nuvoton NuMicro MINI5{1,2,4} support
- * Nuvoton NUC910 series support
- * NXP LPC43xx, LPC2000 fixes
- * NXP LPC800, LPC810 support
- * More ATmega parts supported
- * Fujitsu MB9Ax family support
- * EFM32 Wonder Gecko family support
- * Nordic nRF51 support
-
-Board, Target, and Interface Configuration Scripts:
- * STM32W108xx generic target config
- * STM32F429 discovery board config
- * STM32 Nucleo boards configs
- * DENX M53EVK board config
- * Altera Cyclone V SoC, SoCkit config
- * New TI Launchpads board configs
- * TI am43xx devices, AM437x GP EVM, AM438x ePOS EVM board
- configs
- * Marvell Armada 370 family initial support
- * TI TMDX570LS31USB (TMS570, Cortex-R4) support scripts
- * Freescale FRDM-KL25Z, KL46Z board configs
- * Digilent Zedboard config
- * Asus RT-N16, Linksys WRT54GL, BT HomeHub board configs
- * Atmel Xplained initial support
- * Broadcom bcm28155_ap board config
- * TUMPA, TUMPA Lite interface configs
- * Digilent JTAG-SMT2 interface config
- * New RAM testing functions
- * Easy-to-use firmware recovery helpers targetting ordinary
- users with common equipment
-
-Server Layer:
- * Auto-generation of GDB target description for ARMv7-M,
- ARM4, nds32, OR1K, Quark
- * GDB File-I/O Remote Protocol extension support
- * Default GDB flashing events handlers to initialise and reset
- the target automatically when "load" is used
-
-Documentation:
- * Extensive README* changes
- * The official User's Guide was proofread
- * Example cross-build script
- * RTOS documentation improvements
- * Tcl RPC documentation and examples added
-
-Build and Release:
- * *BSD, OS X, clang, ARM, windows build fixes
- * New pkg-config support changes the way libusb (and other
- dependencies) are handled. Many adapter drivers are now
- selected automatically during the configure stage.
-
-
-This release also contains a number of other important functional and
-cosmetic bugfixes. For more details about what has changed since the
-last release, see the git repository history:
-
-http://sourceforge.net/p/openocd/code/ci/v0.8.0/log/?path=
-
-
-For older NEWS, see the NEWS files associated with each release
-(i.e. NEWS-<version>).
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES.txt files in the source archive).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.9.0
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.9.0 b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.9.0
deleted file mode 100755
index 77ae4b0..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWS-0.9.0
+++ /dev/null
@@ -1,110 +0,0 @@
-This file includes highlights of the changes made in the OpenOCD
-source archive release.
-
-JTAG Layer:
- * SWD support with FTDI, Versaloon, J-Link, sysfsgpio
- * CMSIS-DAP massive speed and stability improvements
- * Versaloon driver ported to libusb-1.0
- * STLink can reestablish communication with a target that was
- disconnected or rebooted
- * STLink FAULT and WAIT SWD handling improved
- * New hla_serial command to distinguish between several HLA
- adapters attached to a single machine
- * Serial number support for CMSIS-DAP and J-Link adapters
- * Support for more J-Link adapters
- * TAP autoprobing improvements
- * Big speedup for SVF playback with USB Blaster
-
-Boundary Scan:
-
-Target Layer:
- * Stability improvements for targets that get disconnected or
- rebooted during a debug session
- * MIPS speed and reliability improvements
- * MIPS 1.5/2.0 fixes
- * ARMv7-R improvements
- * Cortex-A improvements, A7, A15 MPCores support
- * FPU support for ARMv7-M (Cortex-M4F)
- * TPIU/ITM support (including SWO/SWV tracing), can be
- captured with external tools or STLink
- * JTAG Serial Port (Advanced Debug System softcore) support
- * Profiling support for OpenRISC
- * ChibiOS/RT 3.0 support (with and without FPU)
- * FreeRTOS current versions support
- * Freescale MQX RTOS support
- * GDB target description support for MIPS
- * The last created target is auto-selected as the current
-
-Flash Layer:
- * nRF51 async loader to improve flashing performance and stability
- * Cypress PSoC 41xx/42xx and CCG1 families flash driver
- * Silabs SiM3 family flash driver
- * Marvell Wireless Microcontroller SPI flash driver
- * Kinetis mass erase (part unsecuring) implemented
- * lpcspifi stability fixes
- * STM32 family sync with reference manuals, L0 support, bugfixes
- * LPC2000 driver automatically determines part and flash size
- * NXP LPC11(x)xx, LPC13xx, LPC15xx, LPC8xx, LPC5410x, LPC407x support
- * Atmel SAMD, SAMR, SAML21 devices support
- * Atmel SAM4E16 support
- * ZeroGecko family support
- * TI Tiva C Blizzard and Snowflake families support
- * Nuvoton NuMicro M051 support
- * EZR32 support in EFM32 driver
-
-Board, Target, and Interface Configuration Scripts:
- * Normal target configs can work with HLA (STLink, ICDI) adapters
- * STM32 discovery and Nucleo boards configs
- * Gumstix AeroCore board config
- * General Plus GP326XXXA target config
- * Micrel KS869x target config
- * ASUS RT-N66U board config
- * Atmel SAM4E-EK board config
- * Atmel AT91SAM4L proper reset handling implemented
- * TI OMAP/AM 3505, 3517 target configs
- * nRF51822-mKIT board config
- * RC Module \u041a1879\u0425\u04111\u042f target config
- * TI TMDX570LS20SUSB board config
- * TI TMS570 USB Kit board config
- * TI CC2538, CC26xx target configs
- * TI AM437x major config improvements, DDR support
- * TI AM437X IDK board config
- * TI SimpleLink Wi-Fi CC3200 LaunchPad configs
- * Silicon Labs EM357, EM358 target configs
- * Infineon XMC1000, XMC4000 family targets and boards configs
- * Atheros AR9331 target config
- * TP-LINK TL-MR3020 board config
- * Alphascale asm9260t target and eval kit configs
- * Olimex SAM7-LA2 (AT91SAM7A2) board config
- * EFM32 Gecko boards configs
- * Spansion FM4 target and SK-FM4-176L-S6E2CC board configs
- * LPC1xxx target configs were restructured
- * IoT-LAB debug adapter config
- * DP BusBlaster KT-Link compatible config
-
-Server Layer:
- * Polling period can be configured
- * "shutdown" command has an immediate effect
- * The "program" command doesn't lead to a shutdown by
- default, use optional "exit" parameter for the old behaviour
- * Proper OS signal handling was implemented
- * Async target notifications for the Tcl RPC
-
-Documentation:
-
-Build and Release:
-
-
-This release also contains a number of other important functional and
-cosmetic bugfixes. For more details about what has changed since the
-last release, see the git repository history:
-
-http://sourceforge.net/p/openocd/code/ci/v0.9.0/log/?path=
-
-
-For older NEWS, see the NEWS files associated with each release
-(i.e. NEWS-<version>).
-
-For more information about contributing test reports, bug fixes, or new
-features and device support, please read the new Developer Manual (or
-the BUGS and PATCHES.txt files in the source archive).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWTAPS
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWTAPS b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWTAPS
deleted file mode 100755
index 638fa00..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/NEWTAPS
+++ /dev/null
@@ -1,145 +0,0 @@
-Reporting Unknown JTAG TAP IDS
-------------------------------
-
-If OpenOCD reports an UNKNOWN or Unexpected Tap ID please report it to
-the development mailing list - However - keep reading.
-
-openocd-devel@lists.sourceforge.net.
-
-========================================
-
-About "UNEXPECTED" tap ids.
-
- Before reporting an "UNEXPECTED TAP ID" - take a closer look.
- Perhaps you have your OpenOCD configured the wrong way, maybe you
- have the tap configured the wrong way? Or something else is wrong.
- (Remember: OpenOCD does not stop if the tap is not present)
-
- This "tap id check" is there for a purpose.
- The goal is to help get the *right* configuration.
-
-The idea is this:
-
- Every JTAG tap is suppose to have "a unique 32bit tap id" number.
- They are suppose to be "sort of unique" but they are not. There are
- no guarantees.
-
-Version Number Changes:
-
- Sometimes, the tap ID only differs by VERSION number. If so - it's
- not a big deal. Please do report this information. We'd like to
- know about it.
-
- For example
-
-Error: ERROR: Tap: s3c4510.cpu - Expected id: 0x3f0f0f0f, Got: 0x1f0f0f0f
-Error: ERROR: expected: mfg: 0x787, part: 0xf0f0, ver: 0x3
-Error: ERROR: got: mfg: 0x787, part: 0xf0f0, ver: 0x1
-
-========================================
-
-Updating the Tap ID number your self
-
- Why do this? You just want the warning to go away. And don't want
- to update your version/instance of OpenOCD.
-
- On simple systems, to fix this problem, in your "openocd.cfg" file,
- override the tap id. Depending on the tap, add one of these 3
- commands:
-
- set CPUTAPID newvalue
- or set BSTAPID newvalue
- or set FLASHTAPID newvalue
- or set ETMTAPID newvalue
-
- Where "newvalue" is the new value you are seeing.
-
- On complex systems, (with many taps and chips) you probably have a
- custom configuration file. Its is more complicated, you're going to
- have to read through the configuration files
-
-========================================
-
-What to send:
-
-Cut & paste the output of OpenOCD that pointed you at this file.
-
-Please include the VERSION number of OpenOCD you are using.
-
-And please include the information below.
-
-========================================
-
-A) The JTAG TAP ID code.
-
-This is always a 32bit hex number.
-
-Examples:
- 0x1f0f0f0f - is an old ARM7TDMI
- 0x3f0f0f0f - is a newer ARM7TDMI
- 0x3ba00477 - is an ARM cortex M3
-
-Some chips have multiple JTAG taps - be sure to list
-each one individually - ORDER is important!
-
-========================================
-B) The maker of the part
-
-Examples:
- Xilinx, Atmel, ST Micro Systems, Freescale
-
-========================================
-C) The family of parts it belongs to
-
-Examples:
- "NXP LPC Series"
- "Atmel SAM7 Series"
-
-========================================
-
-D) The actual part number on the package
-
- For example: "S3C45101x01"
-
-========================================
-
-E) What type of board it is.
-
-ie: a "commercial off the self eval board" that one can purchase (as
-opposed to your private internal custom board)
-
-For example: ST Micro systems has Eval boards, so does Analog Devices
-
-Or - if it is inside something "hackers like to hack" that information
-is helpful too.
-
-For example: A consumer GPS unit or a cellphone
-
-========================================
-
-(F) The maker of the board
- ie: Olimex, LogicPD, Freescale(eval board)
-
-========================================
-
-(G) Identifying information on the board.
-
- Not good: "iar red ST eval board"
-
- Really good: "IAR STR912-SK evaluation board"
-
-========================================
-
-(H) Are there other interesting (JTAG) chips on the board?
-
- ie: An FPGA or CPLD ...
-
-========================================
-
-(I) What target config files need updating?
-
- In fact it's best if you submit a patch with those
- updates. Most of the other information listed here
- is just to help create a good patch.
-
-========================================
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/README
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/README b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/README
deleted file mode 100755
index 11ea2db..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/README
+++ /dev/null
@@ -1,372 +0,0 @@
-Welcome to OpenOCD!
-===================
-
-OpenOCD provides on-chip programming and debugging support with a
-layered architecture of JTAG interface and TAP support including:
-
-- (X)SVF playback to faciliate automated boundary scan and FPGA/CPLD
- programming;
-- debug target support (e.g. ARM, MIPS): single-stepping,
- breakpoints/watchpoints, gprof profiling, etc;
-- flash chip drivers (e.g. CFI, NAND, internal flash);
-- embedded TCL interpreter for easy scripting.
-
-Several network interfaces are available for interacting with OpenOCD:
-telnet, TCL, and GDB. The GDB server enables OpenOCD to function as a
-"remote target" for source-level debugging of embedded systems using
-the GNU GDB program (and the others who talk GDB protocol, e.g. IDA
-Pro).
-
-This README file contains an overview of the following topics:
-
-- quickstart instructions,
-- how to find and build more OpenOCD documentation,
-- list of the supported hardware,
-- the installation and build process,
-- packaging tips.
-
-
-============================
-Quickstart for the impatient
-============================
-
-If you have a popular board then just start OpenOCD with its config,
-e.g.:
-
- openocd -f board/stm32f4discovery.cfg
-
-If you are connecting a particular adapter with some specific target,
-you need to source both the jtag interface and the target configs,
-e.g.:
-
- openocd -f interface/ftdi/jtagkey2.cfg -c "transport select jtag" \
- -f target/ti_calypso.cfg
-
- openocd -f interface/stlink-v2-1.cfg -c "transport select hla_swd" \
- -f target/stm32l0.cfg
-
-NB: when using an FTDI-based adapter you should prefer configs in the
-ftdi directory; the old configs for the ft2232 are deprecated.
-
-After OpenOCD startup, connect GDB with
-
- (gdb) target extended-remote localhost:3333
-
-
-=====================
-OpenOCD Documentation
-=====================
-
-In addition to the in-tree documentation, the latest manuals may be
-viewed online at the following URLs:
-
- OpenOCD User's Guide:
- http://openocd.org/doc/html/index.html
-
- OpenOCD Developer's Manual:
- 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.
-
-For more information, refer to these documents or contact the developers
-by subscribing to the OpenOCD developer mailing list:
-
- openocd-devel@lists.sourceforge.net
-
-Building the OpenOCD Documentation
-----------------------------------
-
-By default the OpenOCD build process prepares documentation in the
-"Info format" and installs it the standard way, so that "info openocd"
-can access it.
-
-Additionally, the OpenOCD User's Guide can be produced in the
-following different formats:
-
- # If PDFVIEWER is set, this creates and views the PDF User Guide.
- make pdf && ${PDFVIEWER} doc/openocd.pdf
-
- # If HTMLVIEWER is set, this creates and views the HTML User Guide.
- make html && ${HTMLVIEWER} doc/openocd.html/index.html
-
-The OpenOCD Developer Manual contains information about the internal
-architecture and other details about the code:
-
- # NB! make sure doxygen is installed, type doxygen --version
- make doxygen && ${HTMLVIEWER} doxygen/index.html
-
-
-==================
-Supported hardware
-==================
-
-JTAG adapters
--------------
-
-AICE, ARM-JTAG-EW, ARM-USB-OCD, ARM-USB-TINY, AT91RM9200, axm0432,
-BCM2835, Bus Blaster, Buspirate, Chameleon, CMSIS-DAP, Cortino, DENX,
-Digilent JTAG-SMT2, DLC 5, DLP-USB1232H, embedded projects, eStick,
-FlashLINK, FlossJTAG, Flyswatter, Flyswatter2, Gateworks, Hoegl, ICDI,
-ICEBear, J-Link, JTAG VPI, JTAGkey, JTAGkey2, JTAG-lock-pick, KT-Link,
-Lisa/L, LPC1768-Stick, MiniModule, NGX, NXHX, OOCDLink, Opendous,
-OpenJTAG, Openmoko, OpenRD, OSBDM, Presto, Redbee, RLink, SheevaPlug
-devkit, Stellaris evkits, ST-LINK (SWO tracing supported),
-STM32-PerformanceStick, STR9-comStick, sysfsgpio, TUMPA, Turtelizer,
-ULINK, USB-A9260, USB-Blaster, USB-JTAG, USBprog, VPACLink, VSLLink,
-Wiggler, XDS100v2, Xverve.
-
-Debug targets
--------------
-
-ARM11, ARM7, ARM9, AVR32, Cortex-A, Cortex-R, Cortex-M,
-Feroceon/Dragonite, DSP563xx, DSP5680xx, FA526, MIPS EJTAG, NDS32,
-XScale, Intel Quark.
-
-Flash drivers
--------------
-
-ADUC702x, AT91SAM, AVR, CFI, DSP5680xx, EFM32, EM357, FM3, FM4, Kinetis,
-LPC8xx/LPC1xxx/LPC2xxx/LPC541xx, LPC2900, LPCSPIFI, Marvell QSPI,
-Milandr, NIIET, NuMicro, PIC32mx, PSoC4, SiM3x, Stellaris, STM32, STMSMI,
-STR7x, STR9x, nRF51; NAND controllers of AT91SAM9, LPC3180, LPC32xx,
-i.MX31, MXC, NUC910, Orion/Kirkwood, S3C24xx, S3C6400, XMC1xxx, XMC4xxx.
-
-
-==================
-Installing OpenOCD
-==================
-
-A Note to OpenOCD Users
------------------------
-
-If you would rather be working "with" OpenOCD rather than "on" it, your
-operating system or JTAG interface supplier may provide binaries for
-you in a convenient-enough package.
-
-Such packages may be more stable than git mainline, where
-bleeding-edge development takes place. These "Packagers" produce
-binary releases of OpenOCD after the developers produces new "release"
-versions of the source code. Previous versions of OpenOCD cannot be
-used to diagnose problems with the current release, so users are
-encouraged to keep in contact with their distribution package
-maintainers or interface vendors to ensure suitable upgrades appear
-regularly.
-
-Users of these binary versions of OpenOCD must contact their Packager to
-ask for support or newer versions of the binaries; the OpenOCD
-developers do not support packages directly.
-
-A Note to OpenOCD Packagers
----------------------------
-
-You are a PACKAGER of OpenOCD if you:
-
-- Sell dongles and include pre-built binaries;
-- Supply tools or IDEs (a development solution integrating OpenOCD);
-- Build packages (e.g. RPM or DEB files for a GNU/Linux distribution).
-
-As a PACKAGER, you will experience first reports of most issues.
-When you fix those problems for your users, your solution may help
-prevent hundreds (if not thousands) of other questions from other users.
-
-If something does not work for you, please work to inform the OpenOCD
-developers know how to improve the system or documentation to avoid
-future problems, and follow-up to help us ensure the issue will be fully
-resolved in our future releases.
-
-That said, the OpenOCD developers would also like you to follow a few
-suggestions:
-
-- Send patches, including config files, upstream, participate in the
- discussions;
-- Enable all the options OpenOCD supports, even those unrelated to your
- particular hardware;
-- Use "ftdi" interface adapter driver for the FTDI-based devices.
-
-As a PACKAGER, never link against the FTD2XX library, as the resulting
-binaries can't be legally distributed, due to the restrictions of the
-GPL.
-
-
-================
-Building OpenOCD
-================
-
-The INSTALL file contains generic instructions for running 'configure'
-and compiling the OpenOCD source code. That file is provided by
-default for all GNU autotools packages. If you are not familiar with
-the GNU autotools, then you should read those instructions first.
-
-The remainder of this document tries to provide some instructions for
-those looking for a quick-install.
-
-OpenOCD Dependencies
---------------------
-
-GCC or Clang is currently required to build OpenOCD. The developers
-have begun to enforce strict code warnings (-Wall, -Werror, -Wextra,
-and more) and use C99-specific features: inline functions, named
-initializers, mixing declarations with code, and other tricks. While
-it may be possible to use other compilers, they must be somewhat
-modern and could require extending support to conditionally remove
-GCC-specific extensions.
-
-You'll also need:
-
-- make
-- libtool
-- pkg-config >= 0.23 (or compatible)
-
-Additionally, for building from git:
-
-- autoconf >= 2.64
-- automake >= 1.9
-- texinfo
-
-USB-based adapters depend on libusb-1.0 and some older drivers require
-libusb-0.1 or libusb-compat-0.1. A compatible implementation, such as
-FreeBSD's, additionally needs the corresponding .pc files.
-
-USB-Blaster, ASIX Presto, OpenJTAG and ft2232 interface adapter
-drivers need either one of:
- - libftdi: http://www.intra2net.com/en/developer/libftdi/index.php
- - ftd2xx: http://www.ftdichip.com/Drivers/D2XX.htm (proprietary,
- GPL-incompatible)
-
-CMSIS-DAP support needs HIDAPI library.
-
-Permissions delegation
-----------------------
-
-Running OpenOCD with root/administrative permissions is strongly
-discouraged for security reasons.
-
-For USB devices on GNU/Linux you should use the contrib/99-openocd.rules
-file. It probably belongs somewhere in /etc/udev/rules.d, but
-consult your operating system documentation to be sure. Do not forget
-to add yourself to the "plugdev" group.
-
-For parallel port adapters on GNU/Linux and FreeBSD please change your
-"ppdev" (parport* or ppi*) device node permissions accordingly.
-
-For parport adapters on Windows you need to run install_giveio.bat
-(it's also possible to use "ioperm" with Cygwin instead) to give
-ordinary users permissions for accessing the "LPT" registers directly.
-
-Compiling OpenOCD
------------------
-
-To build OpenOCD, use the following sequence of commands:
-
- ./bootstrap (when building from the git repository)
- ./configure [options]
- make
- sudo make install
-
-The 'configure' step generates the Makefiles required to build
-OpenOCD, usually with one or more options provided to it. The first
-'make' step will build OpenOCD and place the final executable in
-'./src/'. The final (optional) step, ``make install'', places all of
-the files in the required location.
-
-To see the list of all the supported options, run
- ./configure --help
-
-Cross-compiling Options
------------------------
-
-Cross-compiling is supported the standard autotools way, you just need
-to specify the cross-compiling target triplet in the --host option,
-e.g. for cross-building for Windows 32-bit with MinGW on Debian:
-
- ./configure --host=i686-w64-mingw32 [options]
-
-To make pkg-config work nicely for cross-compiling, you might need an
-additional wrapper script as described at
-
- http://www.flameeyes.eu/autotools-mythbuster/pkgconfig/cross-compiling.html
-
-This is needed to tell pkg-config where to look for the target
-libraries that OpenOCD depends on. Alternatively, you can specify
-*_CFLAGS and *_LIBS environment variables directly, see "./configure
---help" for the details.
-
-Parallel Port Dongles
----------------------
-
-If you want to access the parallel port using the PPDEV interface you
-have to specify both --enable-parport AND --enable-parport-ppdev, since the
-the later option is an option to the parport driver.
-
-The same is true for the --enable-parport-giveio option, you have to
-use both the --enable-parport AND the --enable-parport-giveio option
-if you want to use giveio instead of ioperm parallel port access
-method.
-
-Using FTDI's FTD2XX
--------------------
-
-The (closed source) FTDICHIP.COM solution is faster than libftdi on
-Windows. That is the motivation for supporting it even though its
-licensing restricts it to non-redistributable OpenOCD binaries, and it
-is not available for all operating systems used with OpenOCD. You may,
-however, build such copies for personal use.
-
-The FTDICHIP drivers come as either a (win32) ZIP file, or a (Linux)
-TAR.GZ file. You must unpack them ``some where'' convenient. As of this
-writing FTDICHIP does not supply means to install these files "in an
-appropriate place."
-
-You should use the following ./configure options to make use of
-FTD2XX:
-
- --with-ftd2xx-win32-zipdir
- Where (CYGWIN/MINGW) the zip file from ftdichip.com
- was unpacked <default=search>
- --with-ftd2xx-linux-tardir
- Where (Linux/Unix) the tar file from ftdichip.com
- was unpacked <default=search>
- --with-ftd2xx-lib=(static|shared)
- Use static or shared ftd2xx libs (default is static)
-
-Remember, this library is binary-only, while OpenOCD is licenced
-according to GNU GPLv2 without any exceptions. That means that
-_distributing_ copies of OpenOCD built with the FTDI code would
-violate the OpenOCD licensing terms.
-
-Note that on Linux there is no good reason to use these FTDI binaries;
-they are no faster (on Linux) than libftdi, and cause licensing issues.
-
-
-==========================
-Obtaining OpenOCD From GIT
-==========================
-
-You can download the current GIT version with a GIT client of your
-choice from the main repository:
-
- git://git.code.sf.net/p/openocd/code
-
-You may prefer to use a mirror:
-
- http://repo.or.cz/r/openocd.git
- git://repo.or.cz/openocd.git
-
-Using the GIT command line client, you might use the following command
-to set up a local copy of the current repository (make sure there is no
-directory called "openocd" in the current directory):
-
- git clone git://git.code.sf.net/p/openocd/code openocd
-
-Then you can update that at your convenience using
-
- git pull
-
-There is also a gitweb interface, which you can use either to browse
-the repository or to download arbitrary snapshots using HTTP:
-
- http://repo.or.cz/w/openocd.git
-
-Snapshots are compressed tarballs of the source tree, about 1.3 MBytes
-each at this writing.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/69f466b5/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/README.OSX
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/README.OSX b/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/README.OSX
deleted file mode 100755
index 979c64b..0000000
--- a/docs/os/tutorials/downloads/openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4/README.OSX
+++ /dev/null
@@ -1,49 +0,0 @@
-Building OpenOCD for OSX
-------------------------
-
-There are a few prerequisites you will need first:
-
-- Xcode 5 (install from the AppStore)
-- Command Line Tools (install from Xcode 5 -> Preferences -> Downloads)
-- Gentoo Prefix (http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap.xml)
- or
-- Homebrew (http://mxcl.github.io/homebrew/)
- or
-- MacPorts (http://www.macports.org/install.php)
-
-
-With Gentoo Prefix you can build the release version or the latest
-devel version (-9999) the usual way described in the Gentoo
-documentation. Alternatively, install the prerequisites and build
-manually from the sources.
-
-
-With Homebrew you can either run:
- brew install [--HEAD] openocd (where optional --HEAD asks brew to
- install the current git version)
- or
- brew install libtool automake libusb [libusb-compat] [hidapi] [libftdi]
- (to install the needed dependencies and then proceed with the
- manual building procedure)
-
-
-For building with MacPorts you need to run:
- sudo port install libtool automake autoconf pkgconfig \
- libusb [libusb-compat] [libftdi1]
-
-You should also specify LDFLAGS and CPPFLAGS to allow configure to use
-MacPorts' libraries, so run configure like this:
- LDFLAGS=-L/opt/local/lib CPPFLAGS=-I/opt/local/include ./configure [options]
-
-
-See README for the generic building instructions.
-
-If you're using a USB adapter and have a driver kext matched to it,
-you will need to unload it prior to running OpenOCD. E.g. with Apple
-driver (OS X 10.9 or later) for FTDI run:
- sudo kextunload -b com.apple.driver.AppleUSBFTDI
-for FTDI vendor driver use:
- sudo kextunload FTDIUSBSerialDriver.kext
-
-To learn more on the topic please refer to the official libusb FAQ:
-https://github.com/libusb/libusb/wiki/FAQ