Øyvind Harboe wrote: > Why do you prefer to have the interface definition inside such > config files? > > Why would you *not* want the interface config file to come from > OpenOCD's published configuration files for interaces? > > > > openocd -f interface/abc.cfg -f customerconfig.cfg > >
At the begin of OpenOCD (in 2005 for Amontec), it was very powerful to have the possibility to provide to our customers only one openocd.exe and one openocd.cfg for their specific boards. In this way, Amontec was minimizing the risk regarding file versions ... This was the case for a lot of our customers using OpenOCD in daisy chain (multi TAP/devices in the same chain), ... When your customer ask you for an issue using the OpenOCD for their specific JTAG chain, your first reflex is to ask about what version they use, what configuration files they use, and if possible the shematic of the specific board ... Some mails after, some hours after, you provide one openocd.exe and one openocd.cfg , and you ask your customer to test with these two files as: openocd -f myconfig.cfg The openocd -f interface/abc.cfg -f customerconfig.cfg is better as it split interface and board configuration, but sometimes the ONE configuration file can stay a great advantage. Regards, Laurent http://www.amontec.com -------------------------- Making JTAG a Snap with JTAGkey full-speed USB JTAG adapter with JTAGkey2 high-speed USB JTAG dongle _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
