> 2) One possible process improvement that I believe makes sense is to start > enforcing a rule that authors of new configuration files must include a > minimal comment header at the top of the file that specifies the exact > hardware/debugger combination used. The SAM-ICE (J-link) debugger I am > using for example has a number of internal quirks that may not exist in > other brands and vice-versa.
To enforce rules on target scripts, we first need to have some rules to enforce against. I suggest that you start writing up a patch against the OpenOCD documentation on requirements for target config scripts. The other problem I have with this is that I want as many scripts as possible, even if they are crummy.... Perhaps we could mark or name scripts that don't follow the rules as work-in-progress? I.e. either it needs to have all the right comments & features, or it needs a "work in progress" note at the top? -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
