You can find some description here (generated from file doc/openocd.texi) : http://openocd.org/doc/html/Config-File-Guidelines.html It is not exhaustive, but a good starting point
Antonio On Thu, Jan 17, 2019 at 9:39 PM Tommy Murphy <[email protected]> wrote: > > Seems pretty self explanatory to me? > What do you want to do? > In my experience normally the most relevant/important folders are chip, > target and board. > And these describe the hierarchy from the bottom up to the thing that you > normally connect to. > E.g. normally a board script pulls in a target (well - at least one) which > pulls in a chip script. > The board script will often also pull in an interface script for the debug > connection (JTAG, SWD, CMSIS-DAP etc.). > And often users will add support for their board/target with only a few > people needing to write new chip scripts. > Well that's my tuppence worth anyway... > _______________________________________________ > OpenOCD-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openocd-devel _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
