On Nov 4, 2008, at 3:08 AM, Øyvind Harboe wrote:
I've committed the attached patch to get the ball rolling on how we can make it easier to figure out what targets OpenOCD supports. The general idea is that there should be a command whichwill print in tabular form the supported CPUs and what options that shouldbe used so as to get the user started on the right track.The user will have some string of numbers and letters that describe hisparticular type of CPU. Vendor specific names is going to far, but hopefully CPU families can be covered.... Thoughts? Patches? :-) -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer <cpuhelp.txt>_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
A thought in this direction is to use Doxygen to generate documentation from source code comments. It keeps the documentation close to the code so it is more likely to be up to date and the final output form can be similar to what we have today. Some areas of the docs, like the getting started section, could still be in separate files, but it means that things like a list of targets could be generated from the source.
-- Rick Altherr [EMAIL PROTECTED]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Slashdot signature
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
