mirror of
git://git.code.sf.net/p/openocd/code
synced 2025-07-19 05:55:41 +10:00
Add another board ... OMAP2420 "H4" board. This won't be very widely used with OpenOCD, but with mainline support in both U-Boot and Linux it at least makes for a more complete set (and another testcase). This is incomplete support in several respects. The ARM11 support is not very deep yet; most registers aren't available, and the ETM can't be hooked up. Plus, there's no script for OMAP-specific stuff like setting up the SDRAM controller. Eventually the same NAND controller driver should work with OMAP2 and OMAP3. git-svn-id: svn://svn.berlios.de/openocd/trunk@2242 b42882b7-edfa-0310-969c-e2dbd0fdcd60 |
||
---|---|---|
.. | ||
aduc702x.cfg | ||
at91eb40a.cfg | ||
at91r40008.cfg | ||
at91rm9200.cfg | ||
at91sam9260_ext_RAM_ext_flash.cfg | ||
at91sam9260.cfg | ||
davinci.cfg | ||
epc9301.cfg | ||
feroceon.cfg | ||
imx21.cfg | ||
imx27.cfg | ||
imx31.cfg | ||
imx35.cfg | ||
is5114.cfg | ||
ixp42x.cfg | ||
lm3s811.cfg | ||
lm3s3748.cfg | ||
lm3s6965.cfg | ||
lpc2103.cfg | ||
lpc2124.cfg | ||
lpc2129.cfg | ||
lpc2148.cfg | ||
lpc2294.cfg | ||
lpc2378.cfg | ||
lpc2478.cfg | ||
mega128.cfg | ||
netx500.cfg | ||
omap2420.cfg | ||
omap3530.cfg | ||
omap5912.cfg | ||
pic32mx.cfg | ||
pxa255.cfg | ||
pxa270.cfg | ||
readme.txt | ||
sam7se512.cfg | ||
sam7x256.cfg | ||
samsung_s3c2410.cfg | ||
samsung_s3c2440.cfg | ||
samsung_s3c4510.cfg | ||
samsung_s3c6410.cfg | ||
sharp_lh79532.cfg | ||
smdk6410.cfg | ||
smp8634.cfg | ||
stm32.cfg | ||
str710.cfg | ||
str730.cfg | ||
str750.cfg | ||
str912.cfg | ||
test_reset_syntax_error.cfg | ||
test_syntax_error.cfg | ||
ti_dm355.cfg | ||
ti_dm6446.cfg | ||
xba_revA3.cfg |
Prerequisites: The users of OpenOCD as well as computer programs interacting with OpenOCD are expecting that certain commands do the same thing across all the targets. Rules to follow when writing scripts: 1. The configuration script should be defined such as , for example, the following sequences are working: reset flash info <bank> and reset flash erase_address <start> <len> and reset init load In most cases this can be accomplished by specifying the default startup mode as reset_init (target command in the configuration file). 2. If the target is correctly configured, flash must be writable without any other helper commands. It is assumed that all write-protect mechanisms should be disabled. 3. The configuration scripts should be defined such as the binary that was written to flash verifies (turn off remapping, checksums, etc...) flash write_image [file] <parameters> verify_image [file] <parameters> 4. jtag_khz sets the maximum speed (or alternatively RCLK). If invoked multiple times only the last setting is used. interface/xxx.cfg files are always executed *before* target/xxx.cfg files, so any jtag_khz in interface/xxx.cfg will be overridden by target/xxx.cfg. jtag_khz in interface/xxx.cfg would then, effectively, set the default JTAG speed. Note that a target/xxx.cfg file can invoke another target/yyy.cfg file, so one can create target subtype configurations where e.g. only amount of DRAM, oscillator speeds differ and having a single config file for the default/common settings.