From: zwelch Date: Wed, 20 May 2009 08:43:18 +0000 (+0000) Subject: Move non-arm target overview from source tree to doxygen manual. X-Git-Tag: v0.2.0~657 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=ed294121ef3cf086cf582b635688eaa3caa487a7;p=openocd Move non-arm target overview from source tree to doxygen manual. git-svn-id: svn://svn.berlios.de/openocd/trunk@1853 b42882b7-edfa-0310-969c-e2dbd0fdcd60 --- diff --git a/doc/manual/target.txt b/doc/manual/target.txt index 26f77084..d569711d 100644 --- a/doc/manual/target.txt +++ b/doc/manual/target.txt @@ -23,12 +23,6 @@ This section needs to describe OpenOCD's ARM target support. */ -/** @page targetnotarm OpenOCD Non-ARM Targets - -This section needs to describe OpenOCD's non-ARM target support. - - */ - /** @page targetregister OpenOCD Target Register API This section needs to describe OpenOCD's Target Register API, as diff --git a/doc/manual/target/notarm.txt b/doc/manual/target/notarm.txt new file mode 100644 index 00000000..c368ed1c --- /dev/null +++ b/doc/manual/target/notarm.txt @@ -0,0 +1,71 @@ +/** @page targetnotarm OpenOCD Non-ARM Targets + +This page describes outstanding issues w.r.t. non-ARM targets. + +@section targetnotarmflash Flash drivers + +The flash drivers contain ARM32 code that is used +to execute code on the target. + +This needs to be handled in some CPU independent +manner. + +The ocl and ecos flash drivers compile the flash +driver code to run on the target on the developer +machine. + +The ocl and ecos flash drivers should be unified +and instructions should be written on how to +compile the target flash drivers. Perhaps +using automake? + + +eCos has CFI driver that could probably be compiled +for all targets. The trick is to figure out a +way to make the compiled flash drivers work +on all target memory maps + sort out all the +little details + +@section targetnotarm32v64 32 vs. 64 bit + +Currently OpenOCD only supports 32 bit targets. + +Adding 64 bit support would be nice but there +hasn't been any call for it in the openocd development +mailing list + +@section targetnotarmsupport Target Support + +target.h is relatively CPU agnostic and +the intention is to move in the direction of less +instruction set specific. + +Non-CPU targets are also supported, but there isn't +a lot of activity on it in the mailing list currently. +An example is FPGA programming support via JTAG, +but also flash chips can be programmed directly +using JTAG. + +@section targetnotarmphy non-JTAG physical layer + +JTAG is not the only physical protocol used to talk to +CPUs. + +OpenOCD does not today have targets that use non-JTAG. + +The actual physical layer is a relatively modest part +of the total OpenOCD system. + + +@section targetnotarmppc PowerPC + +there exists open source implementations of powerpc +target manipulation, but there hasn't been a lot +of activity in the mailing list. + +@section targetnotarmmips MIPS + +Currently OpenOCD has a MIPS target defined. This is the +first non-ARM example of a CPU target + + */ diff --git a/src/non-arm-targets.txt b/src/non-arm-targets.txt deleted file mode 100644 index 2d49c882..00000000 --- a/src/non-arm-targets.txt +++ /dev/null @@ -1,76 +0,0 @@ -Some outstanding issues w.r.t. non-ARM32 targets -================================================ -This file describes outstanding issues w.r.t. -non-ARM32 targets. - -Ideas & patches welcome! - - - - -Flash drivers -------------- -The flash drivers contain ARM32 code that is used -to execute code on the target. - -This needs to be handled in some CPU independent -manner. - -The ocl and ecos flash drivers compile the flash -driver code to run on the target on the developer -machine. - -The ocl and ecos flash drivers should be unified -and instructions should be written on how to -compile the target flash drivers. Perhaps -using automake? - - - -eCos has CFI driver that could probably be compiled -for all targets. The trick is to figure out a -way to make the compiled flash drivers work -on all target memory maps + sort out all the -little details - -32 vs. 64 bit -------------- -Currently OpenOCD only supports 32 bit targets. - -Adding 64 bit support would be nice but there -hasn't been any call for it in the openocd development -mailing list - -target support --------------- -target.h is relatively CPU agnostic and -the intention is to move in the direction of less -instruction set specific. - -Non-CPU targets are also supported, but there isn't -a lot of activity on it in the mailing list currently. -An example is FPGA programming support via JTAG, -but also flash chips can be programmed directly -using JTAG. - -non-JTAG physical layer ------------------------ -JTAG is not the only physical protocol used to talk to -CPUs. - -OpenOCD does not today have targets that use non-JTAG. - -The actual physical layer is a relatively modest part -of the total OpenOCD system. - - -PowerPC -------- -there exists open source implementations of powerpc -target manipulation, but there hasn't been a lot -of activity in the mailing list. - -MIPS ----- -Currently OpenOCD has a MIPS target defined. This is the -first non-ARM example of a CPU target \ No newline at end of file