From 9e5a6679cac36667e51f24a6bd5670396cd06ed6 Mon Sep 17 00:00:00 2001 From: ntfreak Date: Thu, 28 Feb 2008 10:07:54 +0000 Subject: - added svn props - fixed mixed line endings on flash.c, log.c, gdb_server.c git-svn-id: svn://svn.berlios.de/openocd/trunk@371 b42882b7-edfa-0310-969c-e2dbd0fdcd60 --- testing/index.html | 160 ++++++++++++++++++++++++++--------------------------- 1 file changed, 80 insertions(+), 80 deletions(-) (limited to 'testing') diff --git a/testing/index.html b/testing/index.html index 234d597f..8aabcd44 100644 --- a/testing/index.html +++ b/testing/index.html @@ -1,80 +1,80 @@ - - -

Testing

-A test should be done on code committed to svn. Commit, then test. That way -one can know for sure *what* code was actually tested. -

Release procedure

-OpenOCD trunk is work in progress. Expect it to change daily and to have -some work in progress. -

-If you need the latest released and tested version, look for binary snapshots of -OpenOCD. Worst case look up the test result table below for the features -that are important to you and extract and build the version that has the right -cocktail of working features for you. You can also work with the community -to address the problems you are seing. Testing work and bug reports are -highly appreciated. -

-The OpenOCD community may decide to create release branches. If -this happens, then a branch will be created from OpenOCD trunk. The particular -version to create that branch might be an older version rather than the latest -and greatest. Fixes are then ported to that release branch from OpenOCD trunk. -

Vocabulary

- - - - -
Passed versionThe latest version on which the test is known to pass
Broken versionThe latest version on which the test is known to fail. n/a when older than passed version.
IDA unqiue ID to refer to a test. The unique numbers are maintained in this file.
- -

OpenOCD test results

-These tests can be performed on any JTAG device as long -as they are executed using the unmodified code from SVN. -

-The latest version in which the test is known to have -passed is in the table below. - - - - - - - - -
IDSynopsisPassed versionBroken version
ocd1Telnet Windows291n/a
ocd2Telnet Linux291n/a
ocd3Telnet Cygwin291n/a
ocd4ARM7 debugging291
xscale1XScale debugging291
xscale2XScale MMU291
-

OpenOCD JTAG device test results

-Each JTAG device must be tested - - - - - -
IDSynopsisPassed versionBroken version
jtag1Wiggler291n/a
jtag2Parport291n/a
jtag3...291n/a
- -

Policy on removing features from OpenOCD

-If a feature in OpenOCD is known to be broken and nobody has -submitted a fix and the feature is causing trouble for -maintainence, it can be removed from OpenOCD trunk. The threshold -for temporarily removing something from OpenOCD trunk is low to -ease maintainence and place the burden of maintainence on -those that care about a feature. -

-Note that code is never deleted from OpenOCD svn, it remains -in svn so if somebody sees a feature removed that they would -like kept, they have but to port and fix that feature -back up to main trunk. This document can be helpful in this -regard in that the latest working version and the known broken -version may be listed. -

Policy on adding features from OpenOCD

-To add a feature to OpenOCD, generally it should not break any existing -features and it should be functional and the code reasonably readable -and useful to others in the OpenOCD community. The code does not -have to be completed. Work in progress is fine for OpenOCD trunk. -

-Also new tests should be defined. Note that the code does not have -to pass all the tests. In fact it can be helpful to have tests -to describe facets that really should be working, but aren't -done yet. - -

ocd4 - ARM7 debugging

-Connect to ARM7 device(any), use GDB load to load a program into RAM and single halt, resume and single step. - - \ No newline at end of file + + +

Testing

+A test should be done on code committed to svn. Commit, then test. That way +one can know for sure *what* code was actually tested. +

Release procedure

+OpenOCD trunk is work in progress. Expect it to change daily and to have +some work in progress. +

+If you need the latest released and tested version, look for binary snapshots of +OpenOCD. Worst case look up the test result table below for the features +that are important to you and extract and build the version that has the right +cocktail of working features for you. You can also work with the community +to address the problems you are seing. Testing work and bug reports are +highly appreciated. +

+The OpenOCD community may decide to create release branches. If +this happens, then a branch will be created from OpenOCD trunk. The particular +version to create that branch might be an older version rather than the latest +and greatest. Fixes are then ported to that release branch from OpenOCD trunk. +

Vocabulary

+ + + + +
Passed versionThe latest version on which the test is known to pass
Broken versionThe latest version on which the test is known to fail. n/a when older than passed version.
IDA unqiue ID to refer to a test. The unique numbers are maintained in this file.
+ +

OpenOCD test results

+These tests can be performed on any JTAG device as long +as they are executed using the unmodified code from SVN. +

+The latest version in which the test is known to have +passed is in the table below. + + + + + + + + +
IDSynopsisPassed versionBroken version
ocd1Telnet Windows291n/a
ocd2Telnet Linux291n/a
ocd3Telnet Cygwin291n/a
ocd4ARM7 debugging291
xscale1XScale debugging291
xscale2XScale MMU291
+

OpenOCD JTAG device test results

+Each JTAG device must be tested + + + + + +
IDSynopsisPassed versionBroken version
jtag1Wiggler291n/a
jtag2Parport291n/a
jtag3...291n/a
+ +

Policy on removing features from OpenOCD

+If a feature in OpenOCD is known to be broken and nobody has +submitted a fix and the feature is causing trouble for +maintainence, it can be removed from OpenOCD trunk. The threshold +for temporarily removing something from OpenOCD trunk is low to +ease maintainence and place the burden of maintainence on +those that care about a feature. +

+Note that code is never deleted from OpenOCD svn, it remains +in svn so if somebody sees a feature removed that they would +like kept, they have but to port and fix that feature +back up to main trunk. This document can be helpful in this +regard in that the latest working version and the known broken +version may be listed. +

Policy on adding features from OpenOCD

+To add a feature to OpenOCD, generally it should not break any existing +features and it should be functional and the code reasonably readable +and useful to others in the OpenOCD community. The code does not +have to be completed. Work in progress is fine for OpenOCD trunk. +

+Also new tests should be defined. Note that the code does not have +to pass all the tests. In fact it can be helpful to have tests +to describe facets that really should be working, but aren't +done yet. + +

ocd4 - ARM7 debugging

+Connect to ARM7 device(any), use GDB load to load a program into RAM and single halt, resume and single step. + + -- cgit v1.2.3