- added run_and_halt_time to deprecated/removed functions section
git-svn-id: svn://svn.berlios.de/openocd/trunk@880 b42882b7-edfa-0310-969c-e2dbd0fdcd60
This commit is contained in:
ntfreak
parent
db7c3810c2
commit
530057a846
|
|
@ -1434,6 +1434,15 @@ use @option{flash write_image} command passing @option{erase} as the first param
|
||||||
this config option has been removed, simply adding @option{init} and @option{reset halt} to
|
this config option has been removed, simply adding @option{init} and @option{reset halt} to
|
||||||
the end of your config script will give the same behaviour as using @option{daemon_startup reset}
|
the end of your config script will give the same behaviour as using @option{daemon_startup reset}
|
||||||
and @option{target cortex_m3 little reset_halt 0}.
|
and @option{target cortex_m3 little reset_halt 0}.
|
||||||
|
@item @b{run_and_halt_time}
|
||||||
|
@cindex run_and_halt_time
|
||||||
|
This command has been removed for simpler reset behaviour, it can be simulated with the
|
||||||
|
following commands:
|
||||||
|
@smallexample
|
||||||
|
reset run
|
||||||
|
sleep 100
|
||||||
|
halt
|
||||||
|
@end smallexample
|
||||||
@end itemize
|
@end itemize
|
||||||
|
|
||||||
@node FAQ
|
@node FAQ
|
||||||
|
|
|
||||||
|
|
@ -1,76 +1,76 @@
|
||||||
Some outstanding issues w.r.t. non-ARM32 targets
|
Some outstanding issues w.r.t. non-ARM32 targets
|
||||||
================================================
|
================================================
|
||||||
This file describes outstanding issues w.r.t.
|
This file describes outstanding issues w.r.t.
|
||||||
non-ARM32 targets.
|
non-ARM32 targets.
|
||||||
|
|
||||||
Ideas & patches welcome!
|
Ideas & patches welcome!
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Flash drivers
|
Flash drivers
|
||||||
-------------
|
-------------
|
||||||
The flash drivers contain ARM32 code that is used
|
The flash drivers contain ARM32 code that is used
|
||||||
to execute code on the target.
|
to execute code on the target.
|
||||||
|
|
||||||
This needs to be handled in some CPU independent
|
This needs to be handled in some CPU independent
|
||||||
manner.
|
manner.
|
||||||
|
|
||||||
The ocl and ecos flash drivers compile the flash
|
The ocl and ecos flash drivers compile the flash
|
||||||
driver code to run on the target on the developer
|
driver code to run on the target on the developer
|
||||||
machine.
|
machine.
|
||||||
|
|
||||||
The ocl and ecos flash drivers should be unified
|
The ocl and ecos flash drivers should be unified
|
||||||
and instructions should be written on how to
|
and instructions should be written on how to
|
||||||
compile the target flash drivers. Perhaps
|
compile the target flash drivers. Perhaps
|
||||||
using automake?
|
using automake?
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
eCos has CFI driver that could probably be compiled
|
eCos has CFI driver that could probably be compiled
|
||||||
for all targets. The trick is to figure out a
|
for all targets. The trick is to figure out a
|
||||||
way to make the compiled flash drivers work
|
way to make the compiled flash drivers work
|
||||||
on all target memory maps + sort out all the
|
on all target memory maps + sort out all the
|
||||||
little details
|
little details
|
||||||
|
|
||||||
32 vs. 64 bit
|
32 vs. 64 bit
|
||||||
-------------
|
-------------
|
||||||
Currently OpenOCD only supports 32 bit targets.
|
Currently OpenOCD only supports 32 bit targets.
|
||||||
|
|
||||||
Adding 64 bit support would be nice but there
|
Adding 64 bit support would be nice but there
|
||||||
hasn't been any call for it in the openocd development
|
hasn't been any call for it in the openocd development
|
||||||
mailing list
|
mailing list
|
||||||
|
|
||||||
target support
|
target support
|
||||||
--------------
|
--------------
|
||||||
target.h is relatively CPU agnostic and
|
target.h is relatively CPU agnostic and
|
||||||
the intention is to move in the direction of less
|
the intention is to move in the direction of less
|
||||||
instruction set specific.
|
instruction set specific.
|
||||||
|
|
||||||
Non-CPU targets are also supported, but there isn't
|
Non-CPU targets are also supported, but there isn't
|
||||||
a lot of activity on it in the mailing list currently.
|
a lot of activity on it in the mailing list currently.
|
||||||
An example is FPGA programming support via JTAG,
|
An example is FPGA programming support via JTAG,
|
||||||
but also flash chips can be programmed directly
|
but also flash chips can be programmed directly
|
||||||
using JTAG.
|
using JTAG.
|
||||||
|
|
||||||
non-JTAG physical layer
|
non-JTAG physical layer
|
||||||
-----------------------
|
-----------------------
|
||||||
JTAG is not the only physical protocol used to talk to
|
JTAG is not the only physical protocol used to talk to
|
||||||
CPUs.
|
CPUs.
|
||||||
|
|
||||||
OpenOCD does not today have targets that use non-JTAG.
|
OpenOCD does not today have targets that use non-JTAG.
|
||||||
|
|
||||||
The actual physical layer is a relatively modest part
|
The actual physical layer is a relatively modest part
|
||||||
of the total OpenOCD system.
|
of the total OpenOCD system.
|
||||||
|
|
||||||
|
|
||||||
PowerPC
|
PowerPC
|
||||||
-------
|
-------
|
||||||
there exists open source implementations of powerpc
|
there exists open source implementations of powerpc
|
||||||
target manipulation, but there hasn't been a lot
|
target manipulation, but there hasn't been a lot
|
||||||
of activity in the mailing list.
|
of activity in the mailing list.
|
||||||
|
|
||||||
MIPS
|
MIPS
|
||||||
----
|
----
|
||||||
Currently OpenOCD has a MIPS target defined. This is the
|
Currently OpenOCD has a MIPS target defined. This is the
|
||||||
first non-ARM example of a CPU target
|
first non-ARM example of a CPU target
|
||||||
Loading…
Reference in New Issue