As part of the updates I've been working on - I want to introduce a new
"config file directory".
Today we have these two main directories:
(1) ${INSTALL}/lib/openocd/interface
Holds the jtag dongle configuration files
(2) ${INSTALL}/lib/openocd/target
Holds a mixture of Chips & Boards & Init Scripts
I propose
1) *splitting* the target directory and creating a "board" directory.
2) What remains in "target" - is really "chip configurations".
Using the file "hammer.cfg" as an example... - it would split into two
files.
(A) 'target/samsung_s3c2410.cfg' - the chip on the hammer board
(B) 'board/hammer.cfg - which would source [find target/samsung_s3c2410.cfg]
This file would move to ${INSTALL}/lib/openocd/board/hammer.cfg
The general rule would be:
(3) If it is inside the chip - it goes in: target/CHIPNAME.cfg
(4) If it is something on the board - it goes in: board/BOARDNAME.cfg
The benefit is 3 fold
(5) A good benefit is: - as Rick Altherr put it...
carlos> I start OpenOCD with the command:
carlos> openocd -f interface/flyswatter.cfg -f target/hammer.cfg -c
"init" -c "reset"
rick> Hurray! Someone uses the built-in configs.
(6) Make it simpler for others to do exactly that. Many people develop
via "copy/paste" examples.
A confusing aspect of this is for a newbie to *SEE* what belongs in the
*CHIP* vrs the *BOARD* putting *BOARD* configs in a BOARD directory, it
serves as a documentation delineation point - a more "clear line in the
sand".
(7) Make it easier to create better example config files by highlighting
"chip features" or "cpu features"
The simple truth is - the same (target) CHIP is used on MULTIPLE boards,
having a common reusable CHIP config file is a good thing.
====
Comments?
====
-Duane.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
